Cryptoloop and kernel 2.6?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everybody,

I use Slackware 9.1 for desktop and work. I currently use linux-2.4.22
plus the cryptoapi and -loop patches.
I use a cryptoloop-device for my diary.

Now I would like to upgrade my kernel to 2.6, but cryptoloop does not
work with 2.6 - I upgraded util-linux to 2.12, but it still does not
work. What am I doing wrong? Do I have to patch util-linux-2.12? If I
understand correctly, the patch for cryptoloop is already included in
2.12.

Thank you very much,

Kind regards,

Benjamin

- --
Benjamin Walkenhorst
eMail: krylon@gmx.net
http://www.krylon.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAAZ26/JWwsvZUqOwRAuW+AJ9ibNsi5RjJvwUIKgW7mx9GI7YBOwCf WWw1
4UAtbswKuANmKSKSs2GIKMs=
=VDyi
-----END PGP SIGNATURE-----

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Cryptoloop and kernel 2.6?

--GpGaEY17fSl8rd50
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello!

My work partner here has more or less the same problem, please post
any solutions to the list, so he can use 2.6 with his notebook, too.

Nico

Benjamin Walkenhorst [Sun, Jan 11, 2004 at 08:02:18PM +0100]:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Hello everybody,
>=20
> I use Slackware 9.1 for desktop and work. I currently use linux-2.4.22=20
> plus the cryptoapi and -loop patches.
> I use a cryptoloop-device for my diary.
>=20
> Now I would like to upgrade my kernel to 2.6, but cryptoloop does not=20
> work with 2.6 - I upgraded util-linux to 2.12, but it still does not=20
> work. What am I doing wrong? Do I have to patch util-linux-2.12? If I=20
> understand correctly, the patch for cryptoloop is already included in=20
> 2.12.=20
>=20
> Thank you very much,
>=20
> Kind regards,
>=20
> Benjamin
>=20
> - --=20
> Benjamin Walkenhorst
> eMail: krylon@gmx.net
> http://www.krylon.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (NetBSD)
>=20
> iD8DBQFAAZ26/JWwsvZUqOwRAuW+AJ9ibNsi5RjJvwUIKgW7mx9GI7YBOwCf WWw1
> 4UAtbswKuANmKSKSs2GIKMs=3D
> =3DVDyi
> -----END PGP SIGNATURE-----
>=20
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>=20

--=20
Keep it simple & stupid, use what's available.
pgp: 8D0E E27A | Nico Schottelius
http://nerd-hosting.net | http://linux.schottelius.org

--GpGaEY17fSl8rd50
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAAqZSzGnTqo0OJ6QRAiV3AJ9uUxjp3xm/MViXBJTOCeGSyns6KwCf adLr
Nu8l8EymsPMit/gmtm+mpPQ=
=lrJm
-----END PGP SIGNATURE-----

--GpGaEY17fSl8rd50--
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Cryptoloop and kernel 2.6?

On Sun, Jan 11, 2004 at 08:02:18PM +0100, Benjamin Walkenhorst wrote:
> Now I would like to upgrade my kernel to 2.6, but cryptoloop does not
> work with 2.6 - I upgraded util-linux to 2.12, but it still does not

Can you tell more about problem. The questions like "xyz does not
work" is hard to answer, really.

> work. What am I doing wrong? Do I have to patch util-linux-2.12? If I
> understand correctly, the patch for cryptoloop is already included in
> 2.12.

Please, read document how to ask question in mailing list at the URL
bellow:
http://www.tuxedo.org/~esr/faqs/smart-questions.html
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Cryptoloop and kernel 2.6?

Just for kicks I went and did a cryptoloop-device on my slack9.1 box.
Fairly easy, no patches required, and you can *almost* follow the
directions at:

http://tldp.org/HOWTO/Loopback-Encrypted-Filesystem-HOWTO.ht ml

A quick run-down of what to do:

1) Grab the 2.6 kernel from ftp://ftp.kernel.org

2) Configure the kernel:
a) Turn on 'Code maturity level options'/'Prompt for development
and/or incomplete code/drivers'
b) Turn on 'Device Drivers'/'Block devices'/'Loopback device support'
as well as the sub-item 'Cryptoloop Support'
c) Under 'Cryptographic options' make sure to turn on the crypto
algorithms you intend to use. The HOWTO recommends serpent, and that is
what i tested with, though you should be able to use just about any
algorithm you want.
Note: If you compile any of these options as modules, you will probably
want to create a shell-script that will modprobe or insmod them.

3) Compile your new kernel, use your bootloader to make the new kernel
bootable. Reboot.

4) Create your encrypted file, if you don't already have one:
$ dd if=/dev/urandom of=/home/myuser/cryptfile bs=1M count=10
If I understand this correctly, this creates a 10MB file of garbage,
which is what you want. You can change the size of 'count' if you need
to create a larger file.

