Re: Cygwin ssh session privileges differ from console privileges?

2004-09-03 Thread Shaddy Baddah
Thank you Corinna. Your suggestion worked. You are too cool for school
:-D.
- Original Message - 
From: "Corinna Vinschen" 
To: 
Sent: Thursday, September 02, 2004 6:13 PM
Subject: Re: Cygwin ssh session privileges differ from console privileges?
The bottom line is, if you need all the user's access rights use password
authentication.  If that doesn't help, you're out of luck.
As you suggested, I had to change from publickey authentication to
password,keyboard-interactive. Here is how it was achieved:
 [EMAIL PROTECTED] ~
 $ ssh -o 'PasswordAuthentication yes' -o 'PreferredAuthentications 
password,keyboard-interactive' [EMAIL PROTECTED]
 [EMAIL PROTECTED]'s password:
 Last login: Thu Sep  2 20:40:16 2004 from mydesktop

 [EMAIL PROTECTED] ~
 $ sqlplus /nolog
 SQL*Plus: Release 9.2.0.1.0 - Production on Fri Sep 3 05:17:37 2004
 Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.
 SQL> connect / as sysdba
 Connected.
Thanks again, and best regards,
Shaddy

--
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/


Re: Cygwin ssh session privileges differ from console privileges?

2004-09-02 Thread Corinna Vinschen
On Sep  2 15:09, Shaddy Baddah wrote:
> I am having a problem with the privileges on a Cygwin ssh session. It
> seems as though the Cygwin ssh session does not have all the
> privileges of a console session, logged in as the same user. This is
> happening on cygwin v1.5.10-3 under Win2K SP4. The openssh version is
> v3.9p1-1.
> [...]
> I would expect that they would be the same, but understand that there
> might be quirks associated with sshd launching a login session as the
> authenticated user. Is there a plausible explanation as to why there
> is a difference?

It depends on how you log in through ssh.

If you're using password authentication, the same authentication mechanism
is used as if you're logging in locally via the GUI.  Not counting extra
initializations which are only run after GUI logon, password authentication
should grant you about the same rights.

Public Key authentication OTOH is *bypassing* the Windows authentication
mechanism, resulting in a very different access token attached to your
session.  For one, there is no password attached and no network credentials,
so you don't have the same automagical access to network shares.  Another
problem is that you didn't even start a logon session from WinNT's point of
view, which has a couple of interesting side effect.

The bottom line is, if you need all the user's access rights use password
authentication.  If that doesn't help, you're out of luck.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  mailto:[EMAIL PROTECTED]
Red Hat, Inc.

--
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/