public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michael Sowka" <msowka@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Potential bug in sshd
Date: Mon, 11 Sep 2006 16:57:00 -0000	[thread overview]
Message-ID: <91dd2cd50609110957x7e25808bp744ca708b6b8bbe0@mail.gmail.com> (raw)
In-Reply-To: <20060911162039.GA18381@trixie.casa.cgf.cx>

Sorry about the double-post everyone. Because I sent the first email
from a non list-registered address and assumed it wouldn't get
through, I resent it from the address that I actually registered with
Sorry, Mike

On 9/11/06, Christopher Faylor <cgf-no-personal-reply-please@cygwin.com> wrote:
> Please don't send the same message twice.
>
> On Mon, Sep 11, 2006 at 11:39:53AM -0400, Michael Sowka wrote:
> >... just when I thought I was nicely settled with WinXP and Cygwin
> >(being obligated to use Windows, cygwin makes the experience more
> >bearable ;) )...
> >
> >I don't consider myself a newbie, but we'll soon find out. I've
> >installed cygwin on a number of computers I frequently 'ssh'/'scp'
> >to/from. The setup is straight forward (time saving guide here:
> >http://pigtail.net/LRP/printsrv/cygwin-sshd.html). Other than the time
> >when I tried to change user groups manually and had to revert back to
> >get sshd working again, things have been running smooth.
> >[snip]
> >Problem reports:       http://cygwin.com/problems.html
>
> If you are having problems with the instructions you found at a web
> site you should contact the person responsible for the instructions:
>
> nfong AT pigtail DOT net.
>
> cgf
>

--
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/

  reply	other threads:[~2006-09-11 16:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 15:40 Michael Sowka
2006-09-11 16:20 ` Christopher Faylor
2006-09-11 16:57   ` Michael Sowka [this message]
     [not found] <000001c6d676$223a5110$0300a8c0@iPremise.local>
2006-09-12 14:17 ` Rob Bosch
2006-09-12 14:43   ` Michael Sowka
2006-09-12 14:50     ` Dave Korn
2006-09-12 18:15       ` Michael Sowka
2006-09-12 17:09     ` Tristen Hayfield
     [not found] <91dd2cd50609120741qbe4d430h84fab3eb3442b874@mail.gmail.com>
     [not found] ` <000101c6d684$3cd188f0$0300a8c0@iPremise.local>
2006-09-12 15:58   ` Rob Bosch
2006-09-12 16:50     ` Dave Korn
     [not found] <000201c6d68c$e70640b0$0300a8c0@iPremise.local>
2006-09-12 17:00 ` Rob Bosch

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=91dd2cd50609110957x7e25808bp744ca708b6b8bbe0@mail.gmail.com \
    --to=msowka@gmail.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).