ssh -ö NOW!

SSH to Support Internationalized Domain-Names

German version of announcement

Since the advent of IDN in domain names, more and more system administrators and users are in the miserable situation of not being able to login to their umlaut-containing domains; respectively see themselves forced to find out the domains IDN representation by "whois" or other means. No more! Two swiss programmes managed in nightly work to patch ssh to support IDN. In order not to confuse english-only speakers, they cleverly invented a '-ö' -switch, which will turn on this IDN-support on the command-line. The patch for ssh is available as of april 1st on http://ssh.ösprö.ch.

Get the Patch

You can download the patch at ftp://ftp.linu.gs/software/openssh-idn/

Documentation

Read the

FAQ

  1. Why have you done this?

    Because the world is in desperate need of this. (And we had fun doing it)

  2. Is this the only reason?

    No. We also sought for a suitable use of IDN domains to legitimate their existence.

  3. Why -ö?

    Because we like ö.

  4. What can I do when ssh nags about a 'conversion error'?

    Read the README, luke! Try exporting a correct CHARSET environement variable: 

    $ export CHARSET=iso-8859-15

    Of course, you have to replace iso-8859-15 by your very charset.

  5. Where can I test it?

    We set up a test-account at ssh.ösprö.ch for you mates without a IDN domain: 

    $ ssh -ö foo@ssh.ösprö.ch

    But it cerainly works with your IDN third-level domains too!

  6. Who wants this anyway?

    It's not all US-ASCII out there (yes, Mr Bush). If you don't need it you're missing something.

  7. Is the use of ssh -ö an act of terrorism?

    Although it is possible to use ssh -ö for all kinds of characters appearing in even more languages this does not imply to mean ill.

    However it can be used to plunge your not-ö-enabled colleagues into depression.

Have fun!

seegras & cal, 1st of april 2006
Traffic and housing sopnsored by Hostpoint