public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: "Dave Korn" <dave.korn@artimi.com>
To: "'Ssh-you-know-who!'" <cygwin-talk@cygwin.com>
Subject: RE: CYGWIN, changing default port
Date: Thu, 23 Jun 2005 12:06:00 -0000	[thread overview]
Message-ID: <SERRANO43IaSJHhnxN500000183@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <loom.20050623T130721-441@post.gmane.org>

----Original Message----
>From: Jim Hobbs
>Sent: 23 June 2005 12:10

> Hi there
> 
> Our sysadmin will not allow port 22 to be opened on our firewall.  

  The normal solution to this problem would be to drop a hippo on him.

> He has
> suggested we use one of the VNC ports already open for the SSH projects.

  <boggle>  Let me see if I've got this right: your sysadmin won't allow you
to bring SSH in through the firewall, but VNC is just fine?

  I think you'd better drop two hippos on him.

  He clearly needs to have some sense knocked into him.

> To this end I have chosen to use 5800 as we just use 5900 for the VNC
> programs. 
> 
> I have installed CYGWIN on a WinXP machine and it's working on port 22. 
> How can I change this to work with port 5800? Listening that is.

  Drop a hippo on it.[*]

> Thanks for any help :)

  No problem!

  BTW, why are you asking for technical advice on sshd on the hippo list?

    cheers,
      DaveK

[*]  Or read the sshd usage instructions which make it perfectly clear.
Just because it's a daemon doesn't mean you can't still run it from the
command line and pass "--help".
-- 
Can't think of a witty .sigline today....

  reply	other threads:[~2005-06-23 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 12:03 Jim Hobbs
2005-06-23 12:06 ` Dave Korn [this message]
2005-06-23 12:42   ` Jim Hobbs
2005-06-23 13:04     ` Corinna Vinschen
2005-06-23 14:20     ` One Angry User

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=SERRANO43IaSJHhnxN500000183@SERRANO.CAM.ARTIMI.COM \
    --to=dave.korn@artimi.com \
    --cc=cygwin-talk@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).