From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 19 21:34:09 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADA501065672 for ; Thu, 19 Feb 2009 21:34:09 +0000 (UTC) (envelope-from mail@sebastianstumpf.de) Received: from ipx10412.ipxserver.de (spicecastle.net [212.112.237.177]) by mx1.freebsd.org (Postfix) with ESMTP id 699FD8FC18 for ; Thu, 19 Feb 2009 21:34:09 +0000 (UTC) (envelope-from mail@sebastianstumpf.de) Received: by ipx10412.ipxserver.de (Postfix, from userid 5000) id EEA30FFB41; Thu, 19 Feb 2009 22:00:49 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on ipx10412.ipxserver.de X-Spam-Level: X-Spam-Status: No, score=0.4 required=3.0 tests=AWL,BAYES_00,RCVD_IN_PBL, RCVD_IN_SORBS_DUL,RDNS_DYNAMIC autolearn=no version=3.2.3 Received: from elysium (pD9E4706F.dip.t-dialin.net [217.228.112.111]) by ipx10412.ipxserver.de (Postfix) with ESMTP id 1293BFF864 for ; Thu, 19 Feb 2009 22:00:47 +0100 (CET) Date: Thu, 19 Feb 2009 22:00:42 +0100 From: Sebastian Stumpf To: freebsd-hackers@freebsd.org Message-ID: <20090219210041.GA5299@sebastianstumpf.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DocE+STaALJfprDB" Content-Disposition: inline Priority: normal X-Editor: vim 7.1 User-Agent: mutt-ng/devel-r804 (FreeBSD 7.1-STABLE) Subject: gbde and missing lock file X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2009 21:34:09 -0000 --DocE+STaALJfprDB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi. I've got a small GEOM_BDE setup at my computer. I used gbde to encrypt ad4s1e and stored its lock file under=20 /etc/gbde/ad4s1e.lock. Accidently I deleted this file via a=20 cronjob. I know that the lock file only stores the lock sector position on the disk. I've still got my password. I've read a bit through src/sbin/geom, but I don't think that I'm skilled enough to write a hack that will try every sector with my password and call fsck to check for a valid ufs filesystem.=20 I'm watching this list for quite some time now and I know that there are some people out there how could help me with this little brute=20 force problem in a few minutes by putting together a small hack/patch. And yes: Of course there was a backup of the lock file. But guess=20 where... I'd be very grateful if somebody could help me mounting this filesystem one more time. :-) Cheers, Sebastian --=20 VI VI VI - The editor of the beast. - perlhacker.org --DocE+STaALJfprDB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmdyHkACgkQUCsAQC4AUrjG4ACfR+oHbRkDA6OQL7EZN+9RmO0J Y8YAn2Q15uk+PGJjRR0xhBJWpYkGW32E =lIke -----END PGP SIGNATURE----- --DocE+STaALJfprDB--