Crauth

From VoidWarranties - Hackerspace Antwerp, Belgium
(Difference between revisions)
Jump to: navigation, search
Line 30: Line 30:
 
* responses revoke itself by time. (should be a little less obvious how the time is processed, to prevent forging new tokens from existing ones easily - needs rethinking if this is an issue)
 
* responses revoke itself by time. (should be a little less obvious how the time is processed, to prevent forging new tokens from existing ones easily - needs rethinking if this is an issue)
 
* doesn't require central storage for validation of codes (but is possible to add an extra layer of security, or to store data associated with the user which must be accessible by other apps/services)
 
* doesn't require central storage for validation of codes (but is possible to add an extra layer of security, or to store data associated with the user which must be accessible by other apps/services)
 +
 +
===Sample implementation===
 +
I worked out a sample implementation of this system:
 +
* first [[http://dl.dropbox.com/u/15854305/authcodegen.cs draft]] (2011-09-18) C#, compilable and runnable under Mono+.net .
  
 
==Barcode auth==
 
==Barcode auth==
Line 44: Line 48:
 
* small cards with your code on, for in a wallet
 
* small cards with your code on, for in a wallet
 
* requires central storage to validate tokens
 
* requires central storage to validate tokens
 +
 +
===Sample implementation===
 +
(to be added by [[Koert]] if required, otherwise discard this section.

Revision as of 14:41, 18 September 2011


Crauth
What:
Creating a simple authentication system without using a password which can be shared through multiple systems such as the barputer., and does not require specialized hardware to use.
Locked home.jpg
Participants:
Yvanj
Category:
Security
Locations:
Behind you desk, Den Bunker


Contents

Introduction

The goal of this project is to provide an easy-to-use authentication system which doesn't require a password. This comes in handy at the barputer (touch-based input), or other services not related to core management. The system should be easy to use, easy to implement, provide fair enough protection, and shouldn't require special tools or hardware.


Possible ideas

There were a few ideas, and this should be a summary of them. If the summary becomes too long, create a page/project for it.

Challenge/Response auth

Pros

Cons

Other details

Sample implementation

I worked out a sample implementation of this system:

Barcode auth

Pros

Cons

Other details

Sample implementation

(to be added by Koert if required, otherwise discard this section.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Content Creation
Belgian Spaces