[GH-ISSUE #3352] Firejail doesn't hide set secrets #2104

Open
opened 2026-05-05 08:47:03 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @mustaqimM on GitHub (Apr 13, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3352

Describe the bug
The application (aria2) sets the secret which normally shows as stars, but when run with firejail, it gets exposed:
image

Behavior change on disabling firejail
N/A

To Reproduce
Steps to reproduce the behavior:

  1. Run with the command: firejail aria2c --rpc-secret=${RPC_SECRET}
  2. See error

Expected behavior
If possible, firejail should also obfuscate the secret set by the application

Desktop (please complete the following information):

  • Linux distribution and version (ie output of lsb_release -a)
    $❯ lsb_release -a
       LSB Version:    1.0
       Distributor ID: VoidLinux
       Description:    Void Linux
       Release:        rolling
       Codename:       void
    
  • Firejail version (output of firejail --version) exclusive or used git commit (git rev-parse HEAD)
$❯  firejail --version
firejail version 0.9.62

Compile time support:
        - AppArmor support is enabled
        - AppImage support is enabled
        - chroot support is enabled
        - file and directory whitelisting support is enabled
        - file transfer support is enabled
        - firetunnel support is enabled
        - networking support is enabled
        - overlayfs support is enabled
        - private-home support is enabled
        - seccomp-bpf support is enabled
        - user namespace support is enabled
        - X11 sandboxing support is enabled
Originally created by @mustaqimM on GitHub (Apr 13, 2020). Original GitHub issue: https://github.com/netblue30/firejail/issues/3352 **Describe the bug** The application (aria2) sets the secret which normally shows as stars, but when run with firejail, it gets exposed: ![image](https://user-images.githubusercontent.com/24436622/79111059-56d51800-7d6b-11ea-84d1-9867580ab19c.png) **Behavior change on disabling firejail** N/A **To Reproduce** Steps to reproduce the behavior: 1. Run with the command: firejail aria2c --rpc-secret=${RPC_SECRET} 2. See error **Expected behavior** If possible, firejail should also obfuscate the secret set by the application **Desktop (please complete the following information):** - Linux distribution and version (ie output of `lsb_release -a`) ``` $❯ lsb_release -a LSB Version: 1.0 Distributor ID: VoidLinux Description: Void Linux Release: rolling Codename: void ``` - Firejail version (output of `firejail --version`) exclusive or used git commit (`git rev-parse HEAD`) ``` $❯ firejail --version firejail version 0.9.62 Compile time support: - AppArmor support is enabled - AppImage support is enabled - chroot support is enabled - file and directory whitelisting support is enabled - file transfer support is enabled - firetunnel support is enabled - networking support is enabled - overlayfs support is enabled - private-home support is enabled - seccomp-bpf support is enabled - user namespace support is enabled - X11 sandboxing support is enabled ```
gitea-mirror added the
enhancement
label 2026-05-05 08:47:03 -06:00
Author
Owner

@matu3ba commented on GitHub (May 3, 2020):

Does aria2 interact with other programs for this feature and (if you know) in what ways?
What is the output of firejail --debug?

<!-- gh-comment-id:623089279 --> @matu3ba commented on GitHub (May 3, 2020): Does aria2 interact with other programs for this feature and (if you know) in what ways? What is the output of `firejail --debug`?
Author
Owner

@rusty-snake commented on GitHub (May 3, 2020):

What is the output of firejail --debug?

Why? Its completely unrelated.

Does aria2 interact with other programs for this feature and (if you know) in what ways?

I thing they do some hacks in /proc/self.

<!-- gh-comment-id:623089791 --> @rusty-snake commented on GitHub (May 3, 2020): > What is the output of firejail --debug? Why? Its completely unrelated. > Does aria2 interact with other programs for this feature and (if you know) in what ways? I thing they do some hacks in /proc/self.
Author
Owner

@rusty-snake commented on GitHub (Jun 4, 2020):

IDK if we ever want to implement this, because we would need to parse childs args.

labelling as "enhancement" for now.

<!-- gh-comment-id:638798686 --> @rusty-snake commented on GitHub (Jun 4, 2020): IDK if we ever want to implement this, because we would need to parse childs args. labelling as "enhancement" for now.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#2104
No description provided.