[Chapter-delegates] dnssec as a solution to dns poisoning the national dns infrastructure (.ro)

Eduard Tric eduard.tric at isoc.ro
Thu Nov 29 00:48:14 PST 2012


Dear Borka,
We are exactly in the same situation with the .ro.
However, the situation is likely to change , as we explained to the press : 
http://translate.google.com/translate?hl=ro&sl=ro&tl=en&u=http%3A%2F%2Fwww.adevarul.ro%2Factualitate%2Ftech_and_it%2FRomania-usa_deschisa_pentru_hackeri_0_818918348.html
Maybe we can do something with Enisa or at EU level.
It is considered a matter of national security here.
Regads,
Ed

----- Mesaj original -----
De la: borka at e5.ijs.si
Către: "Peter Koch" <pk at ISOC.DE>
cc: "Eduard Tric" <eduard.tric at isoc.ro>, "Delegates Chapter" <chapter-delegates at elists.isoc.org>
Trimis: joi, 29 noiembrie, 2012 9:08:34
Subiect: Re: [Chapter-delegates] dnssec as a solution to dns poisoning the national dns infrastructure (.ro)


Thanks Ed  for the information.
We at ISOC SI are aware and I use any opportunity to express
my worry about the missing DNSSEC in Slovenia. Last time
during the ION ISOC conference in Ljubljana, October 19th  in  my
introductory talk.

However, the action must be taken by state owned Academic Network ARNES - 
the maintainer and holder of the TLD .SI, provider of IP services for cca 
50% of IP networks in Slovenia, including the whole governmental, health, 
cultural, education and research sector.

With regards,



Borka


On Wed, 28 Nov 2012, Peter Koch wrote:

> On Wed, Nov 28, 2012 at 08:12:36PM +0200, Eduard Tric wrote:
>> Today we've had a massive attack of .ro domains (google.ro yahoo.ro microsoft.ro , possibly others).
>
> indeed bad news, thanks for sharing the URLs.
>
>> How can we cooperate with other chapters to demonstrate to the Romanan Government the benefits of a dnssec secured cctld ?
>
> It is probably too early for this kind of conclusions.  Current status
> is still guessing <http://www.securelist.com/en/blog?weblogid=208194028>
> and sugegstions for an incident related to the provisioning system.
> I'm not taking any position and trust the RO TLD colleagues(*)
> to share information in appropriate channels.
>
> Meanwhile we should resist the temptation to advertise or advocate DNSSEC
> as a solution to problems it may not be able to mitigate.
>
> -Peter
>
> (*) disclosure/disclaimer: i work for, but do not speak for DENIC, the DE TLD
>    registry; so all this is in personal capacity as a chapter member
> _______________________________________________
> As an Internet Society Chapter Officer you are automatically subscribed
> to this list, which is regularly synchronized with the Internet Society
> Chapter Portal (AMS): https://portal.isoc.org
>

--

-- 

Eduard Tric ,CEO, Axetel 
I encrypt therefore I am.
http://www.axetel.com
eduard at axetel.com
tel: +40740300740
                                                                    
                                                                                
                               DD;;          
                              DDD;;;         
        We know,             DD  :;;        
    We compute,             fD    tt        
       We decode.           DD  fDf        
                             DDDDDD         
                              DDDD          
                               DD           
    ,    DD  DD DDDDDD DDDDDD DDDDDD DD     
    D    DD DDD DDDDDD DDDDDD DDDDDD DD     
   DDi   :DDDD   DD      DD    DD    DD     
   DDD    DDDD  DDDDDD   DD   DDDDDD DD     
  DDDDi   DDDD  DDDDDD   DD   DDDDDD DD     
  DD DD  tDGDD   DD      DD    DD    DD     
 DDi DD  DD fDD DDDDDD   DD   DDDDDD DDDDDD 
 DD   DD DD  DD DDDDDD   DD   DDDDDD DDDDDG 
                 DD                         
                DDDD                     
               DDDDDD                      
              GD:   DD                      
              ;;    DD                      
              :;;  GDf     We know                
               ;;;DDD   all the codes,                        
                ,;DG   including yours.

6839f52116af1166f4a01e64ad209459f17ecc995c1456a68c7040072a9a58d6



More information about the Chapter-delegates mailing list