From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: openssh: privilege separation no longer supported on Cygwin?
Date: Mon, 29 May 2017 14:29:00 -0000 [thread overview]
Message-ID: <9cdc0a4b3f27dfc196a19a6799f43880@xs4all.nl> (raw)
In-Reply-To: <20e2702ca3837f5d54c558f8e786c717@xs4all.nl>
On 2017-05-29 11:48, Houder wrote:
The following might help help clarify "my words" in my previous
post ... (pictures!)
https://security.stackexchange.com/questions/115896/can-someone-explain-how-sshd-does-privilege-separation
http://www.citi.umich.edu/u/provos/ssh/privsep.html
http://www.citi.umich.edu/u/provos/papers/privsep.pdf
(Niels Provos, Markus Friedl and Peter Honeyman, 12th USENIX
Security Symposium, Washington, DC, August 2003)
Regards,
Henri
--
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
next prev parent reply other threads:[~2017-05-29 12:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 6:40 Houder
2017-05-29 9:22 ` Marco Atzeri
2017-05-29 11:39 ` Houder
2017-05-29 11:44 ` openssh: privilege separation no longer supported on Cygwin? -- example only Houder
2017-05-29 14:29 ` Houder [this message]
2017-05-29 17:45 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! Houder
2017-05-29 20:30 ` Andrey Repin
2017-05-30 3:49 ` Houder
2017-05-30 16:16 ` Houder
2017-05-31 4:58 ` Larry Hall (Cygwin)
2017-05-31 10:51 ` Houder
2017-05-31 14:46 ` cyg Simple
2017-05-31 14:57 ` Houder
2017-05-31 14:59 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! -- minor correction Houder
2017-05-31 16:34 ` openssh: privilege separation no longer supported on Cygwin? SURPRISE! cyg Simple
2017-05-31 19:52 ` Houder
2017-05-31 20:16 ` cyg Simple
2017-06-01 2:27 ` Larry Hall (Cygwin)
2017-05-31 20:20 ` openssh: privilege separation no longer supported on Cygwin? Marco Atzeri
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=9cdc0a4b3f27dfc196a19a6799f43880@xs4all.nl \
--to=houder@xs4all.nl \
--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).