Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Make built-in DAV client work with HTTPS' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Make built-in DAV client work with HTTPS
Authored by: JakBeatZ on Mar 11, '04 11:28:56AM

An easier way would be to just use ssh and do ssh tunnels. ssh is installed by default on all OS X clients 10.2+ via terminal and most machines should support sshd (except Windows).

I have tried, but haven't been able to get it working. Wonder if anyone else has given it a whirl.



[ Reply to This | # ]
Make built-in DAV client work with HTTPS
Authored by: rabblerouser on Mar 11, '04 01:11:03PM
SSH tunnels certainly work. Just make sure that you're not forward a local port to the https (443) port on the webdav server - you don't need to talk https because you're already tunneling over a secured connection.

the command would be something like this: ssh -L 8080:localhost:80 remote.server.name

Then just connect to http://localhost:8080/whateverdirectory/ and your webdav connection will be tunneled over the ssh connection you just established.

Once this is working, you can set up auto-login with authorized keys and then create a shell script containing the ssh command from above.

If you want to get really fancy, you could have that script launch at startup/login, and if you're using a laptop, use one of the network (re)connection utilities to restart the script if/when your network connection is interrupted.

[ Reply to This | # ]
Make built-in DAV client work with HTTPS
Authored by: kevinv on Mar 12, '04 09:45:49AM

the downside to ssh tunnels is you have to have ssh running on the server side. Not everyone has control over the server to be able to ensure that.



[ Reply to This | # ]
Make built-in DAV client work with HTTPS
Authored by: rasputnik on Oct 11, '04 07:52:36AM

You'd need accounts on the server for that to work.



[ Reply to This | # ]