Click here to Skip to main content
16,018,949 members

Comments by Simon Bridge (Top 16 by date)

Simon Bridge 22-May-16 21:26pm View    
How can you tell?
Simon Bridge 19-May-16 23:17pm View    
The OP edited the question only a few days ago. Makes it current to my thinking.
Simon Bridge 19-May-16 23:15pm View    
Deleted
It was top of a list of questions without accepted answers, and I thought I could make a contribution .. easy mistake to make. You don't have to make a big deal out of it, and down-voting my answer was just petty .. was it actually wrong? obviously people are still reading this page and posting comments, so someone might have got something out of it. I still get and read comments posted against articles and questions I wrote years ago and they still provide useful information.
If you are so concerned about this and not just wandering the site looking for people to chastise, close the question out.
Simon Bridge 19-May-16 23:15pm View    
It was top of a list of questions without accepted answers, and I thought I could make a contribution .. easy mistake to make. You don't have to make a big deal out of it, and down-voting my answer was just petty .. was it actually wrong? obviously people are still reading this page and posting comments, so someone might have got something out of it. I still get and read comments posted against articles and questions I wrote years ago and they still provide useful information.
If you are so concerned about this and not just wandering the site looking for people to chastise, close the question out.
Simon Bridge 18-May-16 18:42pm View    
My point is that for anyone who wants to publish a symmetrical encryption algorithm, and have it generally accepted, there is an onus on the author of said algorithm to provide some proof, or reassurance, that information encrypted by this method will not be easily recovered without the key. This is never definite proof however.

There are common steps that are followed for any algorithm, regardless of its implementation, that measure the strength of the cipher. I know a few of these, but by no means do I have a complete understanding of the process. By asking this question I hoped to improve my knowledge and understanding and then be able to articulate that to my peers.

There really isn't room here to either post the code or describe in detail exactly how my simple example of a basic encryption scheme works, and because I want to know the process on a high level I find it would be counter-productive to do so.

For example (a poor one but the best I can think of right now) - if I wanted you to explain to me the road rules in your country, would you really need to know what make and model of car I was driving?

If you really want to know how it is implemented, I could email you the code or you could wait until the article comes out.

Apologies if I was rude before, and I appreciate that you put more effort into writing clearly, it does make a big difference. It's a personal bugbear of mine that so few people put effort into their written English. English is an ambiguous language at best, and when it is written down, you don't have the body language and tone of voice that makes up 70% of the communication, and you don't have the opportunity to say things differently or ask for a correction. So maybe I'm a bit twitchy on the subject and prone to impatience.

PS. You can always edit a comment after you posted it to remove typos if necessary. Just saying.