public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "DePriest, Jason R." <jrdepriest@gmail.com>
To: cygwin@cygwin.com
Subject: Re: windows-to-windows openssh buffering issue
Date: Mon, 20 Jun 2011 14:28:00 -0000	[thread overview]
Message-ID: <BANLkTinW8Z93uWf7oeFeXzs3Zx+tqBqrLw@mail.gmail.com> (raw)
In-Reply-To: <4DFF4CF2.2020805@cygwin.com>

On Mon, Jun 20, 2011 at 8:36 AM, Larry Hall (Cygwin) <> wrote:
> On 6/19/2011 4:36 AM, Nathan Ridge wrote:
>> What I meant was, is it possible to write a different SSH server
>> implementation
>> for windows - perhaps a native one - that doesn't suffer from this
>> problem?
>> (And if so, do you know of one?) Or would all attempts at an SSH server
>> implementation run into this issue?
>
> ptys are a means to an end.  They are not a requirement to implement SSH
> or anything else for that matter, if that's what you're asking.  I'm not
> aware of many other SSH implementations on Windows.  MKS and SFU each
> have one.  I haven't used them though.
>
> --
> Larry

Tectia (owner of the ssh.com URL) sells a product that isn't based on
OpenSSH at all.  It isn't free or open source so you'll have to give
them money, but if you want to read up on it, here is their website:
http://www.tectia.com/en/en.iw3

It's been years since I've used it.  I used it before they changed
their name to Tectia but I'm pretty sure it is still SSH under the
hood.

-Jason

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

      reply	other threads:[~2011-06-20 14:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17  2:20 Nathan Ridge
2011-06-17 15:52 ` Larry Hall (Cygwin)
2011-06-18  9:25 ` Nathan Ridge
2011-06-19  3:31   ` Larry Hall (Cygwin)
2011-06-19  8:36   ` Nathan Ridge
2011-06-20 13:37     ` Larry Hall (Cygwin)
2011-06-20 14:28       ` DePriest, Jason R. [this message]

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=BANLkTinW8Z93uWf7oeFeXzs3Zx+tqBqrLw@mail.gmail.com \
    --to=jrdepriest@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).