Comments on: Authentication over a network http://blogs.gnome.org/rbultje/2009/04/11/authentication-over-a-network/ Random thoughts Fri, 30 Oct 2009 01:15:34 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: Chris Hills http://blogs.gnome.org/rbultje/2009/04/11/authentication-over-a-network/comment-page-1/#comment-237 Chris Hills Wed, 15 Apr 2009 16:15:31 +0000 http://blogs.gnome.org/rbultje/?p=184#comment-237 Since you are specifically authenticating a mobile phone, I would suggest a one-time pad delivered via SMS. The user registers their mobile phone number, and when they require access, the server sends a code via SMS which the user then copies into the client application. The Google SMS gateway would have been ideal for this, unfortunately it was shut down due to abuse from a certain iPhone application. Since you are specifically authenticating a mobile phone, I would suggest a one-time pad delivered via SMS. The user registers their mobile phone number, and when they require access, the server sends a code via SMS which the user then copies into the client application. The Google SMS gateway would have been ideal for this, unfortunately it was shut down due to abuse from a certain iPhone application.

]]> By: me http://blogs.gnome.org/rbultje/2009/04/11/authentication-over-a-network/comment-page-1/#comment-236 me Wed, 15 Apr 2009 07:53:40 +0000 http://blogs.gnome.org/rbultje/?p=184#comment-236 Bluetooth-type authentication does not have to violate your second requirement, if you implement bluetooths 'discoverable' status. So on one of the devices, you set the device to be discoverable. The device shows you some kind of code. The other device now can see the first device, you type in the code and they connect. As long as the implementation is correct (make sure you use secure random numbers) this works reasonably seamless and secure. The only thing that can happen is a man-in-the-middle attack and that would require the attacker to intercept all communication, which is rather impractical. Bluetooth-type authentication does not have to violate your second requirement, if you implement bluetooths ‘discoverable’ status. So on one of the devices, you set the device to be discoverable. The device shows you some kind of code. The other device now can see the first device, you type in the code and they connect.

As long as the implementation is correct (make sure you use secure random numbers) this works reasonably seamless and secure. The only thing that can happen is a man-in-the-middle attack and that would require the attacker to intercept all communication, which is rather impractical.

]]> By: Johannes Berg http://blogs.gnome.org/rbultje/2009/04/11/authentication-over-a-network/comment-page-1/#comment-235 Johannes Berg Sat, 11 Apr 2009 19:44:46 +0000 http://blogs.gnome.org/rbultje/?p=184#comment-235 Maybe see http://en.wikipedia.org/wiki/Wi-Fi_Protected_Setup for some ideas. It's implemented in wpa_supplicant now, but I don't know about any UIs. Might not solve your problem at all, but maybe some of the methods could be usable -- I don't know off-hand, just seemed like WPS is like what you need. Maybe see http://en.wikipedia.org/wiki/Wi-Fi_Protected_Setup for some ideas. It’s implemented in wpa_supplicant now, but I don’t know about any UIs. Might not solve your problem at all, but maybe some of the methods could be usable — I don’t know off-hand, just seemed like WPS is like what you need.

]]> By: Pierre http://blogs.gnome.org/rbultje/2009/04/11/authentication-over-a-network/comment-page-1/#comment-234 Pierre Sat, 11 Apr 2009 19:35:15 +0000 http://blogs.gnome.org/rbultje/?p=184#comment-234 What about a dialog in the desktop application that would show a random 4 digits code that you would have to type in any client you want to allow ? What about a dialog in the desktop application that would show a random 4 digits code that you would have to type in any client you want to allow ?

]]>