summaryrefslogtreecommitdiffstats
path: root/sys/geom/eli
Commit message (Collapse)AuthorAgeFilesLines
* Style(9).pjd2008-08-121-3/+4
|
* Clear passphrase buffer after use.pjd2008-07-201-0/+2
| | | | Submitted by: Fabian Keil <fk@fabiankeil.de> (a bit different version)
* On some arches, openssl is built with OPENSSL_NO_CAMELLIA, so thejb2007-11-191-0/+2
| | | | code here needs to depend on that too.
* Rename the kthread_xxx (e.g. kthread_create()) callsjulian2007-10-201-2/+2
| | | | | | | | | | | to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it turns out that most of these calls actually end up being moved back to the thread version when it's added. but we need to make this cosmetic change first. I'd LOVE to do this rename in 7.0 so that we can eventually MFC the new kthread_xxx() calls.
* Add support for Camellia encryption algorithm.pjd2007-09-012-1/+21
| | | | | | PR: kern/113790 Submitted by: Yoshisato YANAGISAWA <yanagisawa@csg.is.titech.ac.jp> Approved by: re (bmah)
* Commit 14/14 of sched_lock decomposition.jeff2007-06-051-2/+2
| | | | | | | | | | | - Use thread_lock() rather than sched_lock for per-thread scheduling sychronization. - Use the per-process spinlock rather than the sched_lock for per-process scheduling synchronization. Tested by: kris, current@ Tested on: i386, amd64, ULE, 4BSD, libthr, libkse, PREEMPTION, etc. Discussed with: kris, attilio, kmacy, jhb, julian, bde (small parts each)
* When deleting key, flush write cache after each overwrite, so we don'tpjd2007-05-061-0/+5
| | | | overwrite data N times in cache and only once on disk.
* Use root_mounted().pjd2007-04-081-1/+1
|
* Overhaul driver/subsystem api's:sam2007-03-212-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Warn when user use sectorsize bigger than the page size, which will leadpjd2007-03-051-0/+4
| | | | | | | | to problems when the geli device is used with file system or as a swap. Hopefully will prevent problems like kern/98742 in the future. MFC after: 1 week
* Fix geli after last commit for UP systems that are running SMP kernel.pjd2007-03-021-1/+2
| | | | | Submitted by: Hyo geol, Lee <hyogeollee@gmail.com> MFC after: 1 week
* It is possible that GEOM taste provider before SMP is started.pjd2007-01-281-0/+7
| | | | | | | | We can't bind to a CPU which is not yet on-line, so add code that wait for CPUs to go on-line before binding to them. Reported by: Alin-Adrian Anton <aanton@spintech.ro> MFC after: 2 weeks
* I want CPU number here.pjd2006-11-021-1/+1
| | | | Noticed by: ru
* Skip disabled CPU, because after we sched_bind() to a disabled CPU,pjd2006-11-011-1/+16
| | | | | | | | | | we won't be able to exit from the thread. Function g_eli_cpu_is_disabled() stoled from kern_pmc.c. PR: 104669 Reported by: Nikolay Mirin <nik@optim.com.ru> MFC after: 1 week
* Implement BIO_FLUSH handling by simply passing it down to the components.pjd2006-10-311-0/+2
| | | | Sponsored by: home.pl
* Remove trailing spaces.pjd2006-09-302-2/+2
|
* Add 'configure' subcommand which for now only allows setting and removingpjd2006-09-162-3/+116
| | | | | | | | of the BOOT flag. It can be performed on both attached and detached providers. Requested by: Matthias Lederhofer <matled@gmx.net> MFC after: 1 week
* Remove extra arguments.pjd2006-09-161-2/+1
| | | | MFC after: 3 days
* Before using byte offset for IV creation, covert it to little endian.pjd2006-08-112-11/+21
| | | | | | | | | | This way one will be able to use provider encrypted on eg. i386 on eg. sparc64. This doesn't really buy us much today, because UFS isn't endian agnostic. We retain backward compatibility by setting G_ELI_FLAG_NATIVE_BYTE_ORDER flag on devices with version number less than 2 and not converting the offset.
* Forgot to bump version number after G_ELI_FLAG_READONLY flag addition.pjd2006-08-111-3/+5
|
* Allow geli to operate on read-only providers.pjd2006-08-093-24/+67
| | | | | Initial patch from: vd MFC after: 2 weeks
* Fix what looks like a typo: MODULE_DEPEND() takes module names,yar2006-07-271-1/+1
| | | | | | | not KLD file names; and GELI module's name is g_eli, not geom_eli. Approved by: pjd (silence) MFC after: 5 days
* Don't forget to initialize crp_olen field, which is used to calculatepjd2006-07-221-0/+1
| | | | bio_completed value.
* Allow to use the old -a option to specify an encryption algorithm to usepjd2006-06-061-13/+31
| | | | | (for backward compatibility), but print a warning to inform about the change.
* - Unbreak the build when geli is compiled into the kernel (on as module),pjd2006-06-061-2/+2
| | | | | | by silencing unfounded compiler warning. Reported by:
* Implement data integrity verification (data authentication) for geli(8).pjd2006-06-056-275/+1101
| | | | Supported by: Wheel Sp. z o.o. (http://www.wheel.pl)
* Make kern.geom.eli.overwrites sysctl a tunable as well.pjd2006-06-051-0/+1
|
* geli(8) provides keys on newsession time, so remove CRD_F_KEY_EXPLICIT flagpjd2006-04-202-3/+2
| | | | as HW crypto drivers don't support it.
* Correct debug: we are sending child bio here, not parent bio.pjd2006-04-151-2/+2
| | | | MFC after: 1 week
* Pass BIO_GETATTR requests down.pjd2006-04-121-5/+14
| | | | MFC after: 1 week
* Typos.pjd2006-04-051-1/+1
|
* Revert previous change, as I fixed MD5(9).pjd2006-03-301-6/+2
|
* md_hash field in g_eli_metadata structure is not 4 byte aligned, whichpjd2006-03-301-2/+6
| | | | | | | | | | | | | | | case panic on sparc64. The problem is in MD5(9) implementation. The Encode() function takes 'unsigned char *output' as its first argument, which is then assigned to 'u_int32_t *op'. If the 'output' argument is not 4 byte aligned (and in geli(8) case it is not), sparc64 machine will panic. I don't know how to fix MD5(9) in a clean way, so I'm implementing a work-around in geli(8). Reported by: brueffer MFC after: 3 days
* Teach geli how to load keyfiles before root file system is mounted.pjd2006-02-111-19/+106
| | | | | | | | | | | | | | | | | | | | | | An example entries for loader.conf to make it possible: geli_da0_keyfile0_load="YES" geli_da0_keyfile0_type="da0:geli_keyfile0" geli_da0_keyfile0_name="/boot/keys/da0.key0" geli_da0_keyfile1_load="YES" geli_da0_keyfile1_type="da0:geli_keyfile1" geli_da0_keyfile1_name="/boot/keys/da0.key1" geli_da0_keyfile2_load="YES" geli_da0_keyfile2_type="da0:geli_keyfile2" geli_da0_keyfile2_name="/boot/keys/da0.key2" geli_da1s3a_keyfile0_load="YES" geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0" geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key" Thanks for jhb and kan who showed me the right direction. MFC after: 3 days
* Check rootvnode variable to see if we still want to ask for passphrase onpjd2006-02-111-28/+2
| | | | | | boot. Other methods just don't work properly. MFC after: 3 days
* Clean up some sysctl descriptions, debug messages etc.brueffer2006-02-071-7/+7
| | | | | Approved by: pjd MFC after: 3 days
* Remove trailing spaces.pjd2006-02-017-10/+10
|
* - Use better types.pjd2006-01-171-6/+6
| | | | | | - Log problems at level 0 when killing providers. MFC after: 3 days
* Check return value.pjd2006-01-171-0/+4
| | | | | Found by: Coverity Prevent(tm) MFC after: 3 days
* Remove dead code.pjd2006-01-171-2/+0
| | | | | Found by: Coverity Prevent(tm) MFC after: 3 days
* Remove unused value.pjd2006-01-171-2/+1
| | | | | Found by: Coverity Prevent(tm) MFC after: 3 days
* Check for g_read_data(9) errors properly:sobomax2005-11-301-1/+1
| | | | | | | | | | o The only indication of error condition is NULL value returned by the function; o value pointed to by error argument is undefined in the case when operation completes successfully. Discussed with: phk
* Fix copy&paste typo.pjd2005-09-101-1/+1
| | | | MFC after: 3 days
* Don't forget to initialize crp_etype field.pjd2005-09-101-0/+1
| | | | | Reported by: Nick Evans <nevans@syphen.net> MFC after: 3 days
* By default, when doing crypto work in software, start as many threadspjd2005-08-211-5/+10
| | | | | | as we have active CPUs and bind each thread to its own CPU. MFC after: 3 days
* Remove stale comment (we now always start worker thread).pjd2005-08-211-5/+0
| | | | MFC after: 3 days
* Add a __packed keyword to g_eli_metadata struct definition, sopjd2005-08-201-1/+1
| | | | | | | | | | | sizeof(struct g_eli_metadata) will return the exact number of bytes needed for storing it on the disk. Without this change GELI was unusable on amd64 (and probably other 64-bit archs), because sizeof(struct g_eli_metadata) was greater than 512 bytes and geli(8) was failing on assertion. Reported by: Michael Reifenberger <mike@Reifenberger.com> MFC after: 3 days
* Allow to change number of iterations for PKCS#5v2. It can only be usedpjd2005-08-191-2/+21
| | | | | | when there is only one key set. MFC after: 3 days
* - Add a missing period.pjd2005-08-191-3/+3
| | | | | | - Fix number of spaces. MFC after: 3 days
* Always run dedicated kernel thread (even when we have hardware support).pjd2005-08-171-114/+37
| | | | | | | | There is no performance impact, but allows to allocate memory with M_WAITOK flag. As a side effect this simplify code a bit. MFC after: 3 days
OpenPOWER on IntegriCloud