From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 94244 invoked by alias); 13 Dec 2019 22:57:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 94237 invoked by uid 89); 13 Dec 2019 22:57:39 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=instantly X-HELO: mail-wm1-f43.google.com Received: from mail-wm1-f43.google.com (HELO mail-wm1-f43.google.com) (209.85.128.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 13 Dec 2019 22:57:38 +0000 Received: by mail-wm1-f43.google.com with SMTP id a5so468448wmb.0 for ; Fri, 13 Dec 2019 14:57:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=rquBcXtTYZSTbV5opGlDwDbwOvuOT0OeVAuYW+sHTfw=; b=D1Dhi4uTEYGV2oiKWuopAeV9uW2Y2b//O2DGYiPjlFwQCsWhSG2WrdLq0vgNmecjZQ zkOOovBK/+WwBY2CS+d6g7nxUDh4SRtqrFkQutRThsQMhnG2Evp/LYuYtxhwF+IXczk7 4jBvwu/rmZWkQ30MVHE27n/XLdIyYwmoyqjmEY0VZLjUxuUZsMxqLZMhO9pPRAGacWhn gEHd3EYA3eeyJEkjqgcbM/qjoHNXymjAa9IT2p1KL3ID3Xna4C0nVCkezqbL0HFAOEtE 8KDP9aovQRelgMm+HtOv39EVRYaTDqBKUdrpHBaCALRjmwm2WUBGB9rrxb6xYqIHFQnA MDCQ== MIME-Version: 1.0 References: <20191212220749.GB12864@tik.uni-stuttgart.de> In-Reply-To: From: Erik Soderquist Date: Sat, 14 Dec 2019 02:08:00 -0000 Message-ID: Subject: Re: non-persistent storage? To: "Buchbinder, Barry (NIH/NIAID) [E]" , cygwin Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00105.txt.bz2 On Fri, Dec 13, 2019 at 11:20 AM Buchbinder, Barry (NIH/NIAID) [E] via cygwin 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