Re: [Jailkit-dev] jk_init will fail in Debian if /dev/ is needed

[Eriberto]

Hi everyone,

Is there any news about this issue? I would like to fix this in Debian
Stable and Unstable.

Thanks.

Eriberto

Em qua., 18 de ago. de 2021 às 21:03, Eriberto
<eriberto@eriberto.pro.br> escreveu:
>
> Dear developer,
>
> Debian 11 Bullseye, released last Saturday, Debian Unstable and Debian
> Testing (future 12 Bookworm), dropped support for Python 2. Currently,
> when trying to create a jail with a /dev/ device, the following
> message is shown: "Failed to create device /chroot/dev/random, this is
> a know problem with python 2.1".
>
> See an example:
>
> # jk_init -j /teste-jailkit cvs
> Copying /usr/bin/cvs to /teste-jailkit/usr/bin/cvs
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libcrypt.so.1 to
> libcrypt.so.1.1.0
> Copying /lib/x86_64-linux-gnu/libcrypt.so.1.1.0 to
> /teste-jailkit/lib/x86_64-linux-gnu/libcrypt.so.1.1.0
> Creating symlink
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 to
> libgssapi_krb5.so.2.2
> Copying /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 to
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2
> Creating symlink /teste-jailkit/usr/lib/x86_64-linux-gnu/libkrb5.so.3
> to libkrb5.so.3.3
> Copying /usr/lib/x86_64-linux-gnu/libkrb5.so.3.3 to
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libkrb5.so.3.3
> Creating symlink /teste-jailkit/usr/lib/x86_64-linux-gnu/libbsd.so.0
> to libbsd.so.0.11.3
> Copying /usr/lib/x86_64-linux-gnu/libbsd.so.0.11.3 to
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libbsd.so.0.11.3
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libz.so.1 to 
> libz.so.1.2.11
> Copying /lib/x86_64-linux-gnu/libz.so.1.2.11 to
> /teste-jailkit/lib/x86_64-linux-gnu/libz.so.1.2.11
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libc.so.6 to libc-2.31.so
> Copying /lib/x86_64-linux-gnu/libc-2.31.so to
> /teste-jailkit/lib/x86_64-linux-gnu/libc-2.31.so
> Creating symlink
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libk5crypto.so.3 to
> libk5crypto.so.3.1
> Copying /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1 to
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libcom_err.so.2
> to libcom_err.so.2.1
> Copying /lib/x86_64-linux-gnu/libcom_err.so.2.1 to
> /teste-jailkit/lib/x86_64-linux-gnu/libcom_err.so.2.1
> Creating symlink
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libkrb5support.so.0 to
> libkrb5support.so.0.1
> Copying /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1 to
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libkeyutils.so.1
> to libkeyutils.so.1.9
> Copying /lib/x86_64-linux-gnu/libkeyutils.so.1.9 to
> /teste-jailkit/lib/x86_64-linux-gnu/libkeyutils.so.1.9
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libresolv.so.2 to
> libresolv-2.31.so
> Copying /lib/x86_64-linux-gnu/libresolv-2.31.so to
> /teste-jailkit/lib/x86_64-linux-gnu/libresolv-2.31.so
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libdl.so.2 to 
> libdl-2.31.so
> Copying /lib/x86_64-linux-gnu/libdl-2.31.so to
> /teste-jailkit/lib/x86_64-linux-gnu/libdl-2.31.so
> Creating symlink /teste-jailkit/usr/lib/x86_64-linux-gnu/libmd.so.0 to
> libmd.so.0.0.4
> Copying /usr/lib/x86_64-linux-gnu/libmd.so.0.0.4 to
> /teste-jailkit/usr/lib/x86_64-linux-gnu/libmd.so.0.0.4
> Creating symlink /teste-jailkit/lib64/ld-linux-x86-64.so.2 to
> /lib/x86_64-linux-gnu/ld-2.31.so
> Copying /lib/x86_64-linux-gnu/ld-2.31.so to
> /teste-jailkit/lib/x86_64-linux-gnu/ld-2.31.so
> Creating symlink /teste-jailkit/lib/x86_64-linux-gnu/libpthread.so.0
> to libpthread-2.31.so
> Copying /lib/x86_64-linux-gnu/libpthread-2.31.so to
> /teste-jailkit/lib/x86_64-linux-gnu/libpthread-2.31.so
> mknod: número maior de dispositivo é inválido “1.01171875”
> Failed to create device /teste-jailkit/dev/null, this is a know
> problem with python 2.1
> use "ls -l /dev/null" to find out the mode, major and minor for the device
> use "mknod /teste-jailkit/dev/null mode major minor" to create the device
> use chmod and chown to set the permissions as found by ls -l
>
> This bug is related to Debian bug #992422, available here[1].
>
> [1] https://bugs.debian.org/992422
>
> Regards,
>
> Eriberto