http://metawire.org/~sec/aesv3.zip

Everything else that doesn't fall into one of the other PB categories.
CherokeeStalker
User
User
Posts: 66
Joined: Fri Oct 17, 2003 2:42 am

http://metawire.org/~sec/aesv3.zip

Post by CherokeeStalker »

Can't download from this link. Can I get it somewhere else ?
sec
Enthusiast
Enthusiast
Posts: 792
Joined: Sat Aug 09, 2003 3:13 am
Location: 90-61-92 // EU or ASIA
Contact:

Post by sec »

CherokeeStalker
User
User
Posts: 66
Joined: Fri Oct 17, 2003 2:42 am

Post by CherokeeStalker »

That's v2, I'm trying to get v3. Check the link in my original post a little closer !
newbie
Enthusiast
Enthusiast
Posts: 296
Joined: Tue Jul 29, 2003 5:47 pm
Location: FRANCE
Contact:

Post by newbie »

Sec has said "work too", which means that V2 is perfectly working.
No one has the v3, I guess it has just speed optimization.

In the meantime V2 is perfectly working ;)
- Registered PB user -

Using PB 4.00
CherokeeStalker
User
User
Posts: 66
Joined: Fri Oct 17, 2003 2:42 am

Post by CherokeeStalker »

newbie wrote:Sec has said "work too", which means that V2 is perfectly working.
No one has the v3, I guess it has just speed optimization.

In the meantime V2 is perfectly working ;)
Oh, but if that's the case why make this post ?
viewtopic.php?p=66934#66934
Max.²
Enthusiast
Enthusiast
Posts: 175
Joined: Wed Jul 28, 2004 8:38 am

Post by Max.² »

CherokeeStalker wrote:
newbie wrote:Sec has said "work too", which means that V2 is perfectly working.
No one has the v3, I guess it has just speed optimization.

In the meantime V2 is perfectly working ;)
Oh, but if that's the case why make this post ?
viewtopic.php?p=66934#66934
That address me & newbie; not Sec. :wink:

It has nothing to do with the Lib itself and it's functions, but that the functions were used not really correct.

Both Sec's lib as my lib key expect a key to do the encryption successfully. But the way the key was _passed to the lib_ was not according to the standard. That was why I complained. BTW, it didn't really affect encryption but interoperability.

In other words; not the lib was wrong, but the usage of the lib. That was corrected a few postings later anyway and only concerned the AES_Crypt_File procedure.

Hope this clarifies it.
CherokeeStalker
User
User
Posts: 66
Joined: Fri Oct 17, 2003 2:42 am

Post by CherokeeStalker »

Thanks for clearing that up.
Post Reply