Oh well.
Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
91–100 of 119 posts
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#92Earlier quoted context omitted.
Yes. Do not connect with agent forwarding, as doing so would allow the server operator to connect to other locations as you. Do not forward environment information, though the typical ssh default is not to. You will likely leak your username. If you connect from an internet reachable host, and you made the mistake of not doing the first item in this list, they could easily connect back to you, not requiring any zero…
> Do not connect with agent forwarding This requires an explicit argument, right?
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#93Earlier quoted context omitted.
People also expect their postcards to arrive untampered. ISPs, Comcast in particular, inject ad-loading javascript into HTTP pages. https://arstechnica.com/tech-policy/2014/09/why-comcasts-jav... https://www.reddit.com/r/technology/comments/9b5ikd/
In fairness isn't that a result of your relationship with your isp? If you remain because of price or no other services available why wouldn't you use a vpn knowing your isp is a hostile actor and probably trying to deeply inspect packets, etc?
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#94Earlier quoted context omitted.
The “public” in public key just means it doesn’t need to be secret, for cryptographic purposes. It’s different to your public identity as a person — I don’t think I’ve ever seen an ssh key used for that, in practice. I might have multiple ssh key pairs related to my different roles as: high school teacher, two different GitHub users, peer to peer pharmaceuticals distributor, and upstanding private citizen. I cannot s…
Prospective employers probably would want to connect your street pharmacy side-gig with your identity, you just wouldn't want them to.
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#95> The Hack Club Slack Imagine making a job board work over ssh and then using slack to communicate. Especially when things like this exist and are much more in the spirit: https://github.com/shazow/ssh-chat
It’s built by a 15 year old Hack Clubber and streams to / from a channel on the Hack Club Slack.
Open source at https://github.com/quackduck/devzat
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#96Are there are any security precautions in using ssh (or telnet, netcat or curl for that matter) to connect to an unknown service like this?
alias sshn="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no"Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#97Are there are any security precautions in using ssh (or telnet, netcat or curl for that matter) to connect to an unknown service like this?
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#98> The Hack Club Slack Imagine making a job board work over ssh and then using slack to communicate. Especially when things like this exist and are much more in the spirit: https://github.com/shazow/ssh-chat
Try running $ ssh devzat.hackclub.com It’s built by a 15 year old Hack Clubber and streams to / from a channel on the Hack Club Slack. Open source at https://github.com/quackduck/devzat
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#99Earlier quoted context omitted.
Yes. Do not connect with agent forwarding, as doing so would allow the server operator to connect to other locations as you. Do not forward environment information, though the typical ssh default is not to. You will likely leak your username. If you connect from an internet reachable host, and you made the mistake of not doing the first item in this list, they could easily connect back to you, not requiring any zero…
Would it increase security if I ssh from a docker container?
Re: Show HN: Apply for a job through SSH, $ ssh jobs.hackclub.com
#100Earlier quoted context omitted.
Would it increase security if I ssh from a docker container?
Docker containers aren't provably secure. If you want isolation, use a VM that doesn't have host file system access. This way, if the VM is compromised, just throw it away and it can't leak out the way containers do.
Not only are they not provably secure (very few things are), they are explicitly not intended for use as a security boundary. Their whole gimmick is lightweight containers you can use instead of VMs if you trust everyone who's going to run code under them.