views:

28

answers:

2

I was wondering whether a login system that implies that have to upload a certain file and then the server verifies that this is equal to the one stored in the server would be useful.

I was thinking that to its advantage, it would have that the "password" (the file) could be quite large (without you having to remember it).

Also it would mean that you would have to require a login name.

On the other hand one disadvantage would be that you would have to "carry around" the file everyone in able to login.

I dont want to turn this into a philosophical rather a programming one.

I´m trying to see the usability, safety/vulnerabilities etc

Is this or something similar done?

Thanks!!

+1  A: 

I am definitely not a security expert, but here are some thoughts.

This sounds somewhat similar to public key encryption. If you look into how that works, I think you will get a sense of the same sort of issues. For example, see http://en.wikipedia.org/wiki/Public-key_encryption

In addition to the challenge of users having to carry the file around with them, another issue is how to keep that file secure. What if somebody's computer or thumb drive is stolen? A common approach with public-key encryption is to encrypt the private key itself, and require a password to use it. Unless you provide the file in a form which requires this, you are counting on your users to protect the file. Even if you are willing to count on them, there is the question of how to give them the tools they need so they can protect the file.

Note that just like passwords, these files would be vulnerable if a user used one to login from a public machine (which might have all sorts of spyware on it). It's an open question whether a file-based system might slip under the spyware since they might not be looking for it. However, that is not so different from security by obscurity.

Also you would want to make sure that you hashed or encrypted the files on your system. Otherwise, you would be doing the equivalent of storing passwords in plain text which would open the possibility of someone hacking your system, and then being able to log in as any user.

Sid_M
@Sid_M Very interesting and enlightening perspective. Thats the thing with security procedures, there is not such thing as flawless. Thank you very much!
Trufa
+1  A: 

what you are saying can match to a physical factor of two factor (password + physical factor) authentication system. But it can not be a replacement of password, because password is something you know & file is something you have. Now if you turn the password into file you are losing one factor and somehow you have to compensate that :-) Maybe using something you are.

yadab
Thanks! Really interesting article!! (the two factor one)
Trufa