Date: Wed, 18 Dec 2002 21:05:55 +0100 From: Poul-Henning Kamp <phk@freebsd.org> To: current@freebsd.org Subject: GBDE: Bad bug fixed. Message-ID: <5814.1040241955@critter.freebsd.dk>
next in thread | raw e-mail | index | archive | help
Marcus Reid <marcus@blazingdot.com> found a pair of bad bugs in the GBDE code which could result in corrupt data under some circumstances. The two separate bug was in the mapping code which decides where to put the encrypted sectors on the device. One bug affected only certain multi lock configurations, and will probably result in a lock-out situation if hit. The other and more serious would result in data corruption if the requestsize was larger than the sectorsize. If you have data on GBDE which you care about, you should do the following: dump(8) from the encrypted device to some media/file. Make sure you have these versions: 1.8 +21 -1 src/sbin/gbde/gbde.c 1.6 +2 -2 src/sys/geom/bde/g_bde_crypt.c 1.6 +6 -0 src/sys/geom/bde/g_bde_lock.c 1.4 +7 -42 src/sys/geom/bde/g_bde_work.c Recompile the kernel and gbde(8). Teboot the new kernel. Use gbde(8) to init the device again. Use restore(8) to put your data back on the encrypted device. (Delete the backup copy if it is on unsafe media). My sincerest apologies for overlooking what in hindsight is a rather obvious bug... Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5814.1040241955>