Mail Archives: cygwin/2000/08/02/13:34:16
I'm definitely not the decision maker. We try to avoid as many trouble
as possible. As soon as we are _sure_ that we are allowed to upload
OpenSSH with full RSA to sources.redhat.com.
Corinna
Jon Maltz wrote:
>
> The RSA patent expires September 21st, expect to see many encryption
> programs relying on RSAREF to have new versions out around September 22nd.
>
> Export restrictions for encryption software that doesn't require a license
> payment seem to be gone, at the moment away --
> http://www.bxa.doc.gov/Encryption/qanda.htm
> Note the crystal clear language used in this document.
>
> Case in point, redhat distributes OpenSSH and OpenSSL RPMs on ftp.redhat.com
> ftp://ftp.redhat.com/pub/contrib/libc6/SRPMS/openssh-2.1.1p1-1.src.rpm
> ftp://ftp.redhat.com/pub/contrib/libc6/i386/openssl-0.9.5a-1.i386.rpm
>
> The web pages for those packages don't indicate if they use full RSA or
> RSAREF, and I suppose it's possible that redhat got a license for the RSA
> patent at some point in the past that might make that question moot. As it
> stands, since Corinna's version uses full RSA, it can't be downloaded by
> anyone in the USA without violating the RSA patent for the next seven
> weeks. After the patent expires, I'm not sure there would be anything
> preventing it from being hosted on a site in the US, until of course the
> next random encryption policy change.
>
> Jon
>
> I can only assume, not being a linux user myself, that this version of
> At 06:04 PM 8/2/2000 +0200, Corinna Vinschen wrote something like this:
> >James Dumser wrote:
> >> Am I misremembering or is there
> >> another reason your publishing on ftp.franken.de?
> >
> >Crypto export restriction, RSA patent etc.
> >OpenSSH will be released on sources.redhat.com perhaps next year.
> >
> >> >From your README:
> >> > - If you are installing OpenSSH the first time, you can generate
> >> > server keys and your own user keys by running
> >> >
> >> > /usr/local/bin/ssh-config
> >>
> >> Actually, it's not the first time; but it wasn't working before. I
> >> removed /usr/local/etc/ssh_host* files, renamed my ~/.ssh, and ran
> >> ssh-config. BTW, it would be nice if ssh-config created ~/.ssh if it
> >> didn't exist.
> >
> >ssh-keygen creates .ssh by itself.
> >
> >> inetd runs as the SYSTEM account. Your note (and my knowledge of NT) is
> >> not clear if SYSTEM already has the necessary permissions or not. I
> >
> >SYSTEM has all necessary rights. I thought this would be clear.
> >
> >> When I try to ssh to itself, I get
> >> debug: ssh_exchange_identification: sshd: no hostkeys available --
> >> exiting.
> >
> >From the sources I can see exactliy three possible reasons:
> >- v1.X protocol: Problem with rsa.
> >- v1.X protocol: No ssh_host_key file.
> >- v2 protocol: No ssh_dsa_host_key file.
> >
> >Try `sshd -d' from the command line. This might give you a hint.
> >
> >Corinna
> >
> >--
> >Corinna Vinschen Please, send mails regarding Cygwin to
> >Cygwin Developer mailto:cygwin AT sources DOT redhat DOT com
> >Red Hat, Inc.
> >mailto:vinschen AT cygnus DOT com
> >
> >--
> >Want to unsubscribe from this list?
> >Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> >
> >
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin AT sources DOT redhat DOT com
Red Hat, Inc.
mailto:vinschen AT cygnus DOT com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -