VessOnSecurity
bontchev's profile header
VessOnSecurity

@bontchev@infosec.exchange

Anti-virus, malware and infosec expert, crypto amateur, privacy advocate and general annoyance.

PGP keyID: 0x365697c632dd98d9

August 24, 2018

OK, I think I hit Claude's "garbage can full of rabid raccoons" side yesterday...

I have an old honeypot with just a couple of output plugins. I pointed Claude at it and also at a modern honeypot project with a large set of plugins and asked it to create a similar set for the older honeypot. The results were... "mixed", as the financial commentators say when the markets crater.

I don't know what exactly caused the problem. Maybe it was the need to examine and rewrite a multitude of files. I don't know.

At the start, it simply forgot to create half of the plugins. When I pointed this to it, it created the missing ones, but the results were, well...

The task was easy but not trivial. In some cases, only the honeypot name needed to be changed. In some (rare) cases, nothing had to be done, because the plugin just relays the JSON data sent to it by the honeypot. Yet in some cases the plugin needed a significant rewrite, because it outputs to a database with a different schema.

What Claude did:

1) Correctly changed the honeypot name in some plugins that needed that.

2) Didn't bother even changing the honeypot name in some plugins that needed only that.

3) Didn't rewrite the plugins that needed rewriting because they were outputting to a database with a different schema.

4) Completely rewrote 2 plugins that barely needed touching. And I mean completely. The result wasn't more efficient, it wasn't just full of bugs - it was "WTF is this shit?!" kind of result. I had to scrap it completely and replace it with the original source.

Elk Logo

Elk is in Preview!

Thanks for your interest in trying out Elk, our work-in-progress Mastodon web client!

Expect some bugs and missing features here and there. we are working hard on the development and improving it over time.

Elk is Open Source. If you'd like to help with testing, giving feedback, or contributing, reach out to us on GitHub and get involved.

To boost development, you can sponsor the Team through GitHub Sponsors. We hope you enjoy Elk!

Daniel RoePatakAnthony Fu三咲智子 Kevin Deng

The Elk Team