From: yoshi kakbudto <ed@office.targem.ru>
To: cygwin@cygwin.com
Subject: Re: Seems like a bug with mkfifo -m
Date: Thu, 28 May 2020 10:31:18 -0700 (MST) [thread overview]
Message-ID: <1590687078818-0.post@n5.nabble.com> (raw)
In-Reply-To: <c117921e-388a-2ac2-dd95-3d66a6dae5be@cornell.edu>
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.
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
next prev parent reply other threads:[~2020-05-28 17:31 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 [this message]
2020-05-28 17:39 ` Ken Brown
2020-05-28 18:17 ` Corinna Vinschen
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=1590687078818-0.post@n5.nabble.com \
--to=ed@office.targem.ru \
--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).