Harddisk encryption with geli: key's block size

Hi, I want to encrypt my mobile computer's data-partition with a passphrase, 128 bit AES and HMAC/MD5. A lot of people use different block sizes to generate keys with dd. There are examples with block sizes of 64, 32k and 128k in geli's man-page, but I couldn't find out why they were used.

Smartmontools: Load_Cycle_Count increasing rapidly

Hi, there are some reports that Ubuntu GNU/Linux 7.10 kills harddisks: http://ubuntudemon.wordpress.com/2007/10/28/laptop-hardrive-killer-bug-how-to-discover-whether-you-are-affected/ I can confirm this behaviour for FreeBSD 6.2 STABLE 200710 i386 and smartmontools-5.37_2 from the

Re: Smartmontools: Load_Cycle_Count increasing rapidly

There's a way to stop the Load_Cycle_Count growing by installing ataidle from the portscollection and disabling APM with ataidle -P 0 0 0. The Load_Cycle_Count is constant after that. This reduces battery-runtime but that's much better than destroying your harddisk. Best greetings Thomas

Synaptics Touchpad doesn't work on 64-bit FreeBSD

Hi, my Synaptics touchpad doesn't work on FreeBSD 200710 amd64. I've add hw.psm.synaptics_support=1 to my /boot/loader.conf and I've compiled x11-drivers/synaptics and x11-drivers/xf86-input-mouse. My dmesg says: psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics

Encrypting mirrored device with geli fails

# uname -a FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # cat /boot/loader.conf beastie_disable=YES geom_eli_load=YES geom_mirror_load=YES padlock_load=YES Swap space is encrypted by appending '.eli' to

Encrypting mirrored device with geli fails

# uname -a FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 # cat /boot/loader.conf beastie_disable=YES geom_eli_load=YES geom_mirror_load=YES padlock_load=YES Swap space is encrypted by appending '.eli' to

Re: Encrypting mirrored device with geli fails

I was trying to encrypt /dev/mirror/gm0s1f but a MD5 mismatch occurred: # umount /crypt # dd if=/dev/random of=/root/gm0s1f.key bs=64 count=1 1+0 records in 1+0 records out 64 bytes transferred in 0.000580 secs (110331 bytes/sec) longer.. 32k or so. The same failure occurred.

Re: Encrypting mirrored device with geli fails

I was trying to encrypt /dev/mirror/gm0s1f but a MD5 mismatch occurred: # umount /crypt # dd if=/dev/random of=/root/gm0s1f.key bs=64 count=1 1+0 records in 1+0 records out 64 bytes transferred in 0.000580 secs (110331 bytes/sec) longer.. 32k or so. The same failure

GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f

Hi, what is this kind of error's meaning? Greetings elesdo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f

It means that metadata (in the last provider's sector) is in an inconsistent state. Someone/something changed it. The error occurs while attaching a device on a gmirrored disk. Am I right assuming that the responisble change happens right between initialisation and attachment?

Re: GEOM ELI: MD5 hash mismatch for /dev/mirror/gm0s1f

It's impossible to tell which one of these is more likely without more information (e.g. did you receive any other messages, such as CRC errors on the drive?) No, I didn't receive more information. Can I exclude that a combination of gmirror and geli is responsible for this error? Because one