summaryrefslogtreecommitdiffstats
path: root/sys/crypto/rijndael
Commit message (Collapse)AuthorAgeFilesLines
* Make test00 compilable again.sobomax2008-01-152-1/+3
|
* Assert proper key size also in userland by defining KASSERT in !_KERNEL case.pjd2005-08-171-2/+2
|
* Unbreak the world build (in sbin/gbde). This file is used by bothcperciva2005-08-171-0/+2
| | | | | | | kernel and world, so KASSERT() needs to be wrapped within an #ifdef _KERNEL / #endif pair. Reported by: krion, tinderbox
* Check key size for rijndael, as invalid key size can lead to kernel panic.pjd2005-08-161-0/+2
| | | | | | | | | It checked other algorithms against this bug and it seems they aren't affected. Reported by: Mike Tancsa <mike@sentex.net> PR: i386/84860 Reviewed by: phk, cperciva(x2)
* gbde(8) is also rejndael user.ume2005-03-111-2/+0
| | | | Reported by: phk
* just use crypto/rijndael, and nuke opencrypto/rindael.[ch].ume2005-03-111-5/+0
| | | | | | the two became almost identical since latest KAME merge. Discussed with: sam
* integrate rijndael-alg-fst.h into rijndael.h.ume2005-03-115-44/+14
|
* stop including rijndael-api-fst.h from rijndael.h.ume2005-03-111-1/+0
| | | | this is required to integrate opencrypto into crypto.
* Start the dreaded NOFOO -> NO_FOO conversion.ru2004-12-211-1/+1
| | | | OK'ed by: core
* For variables that are only checked with defined(), don't provideru2004-10-241-1/+1
| | | | any fake value.
* avoid module name conflict with opencrypto/rijndael.c.ume2003-11-121-0/+0
| | | | Reported by: tinderbox
* cleanup rijndael API.ume2003-11-112-1/+107
| | | | | | | since there are naming conflicts with opencrypto, #define was added to rename functions intend to avoid conflicts. Obtained from: KAME
* rijndael-alg-fst.[ch]:ume2003-11-104-1634/+1332
| | | | | | | | | | | - redo updating. rijndael-api-fst.[ch]: - switch to use new low level rijndael api. - stop using u8, u16 and u32. - space cleanup. Tested by: gbde(8) and phk's test program
* Add a testcase which validates that the same buffer can be passed tophk2003-10-192-0/+87
| | | | | | | | | | rijndael_blockDecrypt() as both input and output. This property is important because inside rijndael we can get away with allocating just a 16 byte "work" buffer on the stack (which is very cheap), whereas the calling code would need to allocate the full sized buffer, and in all likelyhood would have to do so with an expensive malloc(9).
* - revert to old rijndael code. new rijndael code broke gbde.ume2003-10-194-1424/+1702
| | | | | - since aes-xcbc-mac and aes-ctr require functions in new rijndael code, aes-xcbc-mac and aes-ctr are disabled for now.
* Fix alignment problem on 64 bit arch.ume2003-10-141-0/+49
| | | | | | | I only tested if it doesn't break anything on i368. Since I have no 64 bit machine, I cannot test it, actually. Reported by: jmallett
* simplify and update rijndael code.ume2003-10-126-1737/+1407
| | | | Obtained from: KAME
* one more opossite conditiion.ume2003-09-181-1/+1
| | | | Reported by: "lg" <zevlg@yandex.ru>
* condition of padLen check was opposite.ume2003-09-171-1/+1
| | | | | Reported by: "lg" <zevlg@yandex.ru> Reviewed by: Lev Walkin <vlm@netli.com>
* Use __FBSDID().obrien2003-06-102-2/+6
|
* Don't panic when we can just return an error code.phk2002-10-141-2/+6
|
* Fixed AES encryption algorithm bugsuz2002-05-241-0/+1
| | | | | PR: kern/38465 Obtained from: Ramana Yarlagadda <ramana.yarlagadda@analog.com>
* Remove macros that are defined elsewhere.markm2002-04-211-2/+0
|
* less warningume2001-06-161-80/+80
| | | | warning: cast discards qualifiers from pointer target type
* Sync with recent KAME.ume2001-06-116-72/+127
| | | | | | | | | | | | | | | | | | This work was based on kame-20010528-freebsd43-snap.tgz and some critical problem after the snap was out were fixed. There are many many changes since last KAME merge. TODO: - The definitions of SADB_* in sys/net/pfkeyv2.h are still different from RFC2407/IANA assignment because of binary compatibility issue. It should be fixed under 5-CURRENT. - ip6po_m member of struct ip6_pktopts is no longer used. But, it is still there because of binary compatibility issue. It should be removed under 5-CURRENT. Reviewed by: itojun Obtained from: KAME MFC after: 3 weeks
* Kernel crypto need binary key material, not symbolic ascii.markm2001-03-101-0/+3
|
* Initial import of AES algorithm code (aka Rijndael) from KAME.kris2000-10-307-0/+2024
OpenPOWER on IntegriCloud