<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Otra cosa Fernando, <div><br></div><div>cuando dicen que no puede haber protocolos orientados a conexion sobre multicast, estudiaron los protocolos como los que se listan aqui: <a href="http://tldp.org/HOWTO/Multicast-HOWTO-9.html#sect-trans-prots">http://tldp.org/HOWTO/Multicast-HOWTO-9.html#sect-trans-prots</a></div><div>???</div><div><br></div><div>slds</div><div>r.</div><div><br></div><div><br></div><div><br><div><div>On Aug 14, 2008, at 3:47 PM, Fernando Gont wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>-----BEGIN PGP SIGNED MESSAGE-----<br>Hash: SHA256<br><br>Hola a todos,<br><br>El Centre for the Protection of National Infrastructure (CPNI) del Reino<br>Unido acaba de publicar el documento "Security Assessment of the Internet<br>Protocol", en el cual he trabajado durante estos últimos años.<br><br>Lo que motivó este trabajo se encuentra detallado en el prefacio del<br>documento, que dice:<br><br>- ---- cut here ----<br>The TCP/IP protocols were conceived during a time that was quite different<br>from the hostile environment they operate in now. Yet a direct result of<br>their<br>effectiveness and widespread early adoption is that much of today’s<br>global economy remains dependent upon them.<br><br>While many textbooks and articles have created the myth that the Internet<br>Protocols (IP) were designed for warfare environments, the top level goal<br>for the DARPA Internet Program was the sharing of large service machines on<br>the ARPANET. As a result, many protocol specifications focus only on the<br>operational aspects of the protocols they specify and overlook their<br>security implications.<br><br>Though Internet technology has evolved, the building blocks are basically<br>the same core protocols adopted by the ARPANET more than two decades ago.<br>During the last twenty years many vulnerabilities have been identified in<br>the TCP/IP stacks of a number of systems. Some were flaws in protocol<br>implementations which affect only a reduced number of systems. Others were<br>flaws in the protocols themselves affecting virtually every existing<br>implementation. Even in the last couple of years researchers were still<br>working on security problems in the core protocols.<br><br>The discovery of vulnerabilities in the TCP/IP protocols led to reports<br>being published by a number of CSIRTs (Computer Security Incident Response<br>Teams) and vendors, which helped to raise awareness about the threats as<br>well as the best mitigations known at the time the reports were published.<br><br>Much of the effort of the security community on the Internet protocols did<br>not result in official documents (RFCs) being issued by the IETF (Internet<br>Engineering Task Force) leading to a situation in which “known”<br>security problems have not always been addressed by all vendors. In many<br>cases vendors have implemented quick “fixes” to protocol flaws without<br>a careful analysis of their effectiveness and their impact on<br>interoperability.<br><br>As a result, any system built in the future according to the official<br>TCP/IP specifications might reincarnate security flaws that have already<br>hit our communication systems in the past.<br><br>Producing a secure TCP/IP implementation nowadays is a very difficult task<br>partly because of no single document that can serve as a security roadmap<br>for the<br>protocols.<br><br>There is clearly a need for a companion document to the IETF specifications<br>that discusses the security aspects and implications of the protocols,<br>identifies the possible threats, proposes possible counter-measures, and<br>analyses their respective effectiveness.<br><br>This document is the result of an assessment of the IETF specifications of<br>the Internet Protocol from a security point of view. Possible threats were<br>identified and, where possible, counter-measures were proposed.<br>Additionally, many implementation flaws that have led to security<br>vulnerabilities have been referenced in the hope that future<br>implementations will not incur the same problems. This document does not<br>limit itself to performing a security assessment of the relevant IETF<br>specification but also offers an assessment of common implementation<br>strategies.<br><br>Whilst not aiming to be the final word on the security of the IP, this<br>document aims to raise awareness about the many security threats based on<br>the IP protocol that have been faced in the past, those that we are<br>currently facing, and those we may still have to deal with in the future.<br>It provides advice for the secure implementation of the IP, and also<br>insights about the security aspects of the IP that may be of help to the<br>Internet operations community.<br><br>Feedback from the community is more than encouraged to help this document<br>be as accurate as possible and to keep it updated as new threats are<br>discovered.<br>- ---- cut here ----<br><br>El documento en cuestión se encuentra disponible en el sitio de CPNI:<br><a href="http://www.cpni.gov.uk/Products/technicalnotes/3677.aspx">http://www.cpni.gov.uk/Products/technicalnotes/3677.aspx</a><br><br>Saludos cordiales,<br>Fernando Gont<br><br><br><br><br><br>-----BEGIN PGP SIGNATURE-----<br>Version: PGP Desktop 9.5.3 (Build 5003) - not <br>licensed for commercial use: <a href="http://www.pgp.com">www.pgp.com</a><br><br>wsBVAwUBSKR9C2l+Jnd3SMmAAQgxnAf/YLIxsmYI8kx5f7yvjg8SHPIympTql6wQ<br>9uRayPbigeAR2qMsdq5hxnKw+ysYTnyrwdBuoOR8IdweFWQVzNc8oDxzP8qdU/qB<br>aOFKV24PXdeBND4oy9OIHHvJYRdE5PcGrDqi91BGwaBgJ//dQf39l9tbV28zvWgJ<br>Q+wAnJYGzMYr5HZb03GqojudvwBG68Cm2vdLEObelrDRIGhU34o/DvG/VOQG9Rys<br>yrikSH+PZlLwka92O5O09WIz3PjloL0xJPcwr8xMi9ikzxKfPOHsbA2SyW2ZkTOt<br>RECLQNV3GItmtmr4fjAc97pLrfmg9iWOHmpdGTHzYcbN17x2Wj/wJA==<br>=mzXy<br>-----END PGP SIGNATURE-----<br><br><br>--<br>Fernando Gont<br>e-mail: <a href="mailto:fernando@gont.com.ar">fernando@gont.com.ar</a> || <a href="mailto:fgont@acm.org">fgont@acm.org</a><br>PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1<br><br><br><br><br>_______________________________________________<br>Seguridad mailing list<br><a href="mailto:Seguridad@lacnic.net">Seguridad@lacnic.net</a><br>https://mail.lacnic.net/mailman/listinfo/seguridad<br></div></blockquote></div><br></div></body></html>