Beruflich Dokumente
Kultur Dokumente
NAME STUDENT NO INTAKE MODULE CODE & TITLE PUBLICATION SUPERVISOR/ LECTURER DATE SUBMITTED
: : : : : : :
Page 1
Table of Contents
1.0 Gantt Chart 2.0 Introduction 3.0 Protocol Description 4.0 Protocol Model 5.0 Protocol Operation 6.0 Components of the Protocol 7.0 Strengths of the Protocol 8.0 Weakness of the Protocol 9.0 Relationship to Network Security 9.0 Description of Multimedia Tool Used 9.0 Conclusion 9.0 References 9.0 Appendices
3 4 5 5 6 8 10 11 12 14 15 15 16
Page 2
Page 3
2.0 | Introduction
Kerberos is a network authentication protocol that is designed to provide secure access between a client and server in an open or unsecure network. Kerberos developed as a tool to offer a backbone of a unified secure network at the Massachusetts Institute of Technology in the early 80s in a project called Athena. Research and Development was carried out through the collective funding effort of both IBM computers and Digital Electronic Corporation (DEC) and this saw the rapid development of the Protocol through the creation of varied modules and standards of providing secured access. Its through the advancements made in both the research and development of this protocol that saw it being readily accepted in to the market as the standard universal authentication protocol for the worlds computer networks. Different versions of the protocol have been in continual development and release as software suites to developers and several computer companies though the first three versions are reserved as proprietary standards at the Massachusetts Institute of Technology since they implement auxiliary military technology in their operational algorithm structure. Advancements in the development of the protocol have been made possible since MIT (Massachusetts Institute of Technology) offers the native source code to all developers who wish to advance or modify the algorithms of the protocol to suit their needs. This measure saw independent developers such as Steve Miller and Clifford Neumann collectively create a new version of Kerberos in the early 80s too. Developments in the native protocol have seen the creation of a stronger, more secure and reliable authentication protocol over the years and this measure has led to the main forefront computing companies such as Microsoft, Apple and Google deploying it in all their products and furthermore adopting it as a default authentication standard. Usage of the protocol is done through vending in that the companies that use the technology do so through acknowledgement of the copyrights stated by the Massachusetts Institute of Technology. This serves both as a licensing factor and also offers a ubiquitous channel of support since all the major stakeholders using the technology usually fund its research.
Page 4
Page 5
Page 6
Client -> File Server: Sends two Messages (E) and (G). Message (E) - Client to File Server Ticket. Message (G) - Authenticator (Client ID + Timestamp) -> Encrypted with Client Server Session key from F. F.S decrypts Message (E) gets Client ID and Network Address. F.S decrypts Message (G) using key obtained from Message (E). F.S checks that Client ID from E and G match. F.S checks that the validity period hasnt expired. File Server -> Client: Sends Message (H). Message (H) Timestamp found in (G+1) -> Encrypted with client server session key. Client now knows any message with (Timestamp +1) is from the server. Client can now communicate to the Sever through a secure connection. All in all, the Kerberos Protocol uses both cryptography and symmetric key mechanisms to achieve secure network connectivity. Knowledge of the secret key that is generated as one packet is routed from any object within the key distribution center is regarded as True identity. Aside from the protocol being used to authenticate clients and services within a common network, Kerberos can also be used to establish secure connections in an unsecured network where clients are not necessarily in the same network pool. In such instances, Cross Authentication occurs. Its implemented through both tokens and keys. Its also to be noted that since the Kerberos protocol uses fixed sets of time stamps to authorize clients to the server, the clock on the main Kerberos Server should always be accurate. Implementation of fixed time stamps is necessary in order to deter any client requests that might be using reply attacks. This further enhances secure interconnectivity. In order to foster reliable services on the Kerberos server, a secondary server known as a slave is needed. The slave server acts a backup to the main server and ensures that processing of the tokens and session keys are in line with the main central database. In this case, special Kerberos Software is installed on the main server in order to ensure all operations are concurrent. The Kerberos infrastructure is to be implemented in such a way that if the main server fails, the slave will automatically pick up. The clients should also configure the Kerberos file within their systems in order to facilitate secure access and seamless communication.
Page 7
Page 8
Session Key This refers to a special token pass that is generated within the key distribution center and servers to establish a secure connection between the client and services accessing the server at a particular time. This key is not long term as opposed to the other types of key generated during a session. Reply Cache This refers to a technique unique to Kerberos 5 that serves to deter imposters from using the same generated tickets and session keys for the purpose of accessing the server. It works by buffering a path to which the original tokens and keys will follow when being authenticated. Client This refers to a user or terminal that seeks to establish a connection to the server. Application Server This refers to the destination terminal which offers services to a client in a network. Stash File This refers to the array of disks that are resident within the database in the key distribution center.
Page 9
Page 10
4.2 | Weakness of The Protocol Server Limitation This occurs in the case where the Kerberos Server is down or isnt
functioning properly as it should. Authentication within the network ceases thus rendering the connections unsecure.
Cost In the case where an organization might be required to provide secure access
between the clients and the server over a wide area, more than one Kerberos server might be needed and might thus prove costly.
Clock Synchronization This occurs in since the client and server use timestamps as a
measure of providing secure connections within the network, the clocks of the clients must be at least within 10minutes of the Kerberos Server time.
This problem could easily be solved by ensuring that the clocks of both
the clients and the server workstations dont drift past 10minutes of each other in order to avoid conflict.
Page 11
Page 12
Page 13
Sample Output
Page 14
7.0 | Conclusion
Firstly, I would like to acknowledge my Lecturer for guiding me throughout the development of the project. She was very instrumental in ensuring that I followed the correct steps in making the program. Thanks Ms. Judy.
Secondly, I would like to acknowledge the spirit of cooperation that was shown by my classmates during the development of my research paper and prototype. They all proved essential since their ideas and critism helped me come up with a fairly competitive program that meet all the user requirements and offered even more.
8.0 | References
MIT Kerberos Consortium. (2008). Kerberos. Available: http://www.kerberos.org/software/whykerberos.pdf. Last accessed 10th Jan 2012. V. Alex Brennen. (2004-09-07). Kerberos Infrastructure. Available: http://cryptnet.net/fdp/admin/kerby-infra/en/kerby-infra.html. Last accessed 10th Jan 2012.
Page 15
General Machine Overview. Hardware. GNU/Linux Installation. Choosing a realm. Kerberos Software Configuration. Principal Creation.
Page 16
Single sign on for users. Operate within distributed systems based on an open Internet model. Integrate with existing technology. Mutual authentication of parties involved in information exchanged. Passwords should never be exposed during authentication. Central administration of authentication secrets. Use of cryptographic measure. Support arbitrary distribution of services and users. Trust no party until authenticated. Operate in a hostile environment.
Page 17
The rendered flash animation cannot be further edited since its locked and is exported after rendering as a common unit file. Editing is only possible on the original file which bears an .fls file extension. It should however be noted that for best viewing, the Adobe Flash Player installed on the host machine is up to date and is not corrupted since this might affect the overall working of the simulation.
Page 18