<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/sys/opencrypto/cryptosoft.c, branch releng/10.2</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F10.2</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F10.2'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2010-11-14T13:09:32Z</updated>
<entry>
<title>Let cryptosoft(4) add its pseudo-device with a specific unit number and its</title>
<updated>2010-11-14T13:09:32Z</updated>
<author>
<name>Marius Strobl</name>
<email>marius@FreeBSD.org</email>
</author>
<published>2010-11-14T13:09:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=86c585d92963f996d15ed9cc037452c5f1ffc2ca'/>
<id>urn:sha1:86c585d92963f996d15ed9cc037452c5f1ffc2ca</id>
<content type='text'>
probe method return BUS_PROBE_NOWILDCARD so it doesn't get attached to real
devices hanging off of nexus(4) with no specific devclass set. Actually, the
more desirable fix for this would be to get rid of the newbus interface of
cryptosoft(4) altogether but apparently crypto(9) was written with support
for cryptographic hardware in mind so that approach would require some KPI
breaking changes which don't seem worth it.

MFC after:	1 week
</content>
</entry>
<entry>
<title>Add support for AES-XTS.</title>
<updated>2010-09-23T11:52:32Z</updated>
<author>
<name>Pawel Jakub Dawidek</name>
<email>pjd@FreeBSD.org</email>
</author>
<published>2010-09-23T11:52:32Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=d295bdee07c0ab099c53dc009bb7993b98ff54cd'/>
<id>urn:sha1:d295bdee07c0ab099c53dc009bb7993b98ff54cd</id>
<content type='text'>
Obtained from:	OpenBSD
MFC after:	1 week
</content>
</entry>
<entry>
<title>Add comments trying to explain what bad things happen here, i.e.</title>
<updated>2010-01-09T15:43:47Z</updated>
<author>
<name>Bjoern A. Zeeb</name>
<email>bz@FreeBSD.org</email>
</author>
<published>2010-01-09T15:43:47Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=77680d964f93ff567d1d846a267f123df275e418'/>
<id>urn:sha1:77680d964f93ff567d1d846a267f123df275e418</id>
<content type='text'>
how hashed MD5/SHA are implemented, abusing Final() for padding and
sw_octx to transport the key from the beginning to the end.

Enlightened about what was going on here by: cperciva
Reviewed by:	cperciva
MFC After:	3 days
X-MFC with:	r187826
PR:		kern/126468
</content>
</entry>
<entry>
<title>In case the compression result is the same size as the orignal version,</title>
<updated>2009-11-29T17:53:57Z</updated>
<author>
<name>Bjoern A. Zeeb</name>
<email>bz@FreeBSD.org</email>
</author>
<published>2009-11-29T17:53:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=df4dece10200edc153f51c5fd7bb264c1f5e0a9d'/>
<id>urn:sha1:df4dece10200edc153f51c5fd7bb264c1f5e0a9d</id>
<content type='text'>
the compression was useless as well.  Make sure to not update the data
and return, else we would waste resources when decompressing.

This also avoids the copyback() changing data other consumers like
xform_ipcomp.c would have ignored because of no win and sent out without
noting that compression was used, resulting in invalid packets at the
receiver.

MFC after:	5 days
</content>
</entry>
<entry>
<title>Fix return type for detach routine (should be int)</title>
<updated>2009-02-05T17:43:12Z</updated>
<author>
<name>Warner Losh</name>
<email>imp@FreeBSD.org</email>
</author>
<published>2009-02-05T17:43:12Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=3f147ab25163eb6f6f11777db1cf796188ba123f'/>
<id>urn:sha1:3f147ab25163eb6f6f11777db1cf796188ba123f</id>
<content type='text'>
Fix first parameter for identify routine (should be driver_t *)
</content>
</entry>
<entry>
<title>While OpenBSD's crypto/ framework has sha1 and md5 implementations that</title>
<updated>2009-01-28T15:31:16Z</updated>
<author>
<name>Bjoern A. Zeeb</name>
<email>bz@FreeBSD.org</email>
</author>
<published>2009-01-28T15:31:16Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1f4990a6b5f80438b037eb25d5f88ec315d229e7'/>
<id>urn:sha1:1f4990a6b5f80438b037eb25d5f88ec315d229e7</id>
<content type='text'>
can cope with a result buffer of NULL in the "Final" function, we cannot.
Thus pass in a temporary buffer long enough for either md5 or sha1 results
so that we do not panic.

