I just stumbled upon a collection of bash completions which can be quite handy: https://github.com/perlpunk/shell-completions
I tried mojo, cpan and pip completions in a sandbox and they worked like a charm!
The only question I’ve got is, has anyone ever done a security audit of the repository? Anyone has taken the time to look at the code? I could try auditing but I’m not even sure what to look for.
I feel quite wary of letting an unknown source access to my bash session and what I type.
You must log in or register to comment.
A general programming discussion community.
Rules:
- Be civil.
- Please start discussions that spark conversation
Other communities
Systems
Functional Programming
Also related
- 0 users online
- 5 users / day
- 14 users / week
- 44 users / month
- 138 users / 6 months
- 1 subscriber
- 336 Posts
- 544 Comments
- Modlog
- mods:
- Evan
- @Restioson@lemmy.ml
The mojo, cpan and pip bash scripts don’t fail my test of “skimming over the source and looking for dangerous external commands like curl or
rm” (good syntax highlighting is helpful here). They look like typical completion scripts. However, if your Linux distribution has a pip completion script in their repos, prefer that one.Thanks. At least I’ve got a few clues to look for when auditing such code.
Auditing is nothing more than reading the code. Give it a read and make sure you understand everything it’s doing.
This is a great lesson on trust as well. I can tell you I did an audit and it all looks good but does that really have any value?
Agree w/ you re trust.