From: "René Berber" <r.berber@computer.org>
To: cygwin@cygwin.com
Subject: Re: sshd
Date: Thu, 20 Apr 2006 19:22:00 -0000 [thread overview]
Message-ID: <e28mi7$dpn$1@sea.gmane.org> (raw)
In-Reply-To: <4447CE4D.7070204@elementcxi.com>
Steve Kelem wrote:
> The instructions for sshd (/usr/share/doc/openssh/README.privsep)
The first instructions you should read are those in
/usr/share/doc/Cygwin/openssh.README; if you follow those you use
ssh-host-config and ssh-user-config which take care of setting everything else
so you don't have to ask what is below.
> include the following:
>
> You should do something like the following to prepare the privsep
> preauth environment:
>
> # mkdir /var/empty
> # chown root:sys /var/empty
> # chmod 755 /var/empty
> # groupadd sshd
> # useradd -g sshd -c 'sshd privsep' -d /var/empty -s /bin/false sshd
>
> I used XP's Manage/User Accounts to add a group called sshd.
> When I tried to create a user "sshd", it complained, saying that the
> group already exists.
>
> 1. Which package has "useradd" and "groupadd"?
None.
> 2. Is it possible to create sshd:sshd?
No, Windows doesn't allow a group name that is equal to a user name.
But to make things clear, you don't need to do any of the above if you use the
provided script.
--
René Berber
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2006-04-20 19:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-20 18:49 sshd Steve Kelem
2006-04-20 19:22 ` René Berber [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-13 2:25 sshd Ernie Rael
2022-02-13 5:29 ` sshd Mark Geisert
2022-02-13 6:30 ` sshd Russell VT
2022-02-13 12:42 ` sshd Ernie Rael
2022-02-13 12:38 ` sshd Ernie Rael
2022-02-13 19:59 ` sshd Erik Soderquist
2022-02-14 6:56 ` sshd Andrey Repin
2022-02-14 7:42 ` sshd Ernie Rael
2022-02-15 17:20 ` sshd Gajanana Shridhar
2010-05-13 20:08 sshd Steven Collins
2010-05-13 20:12 ` sshd Eric Berge
2010-05-13 20:18 ` sshd Steven Collins
2010-05-13 20:32 ` sshd Eric Berge
2010-05-13 20:38 ` sshd Steven Collins
2010-05-13 20:17 ` sshd Andrew Dunstan
2010-05-13 20:31 ` sshd Steven Collins
2003-10-15 14:52 sshd e-bone
2003-10-15 15:32 ` sshd Larry Hall
2002-12-18 13:25 sshd Harig, Mark A.
2002-12-18 10:19 sshd Vince Hoffman
2002-12-18 9:21 sshd Vince Hoffman
2002-12-18 9:03 sshd Vince Hoffman
2002-12-18 8:00 sshd Stuardo Rodriguez
2002-07-02 19:53 sshd Bryan Zimmer
2002-07-03 1:39 ` sshd Corinna Vinschen
2002-07-03 8:01 ` sshd Bryan Zimmer
2002-07-03 8:53 ` sshd Corinna Vinschen
2002-03-02 13:23 sshd Erik Vigmostad
2002-03-04 8:37 ` sshd Larry Hall (RFK Partners, Inc)
2001-05-31 0:46 sshd Warunee Noiarun
2001-05-31 3:03 ` sshd Corinna Vinschen
2001-03-16 15:07 sshd Bret Jordan
1999-04-13 12:10 SSHD Gerhardstein, Lawrence H
1999-04-30 18:32 ` SSHD Gerhardstein, Lawrence H
[not found] <862566DC.00528EDA.00@marker.its.uiowa.edu>
1998-12-16 16:28 ` SSHD JJ Streicher-Bremer
1998-10-13 12:17 sshd Juha Jäykkä
1998-01-07 14:50 sshd Derek Young
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='e28mi7$dpn$1@sea.gmane.org' \
--to=r.berber@computer.org \
--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).