Discover and read the best of Twitter Threads about #DNSSEC
Most recents (5)
#ForumPAC:Forum du #Peering d'Afrique Central (#FPAC|#CAPF) en cours depuis ce matin (0700 UTC) et demain.
#IXP|s représentés:@DoualaIx,@CAMIXCameroun,@ixpgabix,@IspaDrc (#KinIX, ...),#CgIX & autres de la sous-région Afrique Centrale (AC).
internetsociety.org/fr/events/cent…
@AfPIF
#cmNOG
#IXP|s représentés:@DoualaIx,@CAMIXCameroun,@ixpgabix,@IspaDrc (#KinIX, ...),#CgIX & autres de la sous-région Afrique Centrale (AC).
internetsociety.org/fr/events/cent…
@AfPIF
#cmNOG
@nk_ghislain : "Comment mobiliser les acteurs non opérateurs réseaux (banques et autres) à rejoindre un Point d'Échange Internet local ?"
...réponse au #ForumPAC ;-)
@AfPIF
#cmNOG
...réponse au #ForumPAC ;-)
@AfPIF
#cmNOG
Journée #Josy sur le #DNS indico.mathrice.fr/event/286/
Premier à parler, @remasse (@AFNIC ) qui va exposer les grands principes.
Premier à parler, @remasse (@AFNIC ) qui va exposer les grands principes.
Résolution #DNS (« ça doit marcher 100 % du temps ») puis cycle de vie du nom de domaine (pensez au renouvellement) pour lequel, dans un .fr, on doit passer par un BE (Bureau d'Enregistrement).
#JoSy
#JoSy
L'évolution du .fr : très petit jusqu'en 2004 car enregistrement très restrictif (« nous avions fini par prendre un .com »)
Depuis les réformes de 2004 et 2006, .fr décolle. Bientôt 4 millions de noms.
Depuis les réformes de 2004 et 2006, .fr décolle. Bientôt 4 millions de noms.
Hello #NDSS20! That keynote was a ton of work to prepare, so I thought I'd squeeze some extra value of by posting key points from the talk here!
Here we go!
(For those of you at home, NDSS is one of the "big four" top-tier academic cybersecurity conferences.)
<thread>
Here we go!
(For those of you at home, NDSS is one of the "big four" top-tier academic cybersecurity conferences.)
<thread>
The focus of my talk was technology transfer.
How can we align incentives in the academic community, to encourage researchers to design systems that actually get used in the real world?
This is a key question in 2020, where infosec is everywhere.
How can we align incentives in the academic community, to encourage researchers to design systems that actually get used in the real world?
This is a key question in 2020, where infosec is everywhere.
Here are two metrics that I think should matter, when judging academic infosec research.
Notice that novelty is not on this list.
I don't think the community gives enough credence to these metrics.
Notice that novelty is not on this list.
I don't think the community gives enough credence to these metrics.
Open Wifi Security (Friday evening rant)
1) Yes, at our @nordic_choice hotels we have open wifi as standard. No Client<->AP encryption (WPA/23), and no captive portal to logon to.
Let me first explain some obvious reasons for doing so. (Often disregarded by infosec pros.)
1) Yes, at our @nordic_choice hotels we have open wifi as standard. No Client<->AP encryption (WPA/23), and no captive portal to logon to.
Let me first explain some obvious reasons for doing so. (Often disregarded by infosec pros.)
@Nordic_Choice 2) It is INCREDIBLY easy for anyone to connect and start using the Internet at our hotels. And we have absolutely all kinds of people staying with us. That includes people that are not tech-savvy at all.
@Nordic_Choice 3) Being a company who very actively seek to reduce our footprint on earth & measure our performance in "People, Planet & Profit" (not just profit), open wifi with no captive portal saves time, energy & money. It helps your mood as well. 😇
@Paul_IPv6 @letoams You're both repeating what I said, but that's fair if (though experiment:) you believe in some absolute truth in DNS - which is a common and understandable belief, because we tend to assume that there is only one DNS, only one system, and that it is global.
@Paul_IPv6 @letoams If you polytheisticly follow the thought experiment and admit is just "a system" rather than some omniscient and single store of truth ("the DNS is true, the DNS is one") then you are squarely back in the land of trusting your upstream priest/resolver. [typo fixed]
@Paul_IPv6 @letoams DNSSEC is nowhere, and we have no global truth to "rely" upon, and anyway if we did would probably be a bad thing to go around and blindly trust what our local DNS church simply tells us.
Lacking such, it's better to build a relationship with just one resolver, & use them.
Lacking such, it's better to build a relationship with just one resolver, & use them.
