similar to: Regarding Trademark Dispute.

I'd like to address several issues raised by people in relation to my notice of the ssh(R) trademark to the OpenSSH group. Also, I would like to make a proposal to the community for resolving this issue (included at the end). First, I'll answer a number of questions and arguments presented in the discussion. > "the SSH Corp trademark registration in the US is for a logo

I would also like to mention that when I released TTSSH in May 1998, I had no concerns about violating any trademarks because I observed that the name "SSH" was already being used by several different parties for different purposes --- as the name of Ylonen's original SSH package and its derivatives, as the name of the protocol, and as a component of names of other implementations

Friends, Sorry to write this to a developer mailing list. I have already approached some OpenSSH/OpenBSD core members on this, including Markus Friedl, Theo de Raadt, and Niels Provos, but they have chosen not to bring the issue up on the mailing list. I am not aware of any other forum where I would reach the OpenSSH developers, so I will post this here. As you know, I have been using the SSH

On Solaris 10 (SPARC & x86), I'm seeing the following error: error: Failed to allocate internet-domain X11 display socket. I tracked this down to this code change between openssh 4.7p1 and 5.0p1: *** openssh-4.7p1/channels.c Mon Jun 25 03:04:47 2007 --- openssh-5.0p1/channels.c Wed Apr 2 15:43:57 2008 *************** *** 1,4 **** ! /* $OpenBSD: channels.c,v 1.270 2007/06/25 08:20:03

Here is a patch to scp made against openssh-2.1.1p2 that adds the -L option to scp. The -L option tells scp to use nonprivilaged ports (by passing ssh the -P option). The non-free ssh's scp has this option, and it is required under some firewall setups (like mine) for scp to function. Please let me know if there are any problems with this patch, or if there is anything I can do to help get

Dear SSH community, It has been brought to my attention that is has been disputed whether the term "SSH" can be used freely as a term to describe implementations compatible with the "SSH" protocols, due to trademark issues. In particular, the owner of the "SSH" trademark argues that implementations compatible with the "SSH" protocols shall no longer be

Hi, So I screwed up when writing the support for the curve25519 KEX method that doesn't depend on OpenSSL's BIGNUM type - a bug in my code left leading zero bytes where they should have been skipped. The impact of this is that OpenSSH 6.5 and 6.6 will fail during key exchange with a peer that implements curve25519-sha256 at libssh.org properly about 0.2% of the time (one in every 512ish

Hi, I usually stay away from issues like this, basically because I'm not a lawyer (and don't want to be one), and I don't have a real interest in these issues. Quoting Tatu : > We also have a trademark pending on the Secure Shell mark This seriously undermines the IETF standard draft. It's the same as registering 'milk' as a trademark. Both Secure and Shell are

A few people have commented that the synopsis in 'man 1 scp' is a bit difficult for humans to parse. I attach a diff between the distributed version and mine: (I suppose this should really go to the OpenBSD maintainers, but I wanted a little feedback about whether this was better or not.) Thanks, Andrew Stribblehill Systems Programmer, IT Service, University of Durham --------------

Hi, I applied the following minor diff to preserve the value of the extern variable across calls to process_sign_request2() in ssh-agent.c. I've no idea if the attachment of the attachment will come out correctly so a cvs diff is also attached. Regards, Alistair -------------- next part -------------- An embedded message was scrubbed... From: "Alistair G. Crooks" <agc at

Hi everyone. I want to point out some facts about TTSSH that may be relevant to the claims of trademark infringement by OpenSSH. I'll confine my opinions to another message :-). I released my product, which has always been named "Teraterm SSH" and is usually abbreviated to "TTSSH", to the public in May 1998. TTSSH is a free software Windows client for the SSH1 protocol.

Hi, I have made a patch which improves scp utility. It adds two new features: rate limit and resume support. With rate limit it's possible to limit transfer speed. Resume allows to continue file transfer where it was last interrupted. Also the progress meter was improved. Here is my patch, please send comments about it and what I can do better if there is something to fix. ---

Just thought I'd put my two cents in about the trademark infringement issue. I ran the true SSH for about a month some time back. When I learned of OpenSSH, I dropped the official product and built OpenSSH. Quite frankly, OpenSSH is a superior package. It is cleaner, commercially unencumbered, and with its affiliation to the OpenBSD team, I feel more secure about the code quality. When

-----BEGIN PGP SIGNED MESSAGE----- ###### ## ## ###### ## ### ## ## ###### ## # ## ## ## ## ### ## ###### . ## ## . ######. Secure Networks Inc. Security Advisory

I hate to open up a discussion that may already be closed (I haven't really followed the trademark dispute other than via the postings to NewsForge, and in particular the one on March 7), and I can't find on www.openssh.com an obviously more appropriate address to send this thought to, so.... [note my reply-to address] though the message below purports to come from <owner-ssh at

Hi, After reading the source code of openssh and man page of sftp. In sftp.h it define 27 /* 28 * draft-ietf-secsh-filexfer-01.txt 29 */ 30 31 /* version */ 32 #define SSH2_FILEXFER_VERSION 3 and In the end of the man page, T. Ylonen and S. Lehtinen, SSH File Transfer Protocol, draft-ietf-secsh-filexfer-00.txt, January 2001, work in progress material. In wikipedia of "SSH File

Hello, I have just installed OpenSSH 4.6p1 and it appears that ChallengeResponseAuthentication is not allowed unless I explicitly set it to "yes" in the sshd_config file. I am using the same config file as I did with 4.5p1 where it was allowed by default. Also, this is OpenSSH package from sunfreeware, but I believe that both versions were compiled with the same options. Is this the

'scp' returns a zero exit code, even if it fails to perform the desired task. bash-2.03$ scp nonexistent at no.such.domain:some/file .; echo $? ssh: no.such.domain: Name or service not known 0 'ssh' will however return a non zero exit code in a similar situation. bash-2.03$ ssh nonexistent at no.such.domain date; echo $? ssh: no.such.domain: Name or service not known 255

Hi, ssh-keygen is unable to change version 2 keys' comments (this was true in 2.9p2, and the changelog doesn't make me think this has changed), so I think this should be documented. Here's a patch to ssh-keygen.1 (It's based on an ssh-keygen patched with my previous patch). Cheers, Matthew --- ssh-keygen.1.orig Thu Sep 27 20:31:48 2001 +++ ssh-keygen.1 Thu Sep 27 20:40:32 2001

Hi folks XenSource published a trademark policy[1]. I don't think we will be able to follow it if we want to support installation of different versions at the same time. Bastian [1]: http://www.xensource.com/company/legal.html -- There are some things worth dying for. -- Kirk, "Errand of Mercy", stardate 3201.7 -------------- next part -------------- A non-text attachment was