06-01-2014, 04:06 PM
Graphical Password authentication system
Graphical Password .docx (Size: 109.41 KB / Downloads: 23)
ABSTRACT
Using the Form factor Card to saving and maintaining the patient’s recordsfrom birth to end of his life. Form factor Card has a microprocessor chip inside, enabling it to store information.Patient’s clearly identifiable by means of a photo and ID. This avoids the risk of misuse connected with conventional cards. Also eradicate fake doctors by registering their qualifications into the government and getting their unique ID.For security, patient data can only be read when patient and physician have been authenticated.
ABOUT THE PROJECT
A Graphical Password authentication system should encourage strong passwords while maintaining memorability. We propose that authentication schemes allow user choice while influencing users toward stronger passwords. In our system, the task of selecting weak passwords (which are easy for attackers to predict) is more tedious, discouraging users from making such choices. In effect, this approach makes choosing a more secure password the path of least resistance. Rather than increasing the burden on users, it is easier to follow the system’s suggestions for a secure password--a feature lacking in most passwords.
OBJECTIVES
The objective of my project is to prevent an unauthorized user from gaining access to confidential information of an individual or organization and to increase the performance of a knowledge-based authentication mechanism in security systems. Since existing graphical password schemes make use of larger memory space and require long-term password memorability, unlike this our security system provides higher level of security with less number of drawbacks.
To motivate administrators and employees to maintain the responsibility for, ownership of and knowledge about information security, in order to minimize the risk of security incidents. Ensure compliance with current laws, regulations and guidelines.
To ensure the availability and reliability of the network infrastructure and the services supplied and operated by concern. Ensure flexibility and an acceptable level of security for accessing information systems from off- campus. Ensure the protection of personal data (privacy)
EXISTING SYSTEM
The most common computer authentication method is for a user to submit a user name and a text password. The vulnerabilities of this method have been well known. One of the main problems is guessing attacks.
Studies have shown that users tend to pick short passwords or passwords that are easy to remember. Unfortunately, these passwords can also be easily guessed or broken.
PROPOSED SYSTEM
To address the problems with traditional username password authentication, alternative authentication methods, such as Graphical Password have been used.We propose that authentication schemes allow user choice while influencing users towards stronger passwords.Using a graphical password, users click on images rather than type alphanumeric characters. We have designed a new and more secure graphical password system, called Click Points.In our project we propose the concept of creating graphical password to provide secured authentication.This system solves the problem of remembering several click-points by replacing multiple image sequence with a single window containing a set of images.
Managed Code
The code that targets .NET, and which contains certain extra information - “metadata” to describe itself. Whilst both managed and unmanaged code can run in the runtime, only managed code contains the information that allows the CLR to guarantee, for instance, safe execution and interoperability.
Managed Data
With Managed Code comes Managed Data. CLR provides memory allocation and Deal location facilities, and garbage collection. Some .NET languages use Managed Data by default, such as C#, Visual Basic.NET and JScript.NET, whereas others, namely C++, do not.
Targeting CLR can, depending on the language you’re using, impose certain constraints on the features available. As with managed and unmanaged code, one can have both managed and unmanaged data in .NET applications - data that doesn’t get garbage collected but instead is looked after by unmanaged code.
Common Type System
The CLR uses something called the Common Type System (CTS) to strictly enforce type-safety. This ensures that all classes are compatible with each other, by describing types in a common way. CTS define how types work within the runtime, which enables types in one language to interoperate with types in another language, including cross-language exception handling. As well as ensuring that types are only used in appropriate ways, the runtime also ensures that code doesn’t attempt to access memory that hasn’t been allocated.
CONCLUSION
A common security goal in password-based authentication systems is to maximize the effective password space. This impacts usability when user choice is involved. We have shown that it is possible to allow user choice while still increasing the effective password space.
In Graphical Password Authentication creating a less guessable password (by selecting a click-point within the first few system-suggested viewport positions) is the easiest course of action.