PR:		bin/126468
MFC after:	1 week
</content>
</entry>
<entry>
<title>Don't hang if encrypting/decrypting using struct iovecs where one of the</title>
<updated>2008-10-30T16:11:07Z</updated>
<author>
<name>Doug Rabson</name>
<email>dfr@FreeBSD.org</email>
</author>
<published>2008-10-30T16:11:07Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=bfd50e2732c722abb6e847a15a75e1f4a04cdf99'/>
<id>urn:sha1:bfd50e2732c722abb6e847a15a75e1f4a04cdf99</id>
<content type='text'>
iovecs ends on a crypto block boundary.
</content>
</entry>
<entry>
<title>Retire the MALLOC and FREE macros.  They are an abomination unto style(9).</title>
<updated>2008-10-23T15:53:51Z</updated>
<author>
<name>Dag-Erling Smørgrav</name>
<email>des@FreeBSD.org</email>
</author>
<published>2008-10-23T15:53:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1ede983cc905643549d8cae56a9d0e28fc68375f'/>
<id>urn:sha1:1ede983cc905643549d8cae56a9d0e28fc68375f</id>
<content type='text'>
MFC after:	3 months
</content>
</entry>
<entry>
<title>Integrate the Camellia Block Cipher.  For more information see RFC 4132</title>
<updated>2007-05-09T19:37:02Z</updated>
<author>
<name>George V. Neville-Neil</name>
<email>gnn@FreeBSD.org</email>
</author>
<published>2007-05-09T19:37:02Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=559d3390d07890da9ca8ad6427f1ae7df7a9257a'/>
<id>urn:sha1:559d3390d07890da9ca8ad6427f1ae7df7a9257a</id>
<content type='text'>
and its bibliography.

Submitted by:   Tomoyuki Okazaki &lt;okazaki at kick dot gr dot jp&gt;
MFC after:      1 month
</content>
</entry>
<entry>
<title>Overhaul driver/subsystem api's:</title>
<updated>2007-03-21T03:42:51Z</updated>
<author>
<name>Sam Leffler</name>
<email>sam@FreeBSD.org</email>
</author>
<published>2007-03-21T03:42:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=6810ad6f2aeb6f6076d535c55a3e58f4b3358e79'/>
<id>urn:sha1:6810ad6f2aeb6f6076d535c55a3e58f4b3358e79</id>
<content type='text'>
o make all crypto drivers have a device_t; pseudo drivers like the s/w
  crypto driver synthesize one
o change the api between the crypto subsystem and drivers to use kobj;
  cryptodev_if.m defines this api
o use the fact that all crypto drivers now have a device_t to add support
  for specifying which of several potential devices to use when doing
  crypto operations
o add new ioctls that allow user apps to select a specific crypto device
  to use (previous ioctls maintained for compatibility)
o overhaul crypto subsystem code to eliminate lots of cruft and hide
  implementation details from drivers
o bring in numerous fixes from Michale Richardson/hifn; mostly for
  795x parts
o add an optional mechanism for mmap'ing the hifn 795x public key h/w
  to user space for use by openssl (not enabled by default)
o update crypto test tools to use new ioctl's and add cmd line options
  to specify a device to use for tests

These changes will also enable much future work on improving the core
crypto subsystem; including proper load balancing and interposing code
between the core and drivers to dispatch small operations to the s/w
driver as appropriate.

These changes were instigated by the work of Michael Richardson.

Reviewed by:	pjd
Approved by:	re
</content>
</entry>
</feed>
