5 ms·
My network blocks outbound ssh, so I use https.
by prepend 2y ago
My network blocks outbound ssh, so I use https.
- mariocesar 2y agoI had the same issue, but you can clone using SSH over HTTPS with GitHub. Like this: git clone ssh://git@ssh.github.com:443/rtyley/small-test-repo.git instead of: git clone git@github.com:rtyley/small-test-repo.git
- crtasm 2y agoIs that using HTTPS? It looks like regular ssh running on port 443.
- NegativeK 2y agoAlso, if you're on a corporate network and start pushing ssh through 443, a competent security team should check in on you to make sure things are okay.
- mariocesar 2y agoYes, if you have audits, most probably they will look for protocols traffic rather than just ports open
- mariocesar 2y agoThe protocol is SSH, but the port is 443. Yes, it's not HTTPS, it's just SSH on a different port than 22.
- gchamonlive 2y agoIs that by design or accident? I couldn't imagine living without ssh.
- prepend 2y agoIt’s by design. There was some cyber practice doc years ago calling out how outbound ssh is a security risk because it can’t be monitored. And they’re afraid people will steal data and send it out without network security knowing. I hated the policy because I loved outbound ssh tunnels to get around blocked websites (ie, no gmail). But I kind of understand it because dumb people will do dumb things and they can’t differentiate people who will use appropriate judgement. But I’ve found that eventually every large org I’ve worked for ends up blocking ssh.
- corytheboyd 2y agoIf it’s your home ISP doing this, you just need to call and ask for them to remove the restriction. Obviously not likely to work if this is a corporate network.