Message-Id:	<200501071258.j07Cw6tC028096@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Chris January" <chris AT atomice DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: EFS encrypted files & ssh
Date:	Fri, 7 Jan 2005 12:57:51 -0000
MIME-Version:	1.0
In-Reply-To:	<20050107113208.GC23589@cygbert.vinschen.de>
X-MailScanner-Information:	Please contact the Soho Consulting for more information
X-MailScannerQuill:	Found to be clean
X-AntiAbuse:	This header was added to track abuse, please include it with any abuse report
X-AntiAbuse:	Primary Hostname - quill.nothard.net
X-AntiAbuse:	Original Domain - cygwin.com
X-AntiAbuse:	Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse:	Sender Address Domain - atomice.net
X-Source:
X-Source-Args:
X-Source-Dir:
X-IsSubscribed:	yes

> Is it normal that during an SSH connection EFS-encrypted 
> files are not 
> accessible?
> Is it for the way the SSH token autentication is made?
Yes, it probably is.

I belive the user's private EFS is encrypted using their password hash. If
the SSH token was generated without using a password (e.g. because you are
using RSA authenitcation) then the EFS key can't be decrypted and used.

Chris


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

- Raw text -