Possibility to get host, user, port and password by HTTP request

[GoogleCodeExporter]

What version of the product are you using? On what operating system?
2.10 on Debian Lenny (5.0)

Is there any possibility to get the SSH host, user, port and password depending 
on the HTTP 
request, instead of one host configuration per service?

I'd like to access, for instance, http://localhost:4200/:id or 
http://localhost:4200/:host/:user/:port or something like that, in a way the 
shellinabox would 
parse it and open the specific connection for that config, just waiting for the 
password (or 
connecting automatically if there is a public key present).

So, in my intranet I would host it and when accessing http://localhost:4200/1 
(with the config in 
some local file) or http://localhost:4200/domain.com/user01/2222 the connection 
would be 
also sucessful.

Any idea how could I solve this idea, if no code change is needed?

Thanks in advance.

Original issue reported on code.google.com by renat...@gmail.com on 25 Nov 2009 at 8:04

• Merged into: #28

[GoogleCodeExporter]

Take a look at the discussion in 
http://code.google.com/p/shellinabox/issues/detail?id=28

I believe it describes the exact same feature request. You can already do this 
with ShellInABox, 
if you provide a suitable script file and use the ${url} parameter. But you 
need to be very 
careful as you are potentially opening yourself up to all sorts of security 
problems. That's why I 
don't really want to document this deployment mode in any more detail.

If you know how to set it up, and if you are fully aware of the security 
implications, then go 
ahead and use ShellInABox in this fashion. In all other cases, you are probably 
better of using it 
in the standard deployment mode which has far fewer security "surprises".

Original comment by zod...@gmail.com on 25 Nov 2009 at 11:21

• Changed state: Duplicate

[GoogleCodeExporter]

I didn't realize there were so many issues already open/closed, so I didn't see 
the other issue.

The security "suprises" aren't really a problem, considering this SSH "helper" 
will be inside my network, in a way 
only authorized people will access. I understand and am aware of the security 
gap, if it leaks in some way.

Thanks.

Original comment by renat...@gmail.com on 25 Nov 2009 at 11:28