It sounds like you are actually looking for sslh ( http://www.rutschle.net/tech/sslh.shtml ) on the server – It allows you to run https and ssh at the same time, both on port 443.

@ Scott Hansen:
It’s on the App store.

Wow. I had no idea they had a bittorrent app for the iPhone. And it works on Synology!

Luke Maciak wrote:

@ Scott Hansen:
Oh, nice. I like that it’s open source. I don’t like that it does not seem to have an iOS client but I guess that’s not surprising considering Apple developer fees don’t necessarily mesh with free software ideals.

An iOS client is in the works. The beauty of it is that the open API and the thorougly documented Block Exchange Protocol are enabling people to work on multiple clients and even different server implementations. It also just recently got re-licensed (MPLv2 I think) for app-store compatibility.

Scott

Seafile actually looks really neat. Thanks for the link. How resource intensive is the server? Is this something you could run from a Raspbery or a PogoPlug at an acceptable speed?

I dont really know, since i run it on my x86-server. But there is a RPi-Version on Seafile.org and it tends to get better performance than that crappy Owncloud-thing (and i know some people use that on RPi)

I never noticed any performance-problems on my system, but when I just looked it used a bit over 300MB RAM, what might be a bit much for RPi.

@ Scott Hansen:

Oh, nice. I like that it’s open source. I don’t like that it does not seem to have an iOS client but I guess that’s not surprising considering Apple developer fees don’t necessarily mesh with free software ideals.

@ Dr. Azrael Tod:

Seafile actually looks really neat. Thanks for the link. How resource intensive is the server? Is this something you could run from a Raspbery or a PogoPlug at an acceptable speed?

i’ve been using seafile for about a year now. Yes it needs having a server, but since i’d run one anyways that isn’t that big of a difference to me.
Seafile is accessible by http and i can point my parents/friends to an URL they can use to get files i want to share.

i’ve been thinking about setting up a SOCKS-tunnel for different uses, but since i’m until now able to do most things via smartphone (that in doubt uses it’s own internet connection rather than corporate wlan) or browser.
But having SSH respond on 443 is a nice idea. I’m prefering typical mail ports like 25, 110, 465 or 587 or 995 since those should be open too and i’d not need hacks to support https/ssh on the same port (i’ve seen an article on that some time ago).

Nice! Except I moved on from Btsync to Syncthing almost a year ago. Btsync’s recent move to a “limited-features for the free version” model and their continued adherence to closed-source have driven a lot of people away. Syncthing still isn’t quite ready for the “everyman” point-and-click solution but it’s getting pretty close. I highly recommend giving it a spin!

Your SSH tunnel approach would probably work fine with Syncthing as well (it uses port 22000 by default, and 21025 for a global discovery server). I typically just run behind a VPN outside my home network and that works fine (only if you can get the VPN ports opened).

Scott