| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Approved by: cognet
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Shut it up.
|
| |
|
|
|
|
| |
Suggested by: njl
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Such an address can be used directly in padlock's AES.
This improves speed of geli(8) significantly:
# sysctl kern.geom.zero.clear=0
# geli onetime -s 4096 gzero
# dd if=/dev/gzero.eli of=/dev/null bs=1m count=1000
Before: 113MB/s
After: 203MB/s
BTW. If sector size is set to 128kB, I can read at 276MB/s :)
|
|
|
|
| |
aligned, it will be used directly, not 'address + 16'.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
new VIA CPUs.
For older CPUs HMAC/SHA1 and HMAC/SHA256 (and others) will still be done
in software.
Move symmetric cryptography (currently only AES-CBC 128/192/256) to
padlock_cipher.c file. Move HMAC cryptography to padlock_hash.c file.
Hardware from: Centaur Technologies
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
them twice.
This is possible for example in situation when session is used in
authentication context, then freed and then used in encryption context
and freed - in encryption context ses_ictx and ses_octx are not touched
at newsession time, but padlock_freesession could still try to free them
when they are not NULL.
|
|
|
|
|
|
|
|
| |
instead of probing again.
Adjust style(9) somewhat in probe.c
Reviewed by: pjd
MFC after: 1 week
|
|
|
|
| |
Reported by: Rong-en Fan <grafan@gmail.com>
|
|
|
|
|
|
|
|
| |
with fast_ipsec(4) and geli(8) authentication (comming soon).
If consumer requests only for HMAC algorithm (without encryption), return
EINVAL.
- Add support for the CRD_F_KEY_EXPLICIT flag, for both encryption and
authentication.
|
|
|
|
| |
Return an error instead of encrypting/decrypting data with a wrong key.
|
| |
|
|
|
|
|
|
| |
HW donated by: Mike Tancsa <mike@sentex.net>
Most of the code obtained from: OpenBSD
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
kernel and world, so KASSERT() needs to be wrapped within an #ifdef
_KERNEL / #endif pair.
Reported by: krion, tinderbox
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
Reported by: phk
|
|
|
|
|
|
| |
the two became almost identical since latest KAME merge.
Discussed with: sam
|
| |
|
|
|
|
| |
this is required to integrate opencrypto into crypto.
|
| |
|
| |
|
| |
|
|
|
|
| |
OK'ed by: core
|
|
|
|
| |
80386 (I386_CPU) support from the kernel.
|
|
|
|
| |
any fake value.
|
| |
|
| |
|
|
|
|
| |
Reported by: tinderbox
|
|
|
|
|
|
|
| |
since there are naming conflicts with opencrypto, #define was
added to rename functions intend to avoid conflicts.
Obtained from: KAME
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
|
|
|
|
| |
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).
|
|
|
|
|
| |
- since aes-xcbc-mac and aes-ctr require functions in new
rijndael code, aes-xcbc-mac and aes-ctr are disabled for now.
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Requested by: sam
|
| |
|
|
|
|
| |
Reported by: tinderbox via kris
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
|
|
| |
smaller footprint.
Obtained from: KAME
|
|
|
|
| |
Reported by: "lg" <zevlg@yandex.ru>
|
|
|
|
|
| |
Reported by: "lg" <zevlg@yandex.ru>
Reviewed by: Lev Walkin <vlm@netli.com>
|
|
|
|
| |
Found by: Juergen Buchmueller <pullmoll@stop1984.com>
|
| |
|