Subject: Re: debugging sftp-server - msg#00087

Previous Message by Date: click to view message preview

sftp and chroot

Woohoo I've finally gotten my sftp-server up and running, and upon logging in I noticed that I had access to the whole system (well, where my user can normally go at least). I'd like to chroot the server if I could so when users log in they stay in their home, is this possible?. Has anyone gotten this to work before? I would also like to get it working on a Linux box I have, so if anyone knows what needs to be done on that platform it would be appreciated as well, thankya. :) Shahrizal Shaari

Next Message by Date: click to view message preview

ssh1 authenticating to a remote kdc

Hi, I am a little confused on how ( if possible) to configure ssh to use a remote KDC to authenticate. I have openbsd 3.2 (official CDs) and no patches have been applied to my install. I have it setup as a router/bridge firewall. I am using authpf on the external side for access from a wifi client. Every thing runs great and I am very happy with openbsd and authpf/ssh setup. I would like minimize the number of passwords I need to use and remember. I have tried to do some study on this however I am still a little confused if what I wish to do can be done and/or is practical. I am trying to configure a wifi client that ssh's to the openbsd firewall as a authpf user so that ssh will use a remote Win2000 MicroSoft KDC database to authenticate the user instead of the local data base on the openbsd it would normally use. If this is possible do I configure this from the ssh config files or from the login.conf files? How (or with which client) does ssh1 communicate with with a remote MIT (like) kerberosV kdc on openbsd 3.2 ? In other words does ssh1 have a built in client or does it rely on a kerberosV client from the OS? Does the openbsd server need to be a part of a Realm? I would prefer it not to be. Is there any documents, articles or papers I could be point to that might help me ?

Previous Message by Thread: click to view message preview

debugging sftp-server

Is there a way to make sftp-server more verbose? I need to trouble shoot a client that I'm working with but there doesn't seem to be a way to make sftp-server chatty. I can pass debug statements to sshd, but it shuts up as soon as the sftp-server kicks in. I'm using openssh-3.1p1-6. Thanks, +jeff The information in this email and subsequent attachments may contain confidential information that is intended solely for the attention and use of the named addressee(s). This message or any part thereof must not be disclosed, copied, distributed, or retained by any person without the authorization from the addressee.

Next Message by Thread: click to view message preview

some problem with tunneling

hello, let me describe what i experienced in order to find out what went wrong. the situation: A B are computers. their users are usera and userb. B is somewhere in the internet, A is behind a firewall/router with ip masquerading enabled and port mapping disabled. (i have no way to change the router's configuration). i have access to both computers. what i wanted to do though was to remote work/configure computer A using vnc. in order to be able to connect to A i needed a way in there. so i used the command ssh -R 12345:127.0.0.1:22 userb@B on computer A to give myself a way to ssh into A (from B). i could indeed do that using the command ssh -p 12345 usera@xxxxxxxxx on B so in odrer to connect vnc to that copmuter i created another tunnel (after connecting via ssh from B). while being logged into A through ssh from B using the tunnel i created before i typed the command ssh -R 12346:127.0.0.1:5900 userb@B this also did work. the vnc server by the way has already been started on machine A. so the next thing i did is started a vnc client on B and connected to 127.0.0.1:12346 now i got an error message in the shell. unfortunately i can nether recall it exactly nor recreate the situation at the moment. so my mind tells me the error message contained "connection was reset by peer" and something like tcp nodelay (bad memory, i know). i have no clue what went wrong. hopefully you can help me understand that problem. btw: i know that i could have created a tunnel to port 5900 on machine A directly. i chose to use the way i did it because i thought i was able to do basically anything on machine A if i ever get logged into the shell. thanks in advance, nikolas