You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#Here I am at a terminal on my local machine (called 'home')
home># I ssh to a remote server called 'Server1'
home> ssh Server1
# On Server1 I run 'ls'
Server1> ls
server1file.bin
# This file server1file.bin lives in my home directory on Server1
If I now use the advanced features of TermKit to refer to server1file.bin (copy to a different location say), TermKit should retain the fact that the handle resides on host Server1
The text was updated successfully, but these errors were encountered:
I believe this is being looked into, but there's security considerations that need to take place in order for this to work. For example:
How do you securely connect to the remote machine given that web browsers don't have the concept of an SSH connection? You'd need your own secure protocol capable of running a top a WebSocket or HTTP and you'd have to make sure that's it's cryptographically secure.
So yes, it probably will happen, but there's quite a few security considerations that need to happen first.
Hi unconed. This relates to my HN post http://news.ycombinator.com/item?id=2559788 .
If I now use the advanced features of TermKit to refer to
server1file.bin
(copy to a different location say), TermKit should retain the fact that the handle resides on hostServer1
The text was updated successfully, but these errors were encountered: