similar to: More on TTSSH and the SSH trademark

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.

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 received the following e-mail in response to an e-mail I had sent to SSH communications questioning the wisdom of their requesting OpenSSH to change it's name. Contained in the message is that statement that SSH Communications did not exert their trademark rights earlier becuase it's only recently that OpenSSH has become more visible. In the United States, this would invalidate the

http://bugzilla.mindrot.org/show_bug.cgi?id=368 Summary: TTSSH will not connect to OpenSSH_3.4p1 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: NetBSD Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

http://bugzilla.mindrot.org/show_bug.cgi?id=368 ------- Additional Comments From mindrot at regs.nebcorp.com 2002-07-24 12:16 ------- Just make life easier: TeraTerm 2.3 http://hp.vector.co.jp/authors/VA002416/ttermp23.zip TTSSH 1.5.4 plugin http://www.cs.cmu.edu/~roc/ttssh154.zip ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the

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

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=368 ------- Additional Comments From djm at mindrot.org 2003-05-14 22:59 ------- Please retest with a recent release, some of the older releases had OpenSSL issues. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=368 ------- Additional Comments From djm at mindrot.org 2002-09-10 21:52 ------- Created an attachment (id=143) --> (http://bugzilla.mindrot.org/attachment.cgi?id=143&action=view) Patch to add pid to logs This is a quick patch to display the pid of the logging process. It may be helpful in debugging privsep problems. ------- You are

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

-- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle -------------- next part -------------- Wine Weekly News All the News that Fits, we print. Events, progress, and happenings in the Wine community for March 05, 2001 .

-- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle -------------- next part -------------- Wine Weekly News All the News that Fits, we print. Events, progress, and happenings in the Wine community for March 05, 2001 .

A non-text attachment was scrubbed... Name: not available Type: application/pgp Size: 3562 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20010214/5489bfec/attachment.bin

The OpenSSH project turns five years old ---------------------------------------- Five years ago, in late September 1999, the OpenSSH project was started. It began with an audit, cleanup and update of the last free version of Tatu Ylonen's legacy ssh-1.2.12 code. The project quickly gathered pace, attracting a portability effort and, in early 2000, an independent implementation of version 2

The OpenSSH project turns five years old ---------------------------------------- Five years ago, in late September 1999, the OpenSSH project was started. It began with an audit, cleanup and update of the last free version of Tatu Ylonen's legacy ssh-1.2.12 code. The project quickly gathered pace, attracting a portability effort and, in early 2000, an independent implementation of version 2

It's been brought to my attention that Mozilla will be changing their implementation of <video/> to default deny cross-site requests. (http://www.w3.org/Bugs/Public/show_bug.cgi?id=6104) In other words: <video src="http://someothersite/videos.ogg"/> Will not work by default. It will not work like the <img/> tag does, or like the embed/object tags do which are

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

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