DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=M0THoXn
	XFgF/B98XxeQxkwwR+PpilOjUxaqE6vsHVfV6Dw1zaPvWqNlDKo0U3uf9pNFnTEa
	RHtgPQCwNFbp2pnEwXLNvQeZrVu1wlsrU1Sq7OS55NoizzXlbeIvwNtz1IGovGY/
	pQz1omKvtEiQiMeAKG3TKFVnrhGbUkNEgCms=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
References: <BYAPR09MB29010912EBAE9D8F0196D35E9B550@BYAPR09MB2901.namprd09.prod.outlook.com> <20191212220749.GB12864@tik.uni-stuttgart.de> <CACoZoo1crFaE0ZHBVZaps+F93MyX1c4MN5-5awJ=jFmEAE2vnA@mail.gmail.com> <BYAPR09MB29010EDD6B0DA9BE871504959B540@BYAPR09MB2901.namprd09.prod.outlook.com>
In-Reply-To: <BYAPR09MB29010EDD6B0DA9BE871504959B540@BYAPR09MB2901.namprd09.prod.outlook.com>
From: Erik Soderquist <ErikSoderquist@gmail.com>
Date: Fri, 13 Dec 2019 17:57:23 -0500
Message-ID: <CACoZoo1CL_yp2fTFCK84937xL-2UBppGmtDyLhcdHNVvEYSnfA@mail.gmail.com>
Subject: Re: non-persistent storage?
To: "Buchbinder, Barry (NIH/NIAID) [E]" <barry.buchbinder@nih.gov>,
        cygwin <cygwin@cygwin.com>
Content-Type: text/plain; charset="UTF-8"

On Fri, Dec 13, 2019 at 11:20 AM Buchbinder, Barry (NIH/NIAID) [E] via
cygwin <cygwin@cygwin.com> wrote:
> One could put a script, batch file, or a link thereto in one's startup
> folder that will run on Windows' boot.

The OP's issue is that the data must be destroyed instantly even in
the event of a power failure.

Use case scenario:  thief breaks in and steals the host, just yanking
power cords/etc out, and then pulls the drive and mounts it on another
system to recover this data; it is sensitive enough that it must be
destroyed immediately by the power failure.

Unfortunately, nothing in Windows is designed for that kind of
security, and Cygwin has to work around a lot of Windows design flaws
to function in general.

I've test all of the suggestions I've seen so far with the exception
of the cygserver and shared memory, and all of the ones I've tested
failed the power failure scenario.  I think if the cygserver/shared
memory suggestion works, it will be the only available option to
prevent the data from default existing on the disc, and due to another
of Window's design flaws, may still be written into the page file,
though it would be much harder to cleanly extract from the page file
than from a normal filesystem file.

-- Erik

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple