here we arehope you brought a helmet
-
RE: https://infosec.exchange/@briankrebs/116563409906012864
here we are
hope you brought a helmet -
RE: https://infosec.exchange/@briankrebs/116563409906012864
here we are
hope you brought a helmet@Viss
Best I can do is Unsung by Helmet. -
RE: https://infosec.exchange/@briankrebs/116563409906012864
here we are
hope you brought a helmet@Viss imma use the 30-day cooldown, but it won't be enough

Neither is no-dependencies.
Probably the only option is burn it all down and plant flowers in the ashes.
-
@Viss imma use the 30-day cooldown, but it won't be enough

Neither is no-dependencies.
Probably the only option is burn it all down and plant flowers in the ashes.
@ellie well, one way to be sensible about it is to do what i proposed in my little preso today:
- light up incus
- create a new container
- firewall it off from everything but the internet
- install whatever
- tcpdump -i incusbr0 and watch for shady fuckery
- if there is no shady fuckery, that install is 'safe', and you can do stuff in it
- keep secrets, env vars, api keys, tokens etc outside the container, never let any llm tech read secrets or drive stuff or delete stuff -
RE: https://infosec.exchange/@briankrebs/116563409906012864
here we are
hope you brought a helmet@Viss the "wreckoning"
-
R relay@relay.infosec.exchange shared this topic