Skip to main content

Thank you note

"A thank you note is the simplest form of showing gratitude". I am both humbled and honored that you have placed your confidence and support in me by electing me for the NRO NC Member and NIR SIG Co-Chair position.
I sincerely thank you for casting your valuable vote in my favor and making me win the election seeing all the required capabilities as a leader in me. I feel and believe that your support will boost my confidence to discharge my duties and responsibilities in a righteous manner.
I want to extend my special and sincere thanks for the immense support, valuable time and opportunity from Sh R.S. Mani (my boss), Dr Seema Khanna, Sh Anil Jain (CEO NIXI), Mr Tarun Dua (my mentor), Mr Vivek from Hapihhost, Sh Shailesh Gupta, Mr Naveen Sharma, Mr Anurag Bhatia, Mr Daryll Swer, Mr Abhishek Mishra, APNIC team and all others who supports me directly or in-directly by encouraging me to use my temperament in the right direction to give out the best result.
Thanking you once again!

Popular posts from this blog

Is APNIC policy of Members Voting Rights doing the Justice with NIRs and Corresponding Countries

APNIC (the Asia Pacific Network Information Centre) is the regional Internet address registry (RIR) for the Asia-Pacific region, service 56 economies, including India, Bangladesh, China, Australia, Japan and others. APNIC is one of the world's five RIRs and is part of the Number Resource Organization (NRO). As of date, the following 7 NIRs (National Internet Registries) are registered with APNIC for serving the local community a b c -- NIR Serving Economy Member under each NIR d APJII (ID) Indonesia 2916 e CNNIC (CN) China  1399 IRINN (IN) India  3368 JPNIC (JP) Japan   474 KISA (KR) Korea Not Available TWNIC (TW) Taiwan   299 VNNIC (VN) Vietnam   624 APNIC Membership is classified into 7 tiers depending on the IP holding by each member. Each membership tier has voting rights. These voting rights play a crucial role in governance and policies matt

Flaw in ServerKeyExchange messages of TLS Protocol

Here we will discuss the flaw in the ServerKeyExchange messages of the TLS protocol which caused the Logjam attack over TLS while using Diffie-Hellman Key Exchange. Before SSLv3, we don't use to authenticate the ServerKeyExchange messages where server negotiates with client regarding usage of cipersuite and parameters. From onwards SSLv3, TLS send the signed message where it mention about parameters it will use but remain silent over ciphersuite. Or in other words, signed portion contains parameters but not contain information about ciphersuite the server will going to use. Now just to remind you, the difference between DH and DH-EXPORT is the size of parameters only. So how to use this flaw - If the server supports DH-EXPORT, an attacker (Men-in-the-Middle) can edit the negotiation sent by the client (even if client doesn't support DH-EXPORT), and replace the list of client supported ciphersuite with DH-EXPORT only. The server will in turn send back a