| bio | website | yannesposito.com |
|---|---|---|
| location | France | |
| age | 36 | |
| visits | member for | 1 year, 10 months |
| seen | Aug 12 '11 at 8:29 | |
| stats | profile views | 1 |
- Ph.D in Machine Learning.
- Had programmed scientific programs in C++ and Java/Swing. About Probabilistic Automata and Edit Distance.
- Elaborated an anonymous network protocol similar to Tor.
- Use Python, Ruby.
- Website done with nanoc (static website generator that rocks). Use jQuery.
- Made some small Mac Screensaver and Dashboard widget. Some personal Mac Apps.
- Work as consultant in a Web/CMS/UNIX/Perl/J2EE environment.
|
Aug 12 |
awarded | Supporter |
|
Aug 12 |
awarded | Scholar |
|
Aug 12 |
accepted | How can I improve a password generation scheme based on a shared secret and URL? |
|
Aug 10 |
awarded | Editor |
|
Aug 10 |
revised |
How can I improve a password generation scheme based on a shared secret and URL? added 18 characters in body |
|
Aug 10 |
comment |
How can I improve a password generation scheme based on a shared secret and URL? @diedthreetimes I use this method to generate passwords. Each different for each website, but also easy to remember as I only have to remember only my master password. Which is not possible to do with random password generation. |
|
Aug 10 |
comment |
How can I improve a password generation scheme based on a shared secret and URL? How to keep secret the salt in an open source project? The only other way is to make the user choose the salt which seems to be exactly the same than to ask for a longer password. Am I wrong? |
|
Aug 10 |
comment |
How can I improve a password generation scheme based on a shared secret and URL? I didn't knew what I wanted to do is called stretching. And from what I read, it is indeed n times (in computer time) more difficult (if I use a good hash algorithm) to crack than the standard hash. |
|
Aug 10 |
awarded | Student |
|
Aug 10 |
comment |
How can I improve a password generation scheme based on a shared secret and URL? Of course, someone using this kind of method to generate password is aware that the master password must be very strong. But as the code is open source, salting isn't useful, simply because the salt will be public. I might had problem to explain myself, but for question 2, the attacker should have access to only the sha1(str), not str. |
|
Aug 10 |
comment |
How can I improve a password generation scheme based on a shared secret and URL? Thanks, the link is really helpful. I just hope I would find libraries to implement these in all the languages I need. |
|
Aug 10 |
comment |
How can I improve a password generation scheme based on a shared secret and URL? This is a way to create password for personal use (like bank website). |
|
Aug 10 |
comment |
How can I improve a password generation scheme based on a shared secret and URL? The idea is to use a large N. Just to make about 1 second on a standard computer. For what I understood, it is the idea behind bcrypt. |
|
Aug 10 |
awarded | Autobiographer |
|
Aug 10 |
asked | How can I improve a password generation scheme based on a shared secret and URL? |