KSSL Case Study

777 Words 4 Pages
SSL: KSSL is a client side only implementation of SSLv3.0 Other versions, SSLv2.0 or SSLv3.1 (aka TLS1.0) are not currently supported since they are not used as frequently. The client only offers two cipher suites – RSA RC4 128 MD5 and RSA RC4 40 MD5 since they are fast and almost universally implemented by SSL servers from the very early days of the protocol. Client side authentication is not implemented because it is rarely used and requires (highly CPU intensive) private key RSA operations on the client. The server is authenticated via RSA signatures. There are no restrictions on the server 's certificate chain length. The client maintains an extensible set of trusted Certification Authorities. The SSL client supports session reuse, works on J2ME running on PalmOS, Solaris and Windows, and interoperates with SSL servers from iPlanet, Microsoft, Sun and Apache (using OpenSSL).
The main security activity in the area of transport layer is the Transport
…show more content…
Because of the global impact of such attacks, routing security is a critical issue for the whole Internet infrastructure. Attacks on routing protocols can cause legitimate traffic to flow over unsecure paths and create various types of security exposure for higher layer protocols ranging from eavesdropping to denial of service. Several routing protocols are used to exchange network topology and routing table information between routers. Commonly used intra-domain routing protocols are the Routing Information Protocol (RIP) and the Open Shortest Path First (OSPF). The Border Gateway Protocol (BGP) is the current inter-domain protocol used between the core routers on the Internet. The main security threats on routing protocols are route subversion through the exchange of bogus routing information and through the impersonation of

Related Documents