Secure Shell Will Remain 'SSH'
cdlu sent in a follow-up to the SSH dispute - the IETF has rejected a request from SSH, the company, to change the name of SSH, the protocol. This will save a lot of people from typing 'ln -s /usr/bin/secsh /usr/bin/ssh'.
KlausBreuer,
I'd like to ask you to change your login name. Your name infringes on my trademark. I know this is an inconvenience for you, but I would greatly appreciate it. Please?
-----------------
And I'll bet you wouldn't do it, no matter how nice the request.
Why should the IETF inconvenience MILLIONS of users so that a single individual can profit?
They decided not to change the usage of the word SSH as the name of the protocol. What OpenSSH decides to call its binaries is an entirely different decision that the IETF has nothing to do with.
For the record, the decision in the room was somewhat split, leaning about 2:1 towards not changing the name. It's still unclear if the name will be trademarked in the documents, which was the second (replaced?) request made to the IETF secure shell working group.
The next site to slashdot will be ready soon, but subscribers can beat the rush and start slashdotting it early!
He could win. Several months ago (and I don't have time to find the link) a domain name had to be given up by its holder even though the ICANN arbitration held that he didn't. The person who wanted the name just sued in US court for trademark infringement, and won. You see, the IETF decisions are not binding in the courts. So Ylonnen could sue for trademark infringement. If he won, it would not matter what the IETF said.
Best Slashdot Co