Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Host Awareness #11

Open
tezza opened this issue May 18, 2011 · 1 comment
Open

Host Awareness #11

tezza opened this issue May 18, 2011 · 1 comment

Comments

@tezza
Copy link

tezza commented May 18, 2011

Hi unconed. This relates to my HN post http://news.ycombinator.com/item?id=2559788 .

#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

@hach-que
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants