I guess SSH is less common for windows. VPN serves similar rol but less *nux-centric. Setup procedure for VPN should also be similar to what you described for SSH. (untestd)
Срд, 11 Янв 2012, Eric Iverson писал(а): > It is relatively easy to have a secure JHS server serving remote clients. > > The trick is to piggyback JHS on a secure SSH tunnel. JHS communication is > through the tunnel and has the same encryption protection as the SHH > connection. If SHH security is good enough for you, there is no reason to > not use JHS from a remote client. > > An SHH tunnel connects a local port on the client to a local port on the > server and uses its encryption/decryption on the connection. This allows a > browser on the client to connect to a local client port and have a secure > connection to a local port on the server. > > Following are basic steps: > > 1. set up server machine with SHH server > 2. set up client machine with SHH client > 3. configure SHH client and verify you can access the server > 4. add tunnel config to SSH client (e.g., 65001 <--> 127.0.0.1:65001) > 5. use SHH to connect client to server > 6. from client SSH session start JHS on server with command: > ~/j64-701/bin/jhs & > 7. from client browser session browse to localhost:65001 (passed through > tunnel to 65001 on server) > 8. you have secure JHS services on client from server > > If you want to use port 65001 on your client for local JHS use, then you'll > want to configure the JHS server on your server to use another port and > configure the SHH tunnel to make that connection (e.g., 65003 <-> > 127.0.0.1:65003) > > If you already have SHH access from your client to your server you have > already done all the hard parts. Tunnel config is done a bit differently on > different SHH clients. On windows putty do the following: > > 1. load saved session that connects to your server > 2. in the Category tree navigate to Connection>SSH>Tunnels > 3. type 65001 in Source port > 4. type 127.0.0.1:65001 (server local port) in Destination > 5. click Add > 6. navigate to Session > 7. click Save (to save config changes) > > I had always planned to add https support to JHS but this is a non-trivial, > I now the SHH tunnel works so well that perhaps there is no need for JHS > https support. > > This really is the way to use a cloud machine! > > I think this is a significant capability and welcome your feedback. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm -- regards, ==================================================== GPG key 1024D/4434BAB3 2008-08-24 gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3 ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
