[Snippet] sbox

[Nestharus]

This resource has moved here.

--

gone

 

[Blarto]

wonder if it's possible for a better syntax to swap values in the box..

lets say I wanted to use a different box.. I'd have to rewrite the whole thing.. making this rather more useless to jass than it is right now.

maybe there's a way to abuse /* */ + comment new line removal + string parser + 2D arrays here.

hashtable + stringhash sounds more natural than arrays.. also..

 

[Nestharus]

You don't want to change the box... the sbox is the sbox : \.

 

[Blarto]

Actually I want to change the box.. to a different sbox scheme. Ended up rewriting the whole thing. Cool story, though.

 

[Nestharus]

er... you do realize that changing the sbox to something else weakens the encryption... everybody uses the same sbox.

 

[Blarto]

you're using a 16 by 16. Standard stuff.

I'm talking about defining a custom size 8 by 8 ... 32 by 32.. etc + it's contents (i.e instead of defining 0xXX + XbyY array calls, just put string and parser parses it).

But not sure if vjass syntax can support it easily, otherwise we are stuck with rewriting this.

Strong encryption for anything a wc3 map generates not possible unless you can hash the map file itself WHILE running the map. But that's beside the point.

 

[Nestharus]

hm...

8x8 would have less possible permutations, so that shouldn't really be done. 32x32 would be interesting, but you'd need to link a 32x32 sbox. Well, you could generate it using the math I suppose.


I hardcoded it as I figured everyone would use 16x16. That's pretty standard.

Read up on here to generate them dynamically -> http://en.wikipedia.org/wiki/Rijndael_S-box

 

[Blarto]

I'm trying to be constructively critical here, probably not very good at it

Between you and me, nobody else will probably use this, and I already have a similar thing like this. Heck, doubt even 5 people on here will understand what this is without looking up a wiki.

I used 64x64 because I was lazy and didn't want to deal with B64->B16->B64 BS. Weakness from this is irrelevant.. strong cipher not possible.. we have a nasty loophole.

However a syntax for defining 2D arrays would be sexy and solve all these kinds of problems (i viewed your other resources)

ex:

String row1 = "00,01,aa,bb, .. etc"
String row2 = "ba,66,11, ..etc"

 

[Nestharus]

Just generate it dynamically and it'll be strong ; ). Look at the wiki article >: o.

 

[Nestharus]

regenerated with c++