5) Create your loopback device (loop, cryptoloop, and your algorithm
modules must be loaded at this point):
$ losetup -e serpent /dev/loop0 /home/myuser/cryptfile
Note: A normal user can't do this by default.
Note2: As stated in the HOWTO, you only get one chance to enter the
password. It will create the loopback device even if you enter the wrong
password, but the contents of /dev/loop0 will essentially be garbage.

6) Create your filesystem, for example:
$ mke2fs /dev/loop0

7) You *should* now be able to mount your filesystem with:
$ mount -t ext2 /dev/loop0 /some/mount/point
Note: add the ability for users to mount /dev/loop0 to fstab if you
don't want to su each time you want to use your encrypted filesystem,
though you'll probably by using su to run losetup.

8) To unmount and secure your file:
$ umount /dev/loop0
$ losetup -d /dev/loop0
Note: 'losetup -d [device]' removes the loopback device

Also, as a side note, Slackware9.1 comes with util-linux-2.12. I didn't
upgrade or patch util-linux in any way.

And that's basically it.

~Brad

Benjamin Walkenhorst wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello everybody,
>
> I use Slackware 9.1 for desktop and work. I currently use linux-2.4.22
> plus the cryptoapi and -loop patches.
> I use a cryptoloop-device for my diary.
>
> Now I would like to upgrade my kernel to 2.6, but cryptoloop does not
> work with 2.6 - I upgraded util-linux to 2.12, but it still does not
> work. What am I doing wrong? Do I have to patch util-linux-2.12? If I
> understand correctly, the patch for cryptoloop is already included in
> 2.12.
>
> Thank you very much,
>
> Kind regards,
>
> Benjamin
>
> - --
> Benjamin Walkenhorst
> eMail: krylon@gmx.net
> http://www.krylon.de
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (NetBSD)
>
> iD8DBQFAAZ26/JWwsvZUqOwRAuW+AJ9ibNsi5RjJvwUIKgW7mx9GI7YBOwCf WWw1
> 4UAtbswKuANmKSKSs2GIKMs=
> =VDyi
> -----END PGP SIGNATURE-----
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Cryptoloop and kernel 2.6?

--i0/AhcQY5QxfSsSZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Bradley Hook [Mon, Jan 12, 2004 at 03:02:07PM -0600]:
> Just for kicks I went and did a cryptoloop-device on my slack9.1 box.=20
> Fairly easy, no patches required, and you can *almost* follow the=20
> directions at:
>=20
> http://tldp.org/HOWTO/Loopback-Encrypted-Filesystem-HOWTO.ht ml
>=20
> A quick run-down of what to do:
> [...]

what about crypto loops created within 2.4?
Is it possible something changed and 2.6 cannot read the old
ones?

Greetings,

Nico

--=20
Keep it simple & stupid, use what's available.
pgp: 8D0E E27A | Nico Schottelius
http://nerd-hosting.net | http://linux.schottelius.org

--i0/AhcQY5QxfSsSZ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAAyPlzGnTqo0OJ6QRAniMAJ44vKa+B3BGkasjcXB94FIDvUrGWwCc CP7z
nkr22eyn8CMctb78xFC+Nd4=
=uhWC
-----END PGP SIGNATURE-----

--i0/AhcQY5QxfSsSZ--
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Cryptoloop and kernel 2.6?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Nico Schottelius wrote:
> what about crypto loops created within 2.4?
> Is it possible something changed and 2.6 cannot read the old
> ones?

sigh, so much is possible these days...

do you experience any problems with your crypto loops created with a
2.4 kernel under a brand new 2.6? do you use crypto loops in the
first place? if so, why don't you just find out and tell us? :)


- --
Bastard Administrator in $hell
GPG-Key at http://lists.notified.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFABTXFLMyTO8Kj/uQRAllfAJ9ri0sLJOoqafuNDaeNYs5zZwiPQgCe NghR
Yl7Un7FSEwLX10EyyxMSQ14=
=KW3O
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Cryptoloop and kernel 2.6?

--zx4FCpZtqtKETZ7O
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

markus reichelt [Wed, Jan 14, 2004 at 01:27:49PM +0100]:
> Nico Schottelius wrote:
> > what about crypto loops created within 2.4?
> > Is it possible something changed and 2.6 cannot read the old
> > ones?
>=20
> sigh, so much is possible these days...

that was true since we live, not just today.
Goethe's "Faust" shows you that very well.

> do you experience any problems with your crypto loops created with a
> 2.4 kernel under a brand new 2.6? do you use crypto loops in the
> first place? if so, why don't you just find out and tell us? :)

"tell"

no go on and fix it ;)

Nico

ps: does anyone know if there were changes in the cryptoloop, which
cause this problem?

--=20
Keep it simple & stupid, use what's available.
pgp: 8D0E E27A | Nico Schottelius
http://nerd-hosting.net | http://linux.schottelius.org

--zx4FCpZtqtKETZ7O
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFABTtlzGnTqo0OJ6QRAm2oAKCA0yfLb2rqm2kyv+rt6PnENr3PUACc CkBt
DgAoqDplbaA1iiu7ILVp/Ic=
=pPCu
-----END PGP SIGNATURE-----

--zx4FCpZtqtKETZ7O--
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html