Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <41E42508.3020400@t-online.de> Date: Tue, 11 Jan 2005 20:12:08 +0100 From: "Harald Dunkel" User-Agent: Mozilla Thunderbird 0.9 (X11/20041130) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: cannot access $HOME (on Samba) via ssh Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ID: Xd0hj0ZeQeRME9kxg2a38EoLo4yDnhx5E4K8+ArVFNx0+LBaLD5woJ X-TOI-MSGID: 3cf06c4d-876f-4b5b-acfa-059b44c4dee8 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Igor Pechtchanski wrote: | , second | paragraph. | HTH, | Igor Sorry, but this does not help. If I got this right, then you assume that either sshd or the login process started by sshd are running as SYSTEM, and the bash started later inherits the restricted network access somehow, making an access to shares which require an authentication impossible. :-( Please note that ssh and rsh are typical applications of users used to work on remote machines in a LAN. If you take away the network access to their home directory and all other shares, then this is a very severe restriction. And making a network share accessible without any authentication is usually not an option, either. Not a good deal. Regards Harri -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB5CUHUTlbRTxpHjcRAvnjAJ4vIka1zWhCJS7NF9tAWhGoqOoq5wCdE19r PqZ9ESIpitZvbwzpELS5N88= =KV+3 -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/