Updates: Captcha Customizer v1 - Angles

The Captcha Customizer Angles rotation design is created. Users can change the values in the textfield and resulting changes will bw shown in the preview graph.

Updates: Captcha Customizer v1 - Position

The Captcha Position customizer design is created. User can change the values in the textfield and effect of the new values will be shown in the graph.

Updates: Captcha Customizer v1

Captcha Customizer v1 is developed.



The screenhot above is the mainframe the user will see when he/she launches the customizer. The "Epic 4 Security" logo has an effect whereby when the user clicks on it, the system default web browser will open automatically and bring the user to the "Epic 4 Security" web site.

Technical: Applet Servlet Communication

We decided that the "New Captcha" will be implement in a Java3D interactive game form which requires interaction with the user. The only way is perhaps through a Java Applet...

Now what worry us is whether can applet talk to servlet?

Heaven's on our side. We found a nice example showcasing Applet and Servlet communication. It shows how data is sent to a servlet from an applet and how the applet receive an answer from the servlet.

http://www.frank-buss.de/echoservlet/index.html

More comments will be added once we get the hang out of the codes.

Updates: End of Session Debrief

We had our first presentation yesterday. Thanks everyone for the effort you have put in. Everything was smooth, no cock-ups and we made our delivery as targeted. These are the questions arrowed to us during the presentation. We will brainstorm it during the weekend and will have this on our Agenda for this coming Monday's group meeting (04 Feb 2008).

1) RUP - How we apply to our project?

2) Show a Attack on our Captcha.

3) How we prevent OCR attacks (Prove it. How it actually done it)

4) How we prevent brute force (Prove it.)

5) How are we better than market's Captcha (Prove it)

6) Either Text/Picture Captcha or Extra picture with Text? (Blur ?!?)

Technical: Image Format

The captcha image output by the servlet have been change to Portable Network Graphics (PNG) instead of JPEG File Interchange Format (JPG).

Meeting: 30 JAN 2008 (w/ supervisor)

Session 1 Technical Report Review
ALAN checking with supervisor regarding the system flow diagram, use case diagram and content listings.

Below are the feedback from Supervisor :

System flowchart
- Should not have breakdown of function calls
- If there is input into a particular function, indicate it using text and arrow direction, do not use function block to indicate
- Advisable to include a brief explanation for the flow

CAPTCHA flow chart
- Change to sequence diagram
- include sequence number
- Advisable to include a brief explanation for the sequence

Use case diagram
- should have 2 users
*Customer
*Administrator for maintaining the product

OCR readings records acquired from product testing.
Sebastian checking with supervisor regarding which section of the technical report should we include the OCR reading result acquired from product testing.

OCR readings records can be either under
- Test plans
- Conclusions
- Product analysis

Brute force attack calculation.
Team checking with Supervisor regarding the brute force attack information.

Below are the calculation explained by Supervisor:
CAPTCHA text is formed by 8 characters with a choice of 46 characters in each position.

46 pow 8 = 20,047,612,231,936 sample space

To get brute force attack computation time required:

(sample space /2) . time taken

time taken = time needed by our system in order to validate a single end user’s answer.

Time taken is to the time needed by our system in order to validate a single end user’s answer.

Discuss with Supervisor regarding Session 1 presentation.
Supervisor reviewed the contents of team presentation slides and feedback :

- RUP methodology should be explained briefly.
- Highlight the differences between our CAPTCHA and those in the market
- Advisable to show the calculation of the brute force attack on our CAPTCHA.
- Advisable to explain the resources used to generate our CAPTCHA image
- Advisable to demo or show some OCR readings on our CAPTCHA
- Suggested using a wireless modem to provide access point to allow mobile phones to connect to.
- Advisable to provide handouts for final presentation


Progress Report submission by team leader
Sebastian submitted Progress Report for session 1 to Supervisor. Some of the suggestion by Supervisor regarding the report format.

- Advice to show our process base on gantt chart that we proposed in proposal.
- Advice to write a summary of what we have done in phase 1.
- Advice to write what we are going to do in phase 2.

Additional CAPTCHA design features suggestion.
LEXIS suggested include additional CAPTCHA feature which allow customers to edit the CAPTCHA design effects to suite their application. Supervisor has reviewed and will confirm with Adrian Choo to see whether the adding feature will be considers as part of the project scope or is the extra features.- Supervisor advice team to come out with a non-text based CAPTCHA in order to score high points.

New CAPTCHA design suggestion.
LEXIS suggested to design a animated CAPTCHA which require end users interaction. It requires end users to use the mouse pointer to point the path in order for an object X to move from A to B. In the meantime, there will be some objects like rock or tree which might block the object X from moving in a straight path. Hence it need end users to find a way in order to reach B which only human can do.

But this design will not be able to apply to mobile devices usage. Supervisor will confirm with Adrian Choo regarding the new design suggested which it only allows to run in computer platform.