SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG
DONATE


YUM REPOSITORY

 
 

MAN page from openSUSE Tumbleweed idnkit-1.0-262.1.x86_64.rpm

RUNIDN

Section: User Commands (1)
Updated: April 6, 2001
Index 

NAME

runidn - A script to allow applications to use internationalized domain names. 

SYNOPSIS

runidn [-e local-codeset] program-name [args..] 

DESCRIPTION

runidn enables applications to use internationalized domain nameswithout recompilation.Just add ``runidn'' before the application-name, and the applicationcan handle non-ASCII domain names. For example, you can do:

% runidn telnet non-ASCII-hostname

Before using runidn, you should set up properties related tointernationalized DNS by configuring idnkit's configuration fileidn.conf.See idn.conf(5) which describes the configuration. 

OPTION

The following option is available:
-e local-codeset
Specify the application's local codeset.If the option is not specified, runidn guesses the codesetfrom the current locale.See the ``NOTE'' section for more details about local codeset.
 

IMPLEMENTATION

runidn is a small shell script that sets up an environment variablecalled ``LD_PRELOAD'', so that an application dynamically links a sharedlibrary ``libidnkitres'' before any other shared libraries.

The library ``libidnkitres'' provides a special version of resolverfunctions which implement features for handling internationalizeddomain names.runidn replaces the following functions with the special version:

gethostbynamegethostbyname2gethostbyaddrgethostbyname_rgethostbyname2_rgethostbyaddr_rgetipnodebynamegetipnodebyaddrfreehostentgetaddrinfofreeaddrinfogetnameinfo

By overriding them in the standard libraries with the special versionprovided by ``libidnkitres'',runidn enables applications to use internationalized domain names.

*
These API functions accept non-ASCII domain names encodedin the local codeset that the application is using.Also the result from these APIs may contain non-ASCII domain names.
*
The normalization and codeset conversion between application's localcodeset and the codeset used in DNS protocol data are handledautomatically, so users/applications need not worry about them.

Properties of internationalized DNS (such as the normalization orthe codeset used on DNS protocol data) can be configured with theidnkit's configuration file (idn.conf).See idn.conf(5) for details. 

NOTE

Unless -e option is specified, runidn tries to guessthe application's local codeset from the application's current locale.However, sometimes it cannot guess the codeset correctly, for exampleif the application does not set the locale appropriately by calling`setlocale()'.In that case, you can explicitly specify the local codeset by setting anenvironment variable ``IDN_LOCAL_CODESET''.See the section ``LOCAL CODESET'' in idn.conf(5) for details.

The idea of using ``LD_PRELOAD'' to replace some functions in the standardlibrary was taken from ``runsocks'' script distributed as part of SOCKS5reference implementation. 

BUGS

There are many cases where runidn does not work.

Your system must support ``LD_PRELOAD'' mechanism in the first place.

Due to security reasons, ``LD_PRELOAD'' mechanism is disabled forsetuid programs in any sane systems.So runidn does not work for setuid programs such as ping or rsh.

If your application uses a function other than the ones runidn supports forname resolution, you lose. 

SEE ALSO

idn.conf(5), runsocks(1)


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTION
IMPLEMENTATION
NOTE
BUGS
SEE ALSO

This document was created byman2html,using the manual pages.