Hacker News Reader

Comment by prepend | Hacker News Reader

My network blocks outbound ssh, so I use https.

I 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

Is that using HTTPS? It looks like regular ssh running on port 443.

Also, 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.

Yes, if you have audits, most probably they will look for protocols traffic rather than just ports open

The protocol is SSH, but the port is 443. Yes, it's not HTTPS, it's just SSH on a different port than 22.

If 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.

Is that by design or accident?

I couldn't imagine living without ssh.

It’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.

Reply on news.ycombinator.com