public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Harig, Mark" <maharig@idirect.net>
To: "Brian Ford" <ford@vss.fsi.com>, <cygwin@cygwin.com>
Subject: RE: Testers for new ssh-*-config scripts wanted!
Date: Fri, 31 Oct 2003 01:50:00 -0000	[thread overview]
Message-ID: <BADF3C947A1BD54FBA75C70C241B0B9E0145951D@ex02.co.idirect.net> (raw)

OK.  Thanks!  I will extract the contents
of the here documents and put them in
/etc/defaults/etc/sshd_config and 
/etc/defaults/etc/ssh_config.  I don't
trust my files in /etc/ to be vanilla
at this point.

> -----Original Message-----
> From: Brian Ford [mailto:ford@vss.fsi.com]
> Sent: Thursday, October 30, 2003 5:35 PM
> To: cygwin@cygwin.com
> Subject: RE: Testers for new ssh-*-config scripts wanted!
> 
> 
> On Thu, 30 Oct 2003, Harig, Mark wrote:
> 
> > I have OpenSSH 3.7.1p2-1 installed, but I
> > do not have the 'ssh_config' or 'sshd_config'
> > template files that the 'ssh-host-config' script
> > expects.  Am I missing a step here that I should
> > have taken to generate these files?
> >
> Yes, see:
> 
> > Corinna Vinschen wrote:
> > > Both scripts are attached.  When testing the new "copy 
> config files
> > > from /etc/defaults/etc" functionality, please think of copying the
> > > ssh_config and sshd_config files (if possible the vanilla 
> versions)
> > > to /etc/defaults/etc first.
> > >
> She meant the ones you would have in /etc if you had previously
> run the old ssh-host-config script.  If you had not, they can be found
> embeded in the old ssh-host-config script as mentioned here:
> 
> > > - /etc/ssh_config and /etc/sshd_config are not hardcoded 
> here-scripts
> > >   in the ssh-host-config script anymore, but they are copied and
> > >   modified from ssh_config and sshd_config files in 
> /etc/defaults/etc.
> > >   This allows to accomodate changes in the vanilla scripts without
> > >   having to change the shh-host-config script.
> > >
> 
> -- 
> Brian Ford
> Senior Realtime Software Engineer
> VITAL - Visual Simulation Systems
> FlightSafety International
> Phone: 314-551-8460
> Fax:   314-551-8444
> 
> --
> 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/
> 
> 

--
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:[~2003-10-30 22:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-31  1:50 Harig, Mark [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-30 22:58 Harig, Mark
2003-10-31  1:34 ` Brian Ford
2003-10-30 18:47 Harig, Mark
2003-10-30 18:07 Corinna Vinschen
2003-10-31  9:31 ` Philippe Torche
2003-10-31 11:20   ` Corinna Vinschen
2003-10-31 16:19     ` Philippe Torche
2003-10-31 18:09       ` Corinna Vinschen
2003-11-03  8:38         ` Philippe Torche
2003-11-03  8:51           ` 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=BADF3C947A1BD54FBA75C70C241B0B9E0145951D@ex02.co.idirect.net \
    --to=maharig@idirect.net \
    --cc=cygwin@cygwin.com \
    --cc=ford@vss.fsi.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).