We started off with a discussion of this recent project. https://blog.filippo.io/ssh-whoami-filippo-io/
It can read your ssh keys you present and determine who you are. It does this because if you have a github account the following works( for public keys): https://github.com/REPLACE_WITH_YOUR_GITHUB_HANDLE.keys This is an article why this may be bad. https://blog.benjojo.co.uk/post/auditing-github-users-keys https://github.com/FiloSottile/whosthere reminder that if you generated your ssh keys between 2007-2008 on debian, consider cycling. https://github.com/g0tmi1k/debian-ssh http://www.metasploit.com/ More ssh hardening. https://github.com/oittaa/happy-dance saw a pull request for happy-dance that used awk a bit. I pointed out that sed and awk are very powerful: http://www.unix.com/shell-programming-and-scripting/174525-tetris-game-based-shell-script-new-algorithm.html while we were on the topic of of obscure programming feats. http://www.ioccc.org/years-spoiler.html essentially docker in bash. https://github.com/p8952/bocker We this talked about how to make NLUG better. -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
