On 7 Jan 2015 20:31 -0500, from kevinsisco61...@gmail.com (Kevin):
> Great! You see at the verry least, we're getting some practice with
> these algorithms. I believe that this list is great for this.
You didn't answer my questions.
--
Michael Kjörling • https://michael.kjorling.se • mich...@k
On 1/7/2015 5:19 PM, Michael Kjörling wrote:
On 7 Jan 2015 22:11 +, from mich...@kjorling.se (Michael Kjörling):
Even if the rotation is bitwise
over the entire plaintext input, the value is bounded by 8 * L, where
L is the length in bytes of the plaintext input. For a full DVD (a
little ove
On 7 Jan 2015 22:11 +, from mich...@kjorling.se (Michael Kjörling):
> Even if the rotation is bitwise
> over the entire plaintext input, the value is bounded by 8 * L, where
> L is the length in bytes of the plaintext input. For a full DVD (a
> little over 4 GiB), that value is about 32 billion
On 7 Jan 2015 15:55 -0500, from kevinsisco61...@gmail.com (Kevin):
> Code:
> ;QODE(Quick Offline Data Encryption)
> ;by
> ;Kevin J. Sisco(kevinsisco61...@gmail.com
> ;provides strong encryption for data entered
> ;written in Autoit
> $i = Inputbox(" ", "Enter data")
> $b = StringToBinary($i)
> ;con
On 1/7/2015 3:32 PM, Warren Kumari wrote:
On Wed, Jan 7, 2015 at 3:09 PM, Kevin wrote:
On 1/7/2015 2:40 PM, Jeffrey Goldberg wrote:
On 2015-01-07, at 12:26 PM, Kevin wrote:
Any company could review it and decide if it's worth using or not.
Hi Kevin.
Actually that’s a part of my job w
On Wed, Jan 7, 2015 at 3:09 PM, Kevin wrote:
> On 1/7/2015 2:40 PM, Jeffrey Goldberg wrote:
>>
>> On 2015-01-07, at 12:26 PM, Kevin wrote:
>>
>>> Any company could review it and decide if it's worth using or not.
>>
>> Hi Kevin.
>>
>> Actually that’s a part of my job within the company I work
On 1/7/2015 3:05 PM, shawn wilson wrote:
On Wed, Jan 7, 2015 at 2:40 PM, Jeffrey Goldberg wrote:
On 2015-01-07, at 12:26 PM, Kevin wrote:
Any company could review it and decide if it's worth using or not.
Hi Kevin.
Actually that’s a part of my job within the company I work for. I’m the
On 1/7/2015 2:40 PM, Jeffrey Goldberg wrote:
On 2015-01-07, at 12:26 PM, Kevin wrote:
Any company could review it and decide if it's worth using or not.
Hi Kevin.
Actually that’s a part of my job within the company I work for. I’m the one who
can read some of the primary literature in c
On Wed, Jan 7, 2015 at 2:40 PM, Jeffrey Goldberg wrote:
> On 2015-01-07, at 12:26 PM, Kevin wrote:
>
>>Any company could review it and decide if it's worth using or not.
>
> Hi Kevin.
>
> Actually that’s a part of my job within the company I work for. I’m the one
> who can read some of the p
On 2015-01-07, at 12:26 PM, Kevin wrote:
>Any company could review it and decide if it's worth using or not.
Hi Kevin.
Actually that’s a part of my job within the company I work for. I’m the one who
can read some of the primary literature in cryptography. Now this makes me
unusual, not a
On 1/7/2015 1:46 PM, shawn wilson wrote:
On Wed, Jan 7, 2015 at 1:26 PM, Kevin wrote:
Any company could review it and decide if it's worth using or not.
Ok, lets run with that - as a company, show me the steps (make file, a
test suite in any programming language, or just english if you
p
On Wed, Jan 7, 2015 at 1:26 PM, Kevin wrote:
> Any company could review it and decide if it's worth using or not.
Ok, lets run with that - as a company, show me the steps (make file, a
test suite in any programming language, or just english if you
prefer), explain to me the steps one would g
here's what you have so far:
"
qode
An encryption algorithm
"
shall we conclude this thread now?
On Wed, Jan 7, 2015 at 12:26 PM, Kevin wrote:
> On 1/6/2015 6:32 PM, shawn wilson wrote:
>
>> So the practical reason behind everyone saying "unless you have
>> qualifications, etc, don'
On 1/6/2015 6:32 PM, shawn wilson wrote:
So the practical reason behind everyone saying "unless you have
qualifications, etc, don't do this" is because, even if you make
something and say it's just for your learning or a joke or w/e,
someone (no joke) *will* use it and then some Fortune 500 will
On 1/6/2015 6:25 PM, John Young wrote:
At 04:55 PM 1/6/2015, you wrote:
Yes, that is the received canon of cryptosystems:
1.Sarcasm toward unqualified efforts,
2. Designing cryptosysystems is *hard*.
3. No, that's too mild, it's mindblowingly* hard.
4. It doesn't start with code, it strts wi
On Tue, 6 Jan 2015, Kevin wrote:
> I figured I'd start building my own open source encryption algorithm:
And how many have you broken so far?
--
Dave Horsfall DTM (VK2KFU) "Bliss is a MacBook with a FreeBSD server."
http://www.horsfall.org/spam.html (and check the home page whilst you're there
Just use XXTEA. It's the only good cipher that allows for blocks of size
equal to that of a disk sector. Additionally, maybe use XXTEA in CTR mode
to provide additional confidentiality so that blocks with all zeroes won't
output to the same value.
On Tue, Jan 6, 2015 at 1:12 PM, Kevin wrote:
> I
The confidence in AES comes from its designation process during which
many publicly tried and failed to convincingly reduce its security
claim and the fact that it has (publicly still) stood the test of time
: ten years later all we have are the bicliques which gains us 2 bits.
It doesn't have much
If it's so foolish to build your own crypto, how foolish would a Fortune
500 company be to deploy it?
Too bad there's not a crypto hacker service to test out various crypto
algorithms. We're always told to trust the government-sponsored crypto
like AES when we know full well that governments
So the practical reason behind everyone saying "unless you have
qualifications, etc, don't do this" is because, even if you make
something and say it's just for your learning or a joke or w/e,
someone (no joke) *will* use it and then some Fortune 500 will fall
over because of your joke code. So, ye
Are you going to do this using recognised and proven primitives and
procedures (within the bounds of current knowledge) or create something
entirely new ?
Very different beasts...
On 07/01/2015 04:12, Kevin wrote:
> I figured I'd start building my own open source encryption algorithm:
> https://g
At 04:55 PM 1/6/2015, you wrote:
Yes, that is the received canon of cryptosystems:
1.Sarcasm toward unqualified efforts,
2. Designing cryptosysystems is *hard*.
3. No, that's too mild, it's mindblowingly* hard.
4. It doesn't start with code, it strts with mathematical description.
5. No, eve
On 6 Jan 2015 16:12 -0500, from kevinsisco61...@gmail.com (Kevin):
> I figured I'd start building my own open source encryption algorithm:
> https://github.com/kjsisco/qode
To borrow a very apt quote from Bruce Schneier: "Who the hell are
you?" [1] [2]
Nobody is perfect. Even very clever people m
Kevin wrote:
> I figured I'd start building my own open source encryption algorithm:
> https://github.com/kjsisco/qode
If you feel overwhelmed by the sarcasm directed your way, there is a
reason for that.
Designing cryptosystems is *hard*. No, that's too mild. Is
*mindblowingly* hard. It doe
yeah thx bra!
On Tue, Jan 6, 2015 at 3:25 PM, Warren Kumari wrote:
> On Tue, Jan 6, 2015 at 4:12 PM, Kevin wrote:
> > I figured I'd start building my own open source encryption algorithm:
>
> ... 'cos that can only end well?
>
> > https://github.com/kjsisco/qode
>
> The entire contents of which
On Tue, Jan 6, 2015 at 4:12 PM, Kevin wrote:
> I figured I'd start building my own open source encryption algorithm:
... 'cos that can only end well?
> https://github.com/kjsisco/qode
The entire contents of which is:
---
qode
An encryption algorithm
>
> --
> Kevin
>
>
> ---
>
26 matches
Mail list logo
