meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 11 months |
| seen | May 11 at 5:26 | |
| stats | profile views | 317 |
The first rule of security is: you do not invent security protocols.
The second rule of security is: you do not invent security protocols!
The third rule of security is: if this is your first time with security you do not invent security protocols.
Inventing, modifying, tweaking, hacking, extending, optimizing, or just about anything else you can do to a cryptographic protocol, hash, algorithm, PRNG, key agreement, or cryptographic technique is a very bad idea.
(Not dead.)
|
Jun 27 |
revised |
windows wiki excerpt added 207 characters in body |
|
Jun 27 |
suggested | suggested edit on windows tag wiki excerpt |
|
Jun 27 |
wiki | created windows excerpt |
|
Jun 27 |
comment |
Most secure password hash algorithm(s)? No, cryptographic hash algorithms are designed to be one-way functions that make it difficult for an attacker to modify a piece of data while keeping the hash value the same. The one-way function is designed to make it difficult to determine how a change in input will impact the output hash value. Fundamentally cryptographic hashes are lossy compression functions. The information loss in compression makes it difficult to recover the input data. Design specs for MD5, SHA1, Whirlwind, etc, do not mention confidentiality, because is not a design goal. |
|
Jun 27 |
revised |
attacks wiki description added 234 characters in body |
|
Jun 27 |
revised |
attacks wiki excerpt added 58 characters in body |
|
Jun 27 |
revised |
operating-systems wiki excerpt added 421 characters in body |
|
Jun 27 |
suggested | suggested edit on attacks tag wiki excerpt |
|
Jun 27 |
suggested | suggested edit on attacks tag wiki |
|
Jun 27 |
wiki | created attacks description |
|
Jun 27 |
wiki | created attacks excerpt |
|
Jun 27 |
suggested | suggested edit on operating-systems tag wiki excerpt |
|
Jun 27 |
wiki | created operating-systems excerpt |
|
Jun 27 |
comment |
Theorical question on encryption methods I'm confused. The diagram shows two instances of Client1. Do you want to act as an information sharing broker? Allowing Client1 to share data with Client2 and Client2 to share data with Client1. However, this can be done with existing PKI with no intermediary. Are you generating data for the clients? |
|
Jun 27 |
comment |
Detection and analysis of unknown malware Very nice answer. Pitty you don't know that IDA Pro has a 5.0 freeware version it includes support for x86 and PE. That should pad your toolkit. |
|
Jun 27 |
comment |
Can ipopts be used to circumvent a pf or iptables firewall source IP based blocking? Do you mean using dc0 on the same machine as the pf or iptables? |
|
Jun 26 |
comment |
Sharing passwords and credentials between founders and employees It would help to describe: what resources you are trying to access/control access to, who you want to share with (are they all your employees?), why you are sharing (in case Alice is sick), and the value of the things you are protecting (helps identify how much security you need). |
|
Jun 26 |
comment |
Sharing passwords and credentials between founders and employees Yes, I think you are leading to Role Based Access Control. Where people are given access based on their role, not their individual identity. |
|
Jun 26 |
comment |
Most secure password hash algorithm(s)? Hash algorithms are not designed to protect the confidentiality of passwords, which are short, but to quickly verify the integrity of medium to large chunks of data. Note that hashes are designed to protect integrity and not confidentiality. Encryption algorithms are designed to protect confidentiality of data. Hashes are used to protect password confidentiality because they are quick, easy, and do not require a separate key. The selection of slower hash function is an odd but understandable approach to avoiding the need for an encryption key. |
|
Jun 26 |
awarded | Tag Editor |
