Hi Brian,
$ ssh -v brian@
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Connecting to port 22.
debug1: connect to address port 22: Connection timed out
ssh: connect to host port 22: Connection timed out
==
This suggests
Apart from not being secure, and not being a shell. It's actually far more
like the windows equivalent of rexec.
Obviously there's
psexec \\$HOST cmd.exe
but yeah, not quite the same as ssh. I think error codes get messed up
compared to ssh.
exit
cmd.exe exited on server with error cod
Hi,
On 15/06/07, Bengt-Arne Fjellner <[EMAIL PROTECTED]> wrote:
Or you could look at psexec in pstools it's the window equivalent to ssh
Sorry, I didn't mention this is across the Internet! psexec isn't an
option. The root problem is that impersonation of an admin user was
enough to execute "n
Hi Rene,
Try `ssh [EMAIL PROTECTED] after you login to the server as a (PowerUser)
user. You should be able to do almost anything as Administrator.
The user we are impersonating (via pubkey auth) is an admin user. Are
you suggesting that once logged in via pubkey, we ssh to localhost
again?
Hi,
We've been using OpenSSH through Cygwin to log into a number of
servers, and it's been great, so thanks. We sometimes have to restart
IIS, usually through a script using pubkey auth. I learned about
impersonation vs. authentication through not being able to use
iisreset - we now use "net stop
5 matches
Mail list logo