Language Selection

English French German Italian Portuguese Spanish

Domain Hijacking Takes ICANN Spotlight

Filed under
Security

The report, announced Wednesday during an international meeting of the ICANN (Internet Corporation for Assigned Names and Numbers) in Luxembourg, followed at least two high-profile incidents this year of what is known as domain-name hijacking.

The committee advises the domain-name system overseer's board of directors and constituents such as the registrars that sell domain names to individuals and business and the registries that manage domains such as .com and .net.

Committee members expressed optimism that the report will lead to swift action, but it was still unclear as of late Wednesday whether ICANN's board planned to address the report's findings and recommendations at its meeting later this week.

The report left ICANN's recently changed policy for the transfer of domain names without blame in domain hijacking, although others in the domain-name industry have raised concerns that the change will fuel more stolen domain names. The new policy had focused on streamlining the process of transferring a domain.

The ICANN committee recommended 10 fixes for hijacking, which ranged from more public awareness and a domain-name emergency hotline to potentially stricter verification of the identity of domain-name holders and better record keeping of registrations.

One technical recommendation focused on the use of registrar locks and domain-name holder passwords. The report suggests that registrars use locks, which prevent a domain-name change until the name holder unlocks the name, and consider using a specification called "authInfo," which essentially password protects a domain name.

Currently, the authInfo password is not available for .com or .net, both of which are managed by VeriSign Inc. But VeriSign has said it plans to add the support, according to the report. Other domains, such as .org, .biz and .net, use the passwords.

Full Story.

More in Tux Machines

Leftovers: Ubuntu

Leftovers: Software

today's howtos

Phoronix on NVIDIA

  • Compute Shader Support Patches For NVIDIA Fermi On Nouveau
    Samuel Pitoiset has published a set of twelve patches for implementing compute shaders support within the Nouveau NVC0 Gallium3D driver for the GeForce 400/500 "Fermi" graphics processors.
  • NVIDIA Posts Latest PRIME Sync Patches On Road To Better Support
    Alex Goins of NVIDIA has spent the past several months working on PRIME synchronization support to fix tearing when using this NVIDIA-popular multi-GPU method. The latest patches were published this week.
  • The Best Graphics Card Brands For NVIDIA/AMD GPUs As A Linux Consumer?
    One of the most frequent topics I'm emailed about is any brand recommendations among NVIDIA and AMD AIB partners for graphics cards. For Linux users, is there a particular brand preference for graphics cards? The short story is, no, there isn't one particular brand when selecting either a GeForce or Radeon graphics card that a Linux gamer/enthusiast should go with over another AIB partner. Over the past 12 years of running Phoronix, there has been no single AIB partner that superbly stands out compared to the rest when it comes to graphics card AIB partner brands like ASUS, Zotac, HIS, MSI, etc. They all work under Linux, rarely the AIB differences extend beyond the heatsink/cooler and any default clock speed differences, and I haven't seen one that's over-the-top crazy about Linux. I also haven't seen any major partner consistently put the Tux logo or other Linux markings on their product packaging, let alone incorporate any Linux drivers onto their CD/DVD driver media.