DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 672DA388A030
MIME-Version: 1.0
References: <CA+7cx1pHS+=+h15rUZ5biSwKb=mxprMx7VadRRqm4Q4MYj+ewg@mail.gmail.com>
In-Reply-To: <CA+7cx1pHS+=+h15rUZ5biSwKb=mxprMx7VadRRqm4Q4MYj+ewg@mail.gmail.com>
Date: Sat, 4 Apr 2020 13:41:12 +0200
Message-ID: <CA+7cx1oXomuqvZLr1uNAbsdJ1M5M6cKgKsptJi0=C+TbGaCZaQ@mail.gmail.com>
Subject: Protecting .netrc
To: cygwin@cygwin.com
From: =?utf-8?q?Morten_Kj=C3=A6rulff_via_Cygwin?= <cygwin@cygwin.com>
Reply-To: =?UTF-8?Q?Morten_Kj=C3=A6rulff?= <mortenkjarulff@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

Hi.

No need to say that putting passwords in plain text file is a bad idea.
But if I use .netrc, wouldn't below be a bit (lot?) safer?
Assuming I have a good passphrase on my key.

It seems so simple, that I fear I am not getting anything out of it.

Morten

#!/bin/sh

# Install utils/gnupg2

# gpg2 --generate-key

# mkdir ~/secrets

# gpg2 -e -r YOU@EMAIL.COM <~/.netrc >~/secrets/netrc.enc

# rm ~/.netrc

# mkfifo ~/.netrc

while true ; do
  gpg2 -d <~/secrets/netrc.enc >~/.netrc
done
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple