Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CLI doesn't have config file like olm

Open
#42 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
go, linux

Research direction

Start with the CLI documentation and the systemd unit referenced in the reproduction steps, then trace how the Pangolin client id and secret are supplied to the CLI. Done means Linux users have a documented secret-passing mechanism that does not expose credentials in /proc//environ or ps output.

Written by the indexing model from the issue text.

Description

enhancement
Describe the Bug

This is a security issue as the client id and secret are always available in /proc/<pid>/environ or in ps output.

Environment
  • OS Type & Version: (e.g., Ubuntu 22.04) Any Linux distro
  • Pangolin Version: Latest
  • Gerbil Version: Latest
  • Traefik Version: Latest
  • Newt Version: Latest
  • Client Version: (if applicable)
To Reproduce

Run pangolin CLI as per the docs provided (including systemd unit) on site, check ps auxf | grep -i pangolin output

Expected Behavior

If this is going to be used for config on Linux machines, there needs to be a mechanism for passing secrets that doesn't expose on CLI or otherwise

Dominant language
Go
Stars
50
Forks
18
Avg merge
2d 9h
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fosrl/cli

All issues in fosrl/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.