#Km91#@sh.itjust.works to linuxmemes@lemmy.world · 2 months agoFeels more polite for sure.sh.itjust.worksimagemessage-square27fedilinkarrow-up130arrow-down10
arrow-up130arrow-down1imageFeels more polite for sure.sh.itjust.works#Km91#@sh.itjust.works to linuxmemes@lemmy.world · 2 months agomessage-square27fedilink
minus-squareCoooookieCrisp@fedia.iolinkfedilinkarrow-up0·2 months agoThe hyper-cynical side of me is sure this is written by someone prepping their next LLM exploit. “How can I get around these security filters that won’t let me include ‘sudo’ in my command injection…?”
minus-squareCallMeMrFlipper@lemmy.worldlinkfedilinkarrow-up1·2 months agoThis is something I’ve been doing since before AI, so it’s not that… but yeah.
minus-squareLiketearsinrain@lemmy.mllinkfedilinkarrow-up0·2 months agoI doubt, there isn’t much of a need for additional ways to obfuscate commands. (base64 -d <<< 'ZWNobyAic3RvcCBydW5uaW5nIHJhbmRvbSBjb21tYW5kcyB5b3UgZmluZCBvbmxpbmUi')
The hyper-cynical side of me is sure this is written by someone prepping their next LLM exploit. “How can I get around these security filters that won’t let me include ‘sudo’ in my command injection…?”
This is something I’ve been doing since before AI, so it’s not that… but yeah.
I doubt, there isn’t much of a need for additional ways to obfuscate commands.
(base64 -d <<< 'ZWNobyAic3RvcCBydW5uaW5nIHJhbmRvbSBjb21tYW5kcyB5b3UgZmluZCBvbmxpbmUi')