network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 8 months |
| seen | Sep 4 '12 at 17:14 | |
| stats | profile views | 8 |
|
May 11 |
awarded | Nice Question |
|
Feb 12 |
awarded | Notable Question |
|
Dec 17 |
awarded | Popular Question |
|
Sep 4 |
accepted | What number of bits does a browser use to generate a key? |
|
Aug 30 |
awarded | Commentator |
|
Aug 30 |
comment |
Understanding 2048 bit SSL and 256 bit encryption Thanks for the details, @AJ! |
|
Aug 30 |
comment |
Is it okay to just secure (using SSL) the login page, but not the rest of the site? Thanks AviD. I've actually been pretty active on SO (different login), so I'm quite familiar with using the site. I guess I slipped when it came to this one. Sorry about that, but got some good answers out of it. :) |
|
Aug 30 |
comment |
Is it okay to just secure (using SSL) the login page, but not the rest of the site? For those interested in this topic, I found another great answer on StackOverflow: stackoverflow.com/questions/1211638/… |
|
Aug 30 |
accepted | Is it okay to just secure (using SSL) the login page, but not the rest of the site? |
|
Aug 30 |
awarded | Supporter |
|
Aug 30 |
comment |
What number of bits does a browser use to generate a key? excellent info! Thanks for the link to the other post as that answers another question I had. |
|
Aug 30 |
asked | Is it okay to just secure (using SSL) the login page, but not the rest of the site? |
|
Aug 30 |
comment |
What number of bits does a browser use to generate a key? Great, thank you @AJ! |
|
Aug 30 |
comment |
Understanding 2048 bit SSL and 256 bit encryption Great info! However, wouldn't the tougher algorithm imply a greater level of security? I'm referring this part in your answer, "That said, because the algorithm is based on something that is simply really hard to figure out (but is solvable), it is less secure than a symmetric algorithm based on a shared secret (more on that later). " |
|
Aug 30 |
comment |
Understanding 2048 bit SSL and 256 bit encryption @CodesInChaos: I agree, but maybe it is useful? Given the accepted answer below, my question is how would the client know to generate a random 256 bit key? (Why not 128?). If the server plays a role in the client's decision, then I can understand why the vendor would display this info. |
|
Aug 30 |
asked | What number of bits does a browser use to generate a key? |
|
Aug 30 |
comment |
Understanding 2048 bit SSL and 256 bit encryption Ignore that question - I get it now. I combined your answer with the one in this post: security.stackexchange.com/questions/13688/… Thank you! |
|
Aug 30 |
awarded | Scholar |
|
Aug 30 |
accepted | Understanding 2048 bit SSL and 256 bit encryption |
|
Aug 30 |
comment |
Understanding 2048 bit SSL and 256 bit encryption Thank you! Can you clarify this part: "the client generates a random 256-bit key"? In this case, the client is the browser? If so, does the ad mean to say that the root encryption is for the handshake portion and the 256 bit is for the data encryption? Hope I'm getting this. |
