Searched hist:1.1269 (Results 1 - 11 of 11) sorted by relevance

/src/sys/dev/pci/
H A Dpcidevs_data.h1.1269 Sun Jan 15 04:44:01 GMT 2017 msaitoh branches: 1.1269.2;
regen.
1.1269 Sun Jan 15 04:44:01 GMT 2017 msaitoh branches: 1.1269.2;
regen.
H A Dpcidevs.h1.1269 Sun Jan 15 03:49:43 GMT 2017 msaitoh regen.
H A Dpcidevs1.1269 Mon Oct 24 06:03:52 GMT 2016 msaitoh Add Xeon E7 v4 devices from "Intel Xeon Processor E7 v4 Product Famliy
Datasheet Volume 2: Registers".
/src/doc/
H A D3RDPARTY1.1269 Thu Dec 17 22:32:41 GMT 2015 christos new mdocml
H A DCHANGES1.1269 Wed Aug 05 19:10:56 GMT 2009 christos mention new openssl.
/src/distrib/sets/lists/base/
H A Dmi1.1269 Tue Nov 10 08:49:08 GMT 2020 kamil Integrate Warp Kit into the NetBSD build

Fix the build and make it install and run with minimal required changes.
/src/distrib/sets/lists/man/
H A Dmi1.1269 Thu Dec 16 15:30:56 GMT 2010 pooka +rump_sp manpage
/src/distrib/sets/lists/tests/
H A Dmi1.1269 Fri Jun 16 09:25:13 GMT 2023 rillig tests/make: add test for multiple-inclusion guards
/src/share/mk/
H A Dbsd.own.mk1.1269 Mon Dec 06 17:52:00 GMT 2021 abs Add Xwsfb X server to pmax build

With the previous tweak to TURBOchannel framebuffers in sys/dev/tc this
should allows pmax to once again run X11.

TODO: Investigate pullup to -9
/src/sys/conf/
H A Dfiles1.1269 Mon Jun 29 23:27:52 GMT 2020 riastradh Rework AES in kernel to finally address CVE-2005-1797.

1. Rip out old variable-time reference implementation.
2. Replace it by BearSSL's constant-time 32-bit logic.
=> Obtained from commit dda1f8a0c46e15b4a235163470ff700b2f13dcc5.
=> We could conditionally adopt the 64-bit logic too, which would
likely give a modest performance boost on 64-bit platforms
without AES-NI, but that's a bit more trouble.
3. Select the AES implementation at boot-time; allow an MD override.
=> Use self-tests to verify basic correctness at boot.
=> The implementation selection policy is rather rudimentary at
the moment but it is isolated to one place so it's easy to
change later on.

This (a) plugs a host of timing attacks on, e.g., cgd, and (b) paves
the way to take advantage of CPU support for AES -- both things we
should've done a decade ago. Downside: Computing AES takes 2-3x the
CPU time. But that's what hardware support will be coming for.

Rudimentary measurement of performance impact done by:

mount -t tmpfs tmpfs /tmp
dd if=/dev/zero of=/tmp/disk bs=1m count=512
vnconfig -cv vnd0 /tmp/disk
cgdconfig -s cgd0 /dev/vnd0 aes-cbc 256 < /dev/zero
dd if=/dev/rcgd0d of=/dev/null bs=64k
dd if=/dev/zero of=/dev/rcgd0d bs=64k

The AES-CBC encryption performance impact is closer to 3x because it
is inherently sequential; the AES-CBC decryption impact is closer to
2x because the bitsliced AES logic can process two blocks at once.

Discussed on tech-kern:

https://mail-index.NetBSD.org/tech-kern/2020/06/18/msg026505.html
/src/distrib/sets/lists/comp/
H A Dmi1.1269 Tue Jun 09 00:16:06 GMT 2009 njoly +netpgpverify.debug

Completed in 1067 milliseconds