public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Seems like a bug with mkfifo -m
Date: Thu, 28 May 2020 20:17:29 +0200	[thread overview]
Message-ID: <20200528181729.GQ6801@calimero.vinschen.de> (raw)
In-Reply-To: <2f43f693-67dc-7211-d2af-3622b4ae98f3@cornell.edu>

On May 28 13:39, Ken Brown via Cygwin wrote:
> On 5/28/2020 1:31 PM, yoshi kakbudto wrote:
> > you say  'ls' is a problem source. Then i have to be more specific with the
> > problem to not miss any other possible problems around it.
> > 
> > My use case is this: I have an ssh rsa keys dynamically loaded in
> > environment variables.
> > Those variables then expaned and piped to the named pipe and then the pipe
> > instantly read by ssh-add.
> > I know there could be other ways to ssh-add from environment, but its just
> > our specifics.
> > So the actual commands looks like this:
> > 
> > $ mkfifo -m 0600 somefifo
> > 
> > # The KEY contains ssh rsa private key data
> > $ echo $KEY > somefifo | ssh-add somefifo
> > 
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
> > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> > Permissions 0644 for 'somefifo' are too open.
> > It is required that your private key files are NOT accessible by others.
> > This private key will be ignored.
> 
> Sorry, I shouldn't have said the problem was with ls.  The problem was
> actually with stat, and it's fixed now.  You should be able to test it the
> next time Corinna creates a snapshot.

Done.  Try the latest snapshot from https://cygwin.com/snapshots/


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

      reply	other threads:[~2020-05-28 18:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1895966314.19173483.1590653374238.JavaMail.zimbra@office.targem.ru>
2020-05-28  8:12 ` Дмитрий Есарев
2020-05-28 13:16   ` Ken Brown
2020-05-28 14:52     ` Corinna Vinschen
2020-05-28 15:28       ` Ken Brown
2020-05-28 17:35         ` Ken Brown
2020-05-28 17:31     ` yoshi kakbudto
2020-05-28 17:39       ` Ken Brown
2020-05-28 18:17         ` Corinna Vinschen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200528181729.GQ6801@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).