HackerLangs
トップ新着トレンドコメント過去質問紹介求人

danslo

440 カルマ登録 6 年前

投稿

Building a faster YARA engine in pure Go

sansec.io
1 ポイント·投稿者 danslo·5 か月前·0 コメント

コメント

danslo
·12 日前·議論
It reads like an ad.

Secondly these are "just" IDORs, arguably the easiest class of vulnerabilities.

Thirdly it compares to GPT 5.5 and Opus 4.8.

No, we don't have Mythos at home.
danslo
·先月·議論
>from our experience, uBO Lite does not seem to be as good as the original non-Lite version

In what way? I've never noticed a difference.
danslo
·先月·議論
It's not a freebie, it still requires a subscription and burns tokens twice as fast as Opus.
danslo
·先月·議論
Support is slowly landing... https://www.phoronix.com/news/Lenovo-Yoga-Slim-7x-Gen11-Linu...
danslo
·先月·議論
I could be wrong, but I believe the name is in reference to the Divine Rapier, an item in Dota 2, which is very popular among Russian speakers.
danslo
·2 か月前·議論
Fine. Not really different from most governments relying on private suppliers to manage their infrastructure.
danslo
·2 か月前·議論
DigiD itself is government-owned, but its infrastructure is managed by Solvinity (a private company). Not really different from the US gov running half its stack on AWS.
danslo
·2 か月前·議論
This one's pretty bad but there are some preconditions.

Requires a "rewrite" directive with a questionmark in the replacement string, and then a subsequent "set" directive that references a regex capture group (e.g. set $var $1).

Also the POC assumes ASLR is disabled.
danslo
·2 か月前·議論
We're enrolled in the Cyber Verification Program and Claude will happily help me look for vulnerabilities and built POCs demonstrating RCE. But when I point it to a malware sample and ask for analysis it will still refuse any work. It's incredibly frustrating.
danslo
·3 か月前·議論
If only the blog itself wasn't written by AI?

>No reasoning. No capability. Just exploitation of how the score is computed.

shudder
danslo
·3 か月前·議論
The only reason I used Tailscale's menubar applet was to change exit nodes, I definitely don't need a whole UI.

Guess I'll just stick with CLI only for now (via darwin-nix)
danslo
·4 か月前·議論
If you're OK with it draining 3% battery per hour when you close the lid, sure.
danslo
·4 か月前·議論
Not sure if it's Claude Code or golsp, but I had to uninstall the plugin. Regularly makes Claude Code crash with golsp going to 100% CPU usage.
danslo
·5 か月前·議論
It is as long as they're not refunding you when you make a loss.
danslo
·8 か月前·議論
This is slop right?

>This isn’t a minor gap; it’s a fundamental limitation.

>His timeline? At least a decade, probably much longer.

>What does that mean? Simply throwing more computing power and data at current models isn’t working anymore.

>His timeline for truly useful agents? About ten years.
danslo
·8 か月前·議論
s/postgres/sqlite/g
danslo
·9 か月前·議論
I tried to switch from neovim to helix for a couple weeks, but noted down the following things that were essential to me and not implemented yet:

- Code actions on save, for example adding Go imports: https://github.com/helix-editor/helix/pull/6486

- Fuzzy search with a filepicker like telescope+rg, seems to have been added earlier this year: https://github.com/helix-editor/helix/pull/11285

- Automatically updating buffers when the files on disk change (claude, templ, sqlc, etc): https://github.com/helix-editor/helix/issues/1125

- File tree in browser, which has been rejected in favor of a plugin system which has not materialized yet: https://github.com/helix-editor/helix/pull/5768

There were a number of other things too, that I could have lived with. I guess I'll try again in a year or two.