[GH-ISSUE #5363] curl and wget profiles: shouldnt they be pretty much identical? #2972

New issue

Open

opened 2026-05-05 09:38:00 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 09:38:00 -06:00

Owner

Originally created by @ghost on GitHub (Sep 5, 2022).
Original GitHub issue: https://github.com/netblue30/firejail/issues/5363

Discussed in https://github.com/netblue30/firejail/discussions/5342

^{Originally posted by slowpeek August 27, 2022}
Aside for other things:

curl	wget
private-tmp	#private-tmp
protocol inet,inet6	protocol unix,inet,inet6

So with stock profiles:

one can download to /tmp with wget, but not with curl
one is allowed to communicate over unix sockets with wget (does wget even support it?), but not with curl

Originally created by @ghost on GitHub (Sep 5, 2022). Original GitHub issue: https://github.com/netblue30/firejail/issues/5363 ### Discussed in https://github.com/netblue30/firejail/discussions/5342 <div type='discussions-op-text'> <sup>Originally posted by **slowpeek** August 27, 2022</sup> Aside for other things: |curl|wget| |-|-| |private-tmp|#private-tmp| |protocol inet,inet6|protocol unix,inet,inet6| So with stock profiles: - one can download to `/tmp` with wget, but not with curl - one is allowed to communicate over unix sockets with wget (does wget even support it?), but not with curl </div>