I also found this open source tool for sandboxing to be useful: https://github.com/bullfrogsec/bullfrog
Deleted Comment
I also found this open source tool for sandboxing to be useful: https://github.com/bullfrogsec/bullfrog
https://www.virustotal.com/gui/url/6dd23e90ee436e1ff066725aa...
> BitDefender - government
> Sophos - government
> Forcepoint ThreatSeeker - government
- From a Docker/Moby Maintainer
The hypothetical new control code is different because it does not display a hyperlink; it directly opens the link using the appropriate system URL handler.
[0] https://gitlab.com/gnachman/iterm2/-/issues/10994I'm unclear which of these are being described:
1: when printed and clicked, they may be handled by the terminal, and the terminal's handling allows more behaviors than it should, allowing code execution
2: when printed, these urls are automatically executed by the shell, allowing code execution
Neither are good of course, but they're different levels of badness, and I feel like I must be missing a single critical word somewhere to be able to figure out which it is.
---
That said, oh boy I do not want this:
>Most terminal emulators these days allow using Osc 8 to directly generate hyperlinks from arbitrary text.
Is there a standard way to disable it? That sounds awful, terminals don't have even a small fraction of browsers' malicious-link-defense mechanisms (as demonstrated). I always want to see the full url in a terminal.
Apart from this a major issue is DNS based dynamic filtering which is way batter to get right in a Kubernetes environment with something like Cilium. IP lists are impossible to manage with modern level of third party integrations.