delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2018/04/19/09:46:09

X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; q=dns; s=
default; b=bG+L9UJucOtnLrZjf2fH6V/Vd1PX4qg/4VWzJBgqXqhZw3ioEqJIG
SJHbb0/vIfg55qW2qyn61Gy8N25A0vVadS78sxC9uXEAEPi0TzzwTYmIpRMaQVJ+
nKPBrykb1IT1V1mFM5ZHN+0lhuCkbjip8aDOl5XYb8agESyPO3mDjc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
:list-unsubscribe:list-subscribe:list-archive:list-post
:list-help:sender:date:from:to:subject:message-id:reply-to
:references:mime-version:content-type:in-reply-to; s=default;
bh=F3ma1VWXPgOyPe40d4jaBBrTCp8=; b=KqN8F74eC5dVJjik/TO99Ai/NNSI
H7G9Azz3HOXqeNJDlM8VpeuXozfhjxcEQac6Ict/rYSBb0in+fyvN22QqG9G5v2k
rpFVcFPS044UrpVAj7N97kiCT4BSltQeoom63jqMU4fGMWUyJJPNaJzGUD6UMQcJ
aKoCeAxJ/oLwXTg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-101.7 required=5.0 tests=AWL,BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=card
X-HELO: mout.kundenserver.de
Date: Thu, 19 Apr 2018 15:45:52 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Issue when trying to access files on a locked BitLocker volume
Message-ID: <20180419134552.GQ15911@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CAFBd_9syterX=7PSFb2+Z_KWMxvdrH3o_Rq3oJ65AVOYDX2=ig AT mail DOT gmail DOT com>
MIME-Version: 1.0
In-Reply-To: <CAFBd_9syterX=7PSFb2+Z_KWMxvdrH3o_Rq3oJ65AVOYDX2=ig@mail.gmail.com>
User-Agent: Mutt/1.9.2 (2017-12-15)
X-UI-Out-Filterresults: notjunk:1;V01:K0:osHKVEwM9KY=:C5ZdLAvXtta28xDJZDOQ4l 3coOfcnfZTKQrHZyMGDvonRooIEwH/dDPVXFbmB0ghezWTspfyjCislj1WpMPFsv/nAVEQjwX A9W4zlwY+XWynBzcnFuEB09ad0AQDp+FdYBGlKRuJADUMib9hn0fTDYgPtmoDGU3MMrcj8dDy yeySiFg7sfqdlasuiXLy9SzHTzhF8U0+jp01hKXl0yK7Ristaz6DRmpJRpIr6RJumYNxQJYbT 52Jimwbt2DzxtldnN9COXNqJftlwuRGgK4GuAfwz1dsKGLKpqwpBWX0Azbl7oRCJM+cTckGH4 gwO/eDoc4E3P1XIA9qFoE4vmXJEyXYFyBdNvsao4eZ9mrV0AeiljJnyV/qHPfAjbpFk6x5/lM Pj2wcySczM+tp/D/xXDhCrWDcb3cVRBYZIKFrxLLPa9JFns3qTXFUTA2d9r7HcabHAUUd/DiM Tl6sWr26IIxKRHXxAodlJn8fGCcvAR8+1SRR3iRlcJZL8hOAUq08gDa+PfHmAiILg8jE81p16 sjb9ZQzPrPa3cy+Y3eaJnpB3Bf3dCipWZ///aYTsUBuOcz/xpkXqo8xA2ipOukfVoAQHrk6Ix Dl0fTjYu8WkG1DPXoGjL5kVooPlPa1zTKTcurcilFK2C6Rc4g2xe0sz/5GfGOd48HlQcS9Vnm /mvruX7UduP3IX6LPtJs0v0gPU83Guz932cb79q2upb8zwrDASWbkFWczy4ydhI304ANLE4EB Y1zl629ck4AugNXLUyEYzcMM6WsaoygGefiNhw==

--GdbWtwDHkcXqP16f
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr 19 13:38, Vincent Gheur wrote:
> Hi,
>=20
> I'm using a Bitlocker encrypted SD card, which stays most of the time in =
my
> laptop, but is generally not unlocked. I'm unlocking it only when I need =
to
> access files on it.
>=20
> I have also a script which is started at regular intervals, which copies
> some critical files on the SD card when it is unlocked. I was using till
> recently a *very* old version of cygwin (probably downloaded 10 years ago=
),
> in which I could check whether my SD card was unlocked or not by using *if
> [ -d <folder-on-SD-card> ]*. I have downloaded a new version of cygwin in
> January, as I migrated to Windows 10 and was encountering some issues with
> it. Since I upgraded, this test is not working anymore. When the SD card =
is
> unlocked, testing " -d <folder> " returns TRUE. It returns FALSE when I do
> the same test on a non Bitlocker volume for a non-existent folder (which =
is
> the expected behaviour).

I'm not sure I understand.

You're testing with -d <non-existing-folder> if the drive is unlocked?
And you're expecting... what exactly?  The test should return FALSE in
all cases, regardless of the drive being locked or unlocked.

Sure, it sounds wrong if -d <non-existing-folder> returns TRUE, but
I wonder if I misunderstand what you're doing.

Can you rephrase this to make it more clear?

Also, can you create an strace of the wrong behaviour to see if there's
a certain error or NT status code which indicates the problem to be
handled more correctly?


Thanks,
Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--GdbWtwDHkcXqP16f
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlrYnZAACgkQ9TYGna5E
T6BRDA/9FNTov3xkAuseSPfwHrY89hWRN60XW0WpTstkNwu+OMmdKppov0q3P6ki
r3mGrVc/1fzLap4+A1yD9OpBsomSGj8IHQIdAdDjKOm8n1jjkXbFK0f4doim0JVq
/QJ/bdqFrUzBC0EOk3QidHk/ZaHmqcyq4z9sNrtjfHTKyvul4demjoCjy68jPM+R
I40vydHiwDlx7JfygsMwcq9Z5Yn158YOMjh42D5ypRQK2BM3CPMJQkIkwErNGi+D
NC91tbsSQraVLMAPILaKGQmnrZ13PWAOIfK4uFITHLnU+fVEw3S+kd1dP37HE16K
dSsHTQ69HyMtDViRz9MmRIATxtNao4xO2paR8pdmKWA0+qiFmeHubB9ZqKbxT+Ci
3++ibxMYUF2mkujGzZNGEtcHBkGnC2YU55swMLrKJ1Jy3X56x11+qDJFC9xD9bbc
o0qexDM9NRgxS/T++A1xPbzizkSF7LoIAaJwY4sBU6PHer+GOGzZbMwFP32R9bnB
EIE+mNc6GFQEGIh5IgYKYvqQ6B8rhgXZNji64T7jeZtokIVGcw1FXyifW+SgvABM
aKHIkv45fOSXz/YXuOV9izSLNSargPgQoVu3PVPLYUp1Efozb3myViFSsAAwtb6m
eM0rEIsAZ4Mn5czA2i0SU90E6PBcIDfDOxnzbPvwhyaV3V8+RgU=
=QlFm
-----END PGP SIGNATURE-----

--GdbWtwDHkcXqP16f--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019