cheat.sh
cheat.sh copied to clipboard
one_lin3r is a repository of security-related commands
Hi Igor,
I wonder if one-lin3r database of commands is worth inserting in cht.sh.
Pro:
- Already organized by OS
- Seems that the concepts covered are not yet addressed in cht.sh, and names don't collide
Con:
- Uses Python class definitions, so migration might be more than simple formatting. But, I've seen worse.
https://github.com/D4Vinci/One-Lin3r/tree/master/one_lin3r/core/liners
Thanks, your weather command is lovely.
@matt-hayden Matt hi!
Wow! What a cool project! Thank you a lot for mentioning it. It is definitely worth binding to cheat.sh.
What do you think: at what namespace should it be bound?
Should it be just cheat.sh/one_lin3r? Or should it be distributed among the mentioned
commands, so that if you make say curl cheat.sh/ncat you'll find
the one_lin3r lines there too?
What do you think about it?
I don't have an affinity for the namespace one_lin3r because of the extra typing -- of course preserving credit to the author.
I believe that nmap is the only non-operating-system that's promoted to the "multi" catchall. I would demote it and duplicate it across BSD and Linux. nmap on Windows is not reliable enough to use in code, imho.