Re: Debian 12.5 up-to-date Xfce, Firefox clings to USB stick

2024-04-03 Thread Max Nikulin 

On 31/03/2024 22:35, David Wright wrote:

On Sun 31 Mar 2024 at 09:42:37 (+0300), Antti-Pekka Känsälä wrote:

But I'm worried my Gmail in Firefox is capable of stealing
files off my USB stick.


I've no answer for that, particularly in view of Max's reply
to my previous post.

I've always copied files to and from USB sticks, floppy disks, CDs,
etc), using the hard disk as a staging area.


I think, it is a reasonable approach when combined with other measures.

Frankly speaking, I am not convinced that there is something weird with 
Gmail and Firefox.


If you do not trust Gmail as a web application, use a mail application 
that supports IMAP.


Isolate applications you do not trust and do not expose your private 
files to them. There is a number of possibilities, but neither is perfect:

- multiple system users and file permissions combined with ACLs
- virtual machines
- mount, user and other namespaces, e.g. the following options
- containers
- tools like firejail and bubblewrap
- flatpak and snap (designed for some kind of isolation, but I am unsure 
if it may be configured to specific needs)


Mount a USB drive to a trusted environment and copy specific files to a 
location available to a suspicious application.

Re: readonly installer, (SOLVED)

2024-04-03 Thread Stefan Monnier 
> I have a 128 MB USB flash drive from back in the day that includes a write
> protect switch.  There are few products today that offer that feature.

Side note: AFAIK this "write protect switch" doesn't prevent writing.
It just tells your card reader that you'd like to avoid writing to it.
Whether it ends up doing what you want depends on the hardware exposing
that info to the driver and the driver paying attention to it.


Stefan

Re: ConsultaInstalaciónDEBIAN

2024-04-03 Thread JavierDebian 

El 3/4/24 a las 19:18, Daniel Abaurrea Ruiz escribió:
Hola, aquí Daniel Abaurrea Ruiz desde Barcelona en España. Tengo 
cincuenta años de edad. Estudié arquitectura.



Mi nivel de conocimientos de hardware y software es el de usuario. 
Siempre me ha interesado mucho saber como funciona todo lo que me rodea. 
Por esta razón me gustaria aprender a instalar un sistema operativo 
debian en un ordenador portatil nuevo, comprado sin un sistema operativo 
windows instalado de serie.


He puesto este mensaje en vuestro sitio web porque estoy tratando de 
encontrar un curso en el que aprender a rea lizar el tipo de instalación 
que he descrito. He buscado información al respecto en internet pero me 
he perdido en la cantidad de información que he encontrado.


Existe algun colectivo de usuarios de debian que organice un curso en el 
que pueda aprender a realizar el tipo de instalación que he propuesto?


Dispongo de un ordenador portatil que puedo utilizar para practicar la 
instalación antes de intentarla en un ordenador portatil nuevo.


¿Alguien puede ayudarme a conseguir el obejetivo que me he propuesto?

No dudeis en contactar conmigo a traves de:

danielabaurrear...@gmail.com

Muchas gracias por vuestro tiempo y colaboración... danielabaurrearuiz




DOCENDO DISCIMUS

Acá tenés algo que te puede servir. No es el único.

https://www.youtube.com/watch?v=wc3ZcW0sjBY

Y no dude en preguntar.

Saludos

JAP

Re: ConsultaInstalaciónDEBIAN

2024-04-03 Thread Francisco Cid 
El mié., 3 abr. 2024 19:36, Daniel Abaurrea Ruiz <
danielabaurrear...@gmail.com> escribió:

> Hola, aquí Daniel Abaurrea Ruiz desde Barcelona en España. Tengo cincuenta
> años de edad. Estudié arquitectura.
>
>
> Mi nivel de conocimientos de hardware y software es el de usuario. Siempre
> me ha interesado mucho saber como funciona todo lo que me rodea. Por esta
> razón me gustaria aprender a instalar un sistema operativo debian en un
> ordenador portatil nuevo, comprado sin un sistema operativo windows
> instalado de serie.
>
> He puesto este mensaje en vuestro sitio web porque estoy tratando de
> encontrar un curso en el que aprender a rea lizar el tipo de instalación
> que he descrito. He buscado información al respecto en internet pero me he
> perdido en la cantidad de información que he encontrado.
>
> Existe algun colectivo de usuarios de debian que organice un curso en el
> que pueda aprender a realizar el tipo de instalación que he propuesto?
>
> Dispongo de un ordenador portatil que puedo utilizar para practicar la
> instalación antes de intentarla en un ordenador portatil nuevo.
>
> ¿Alguien puede ayudarme a conseguir el obejetivo que me he propuesto?
> No dudeis en contactar conmigo a traves de:
>
> danielabaurrear...@gmail.com
>
>
>
> Muchas gracias por vuestro tiempo y colaboración... danielabaurrearuiz
>

Hola Daniel, yo con gusto le ayudo. Escríbame a mi correo y coordinamos una
llamada.

Saludos desde Chile

Francisco Cid T

Re: Debian ISOs on USB stick

2024-04-03 Thread David Christensen 

On 4/3/24 05:56, Thomas Schmitt wrote:

Hi,

i read from bytes 2085412 to 2085479:
   "Info rrmation Syste rm VolumeSYSTEM~"
which is similar to the alterations of one of the USB sticks shown in
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998#35

The web knows about a Microsoft folder named "System Volume Information".
   
https://answers.microsoft.com/en-us/windows/forum/all/system-volume-information-what-is-it-and-what-is/3bc81844-0baa-46bd-9949-4efb4678b677
   "whenever I put my flash-drive or my micro sd adapter and sd card into
my windows 8.1 something called "System Volume Information" is always
getting added on."

So did you perhaps show this USB stick to a running MS-Windows system ?


Have a nice day :)

Thomas



It is possible the drive was inserted into a Windows computer.


If and when I need a newer d-i, perhaps I will put the ISO onto a USB 
flash drive, conduct more experiments, and post the results.



I apologize for blaming d-i for what might be Dell, Intel, BIOS/UEFI, 
Microsoft, and/or other bugs.



David

Re: readonly installer, (SOLVED)

2024-04-03 Thread David Christensen 

On 4/3/24 08:16, David Wright wrote:

On Tue 02 Apr 2024 at 05:54:06 (-0700), David Christensen wrote:

On 4/1/24 11:35, DdB wrote:

Am 01.04.2024 um 18:52 schrieb David Christensen:

A bad USB flash drive would explain why you cannot boot the Debian
installer.  Please buy a good quality USB 3.0+ flash drive and try again.


A friend of mine just let me use an external CD-Drive with the netboot
image.


I thought about suggesting that in my last post, but did not want to
complicate things.  A key advantage of using a CD-R disc is that you
can verify the disc contents and/or checksum against the ISO and/or
checksum now and in the future.  This is not true for a USB flash
drive, because the Debian installer modifies the contents of the USB
flash drive when it runs.


If this troubles you, you can also use an SD card with a write-lock,
or a µSD card with a lock on the SD adaptor.

Check that the write-lock works with the logs when you plug it in,
or run fdisk/gdisk and immediately quit.

Cheers,
David.



I have a 128 MB USB flash drive from back in the day that includes a 
write protect switch.  There are few products today that offer that feature.



David

ConsultaInstalaciónDEBIAN

2024-04-03 Thread Daniel Abaurrea Ruiz 
Hola, aquí Daniel Abaurrea Ruiz desde Barcelona en España. Tengo 
cincuenta años de edad. Estudié arquitectura.



Mi nivel de conocimientos de hardware y software es el de usuario. 
Siempre me ha interesado mucho saber como funciona todo lo que me rodea. 
Por esta razón me gustaria aprender a instalar un sistema operativo 
debian en un ordenador portatil nuevo, comprado sin un sistema operativo 
windows instalado de serie.


He puesto este mensaje en vuestro sitio web porque estoy tratando de 
encontrar un curso en el que aprender a rea lizar el tipo de instalación 
que he descrito. He buscado información al respecto en internet pero me 
he perdido en la cantidad de información que he encontrado.


Existe algun colectivo de usuarios de debian que organice un curso en el 
que pueda aprender a realizar el tipo de instalación que he propuesto?


Dispongo de un ordenador portatil que puedo utilizar para practicar la 
instalación antes de intentarla en un ordenador portatil nuevo.


¿Alguien puede ayudarme a conseguir el obejetivo que me he propuesto?

No dudeis en contactar conmigo a traves de:

danielabaurrear...@gmail.com

Muchas gracias por vuestro tiempo y colaboración... danielabaurrearuiz

ConsultaInstal·lacióDebian

2024-04-03 Thread Daniel Abaurrea Ruiz 
Hola, aquí Daniel Abaurrea Ruiz des de Barcelona ciutat. Tinc cinquanta 
anys d’edat. Vaig estudiar arquitectura.


Els meus coneixements d’hardware i software son del nivell d’usuari. 
Sempre m’ha interessat molt saber com funciona tot el que m’envolta. Es 
per això que m’agradaria molt aprendre a instal·lar un sistema operatiu 
debian en un ordinador portàtil comprat sense que s’hi hagués instal·lat 
prèviament un sistema operatiu windows.


He decidit posar aquest missatge en el vostre lloc web perquè he 
intentat aprendre a fer la instal·lació cercant cursos e informació per 
internet però m’he perdut en la quantitat d’informació que he trobat a 
la xarxa.


Hi ha algun col·lectiu que organitzi un curs en el que aprendre a fer 
aquest tipus d’instal·lació?


Disposo d’un ordinador portàtil en el que podria assajar el procés 
d’instal·lació abans d’intentar-ho en un dispositiu nou comprat sense el 
sistema operatiu windows prèviament instal·lat.


Algú em pot orientar en aquest propòsit?

No dubteu a contactar amb mi:

danielabaurrear...@gmail.com 

Moltes gracies pel vostre temps i esforç... danielabaurrearuiz

ConsultaInstal·lacióDEBIAN

2024-04-03 Thread Daniel Abaurrea Ruiz 
Hola, aquí Daniel Abaurrea Ruiz des de Barcelona ciutat. Tinc cinquanta 
anys d’edat. Vaig estudiar arquitectura.


Els meus coneixements d’hardware i software son del nivell d’usuari. 
Sempre m’ha interessat molt saber com funciona tot el que m’envolta. Es 
per això que m’agradaria molt aprendre a instal·lar un sistema operatiu 
debian en un ordinador portàtil comprat sense que s’hi hagués instal·lat 
prèviament un sistema operatiu windows.


He decidit posar aquest missatge en el vostre lloc web perquè he 
intentat aprendre a fer la instal·lació cercant cursos e informació per 
internet però m’he perdut en la quantitat d’informació que he trobat a 
la xarxa.


Hi ha algun col·lectiu que organitzi un curs en el que aprendre a fer 
aquest tipus d’instal·lació?


Disposo d’un ordinador portàtil en el que podria assajar el procés 
d’instal·lació abans d’intentar-ho en un dispositiu nou comprat sense el 
sistema operatiu windows prèviament instal·lat.


Algú em pot orientar en aquest propòsit?

No dubteu a contactar amb mi:

danielabaurrear...@gmail.com

Moltes gracies pel vostre temps i esforç... danielabaurrearuiz

Fwd: Delivery Status Notification (Failure)

2024-04-03 Thread Carlos Villiere 
-- Forwarded message -
De: Mail Delivery Subsystem 
Date: mar, 2 abr 2024 a las 15:11
Subject: Delivery Status Notification (Failure)
To: 


[image: Icono de error]
No se ha encontrado la dirección
Tu mensaje no se ha entregado a *al.privado...@a.la.lista.com* porque no se
ha encontrado el dominio a.la.lista.com. Comprueba que no haya erratas ni
espacios innecesarios y vuelve a intentarlo.
MÁS INFORMACIÓN 
La respuesta fue:

DNS Error: DNS type 'mx' lookup of a.la.lista.com responded with code
NXDOMAIN Domain name not found: a.la.lista.com For more information, go to
https://support.google.com/mail/?p=BadRcptDomain



-- Forwarded message --
From: Carlos Villiere 
To: al.privado...@a.la.lista.com
Cc:
Bcc:
Date: Tue, 2 Apr 2024 15:09:05 -0300
Subject: Re: Paquetes snap sin snap.
- Message truncated -

Re: [Sid] Nouveau: only one monitor after 6.6.15 to 6.7.9 upgrade

2024-04-03 Thread Sven Joachim 
On 2024-04-03 21:39 +0200, Greg wrote:

> I have two HP Z30i connected to Nvidia GeForce GTX 670. After last
> upgrade I'm able to use only one monitor.
>
> When running linux-image-6.7.9:
>
> # dmesg | grep nouveau | cut -b 16-
> nouveau :01:00.0: vgaarb: deactivate vga console
> nouveau :01:00.0: NVIDIA GK104 (0e4090a2)
> nouveau :01:00.0: bios: version 80.04.19.00.0f
> nouveau :01:00.0: fb: 2048 MiB GDDR5
> nouveau :01:00.0: DRM: VRAM: 2048 MiB
> nouveau :01:00.0: DRM: GART: 1048576 MiB
> nouveau :01:00.0: DRM: TMDS table version 2.0
> nouveau :01:00.0: DRM: MM: using COPY for buffer copies
> snd_hda_intel :01:00.1: bound :01:00.0 (ops
> nv50_audio_component_bind_ops [nouveau])
> [drm] Initialized nouveau 1.4.0 20120801 for :01:00.0 on minor 0
> fbcon: nouveaudrmfb (fb0) is primary device
> nouveau :01:00.0: vgaarb: VGA decodes changed:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
> # xrandr
> Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 16384 x 16384
> DVI-I-1 connected 2560x1600+0+0 (normal left inverted right x axis y
> axis) 641mm x 400mm
>2560x1600 59.97*+
>1920x1200 59.95
>1920x1080 60.00
>1600x1200 60.00
>1680x1050 59.88
>1280x1024 60.02
>1440x900  59.90
>1280x800  59.91
>1280x720  60.00
>1024x768  60.00
>800x600   60.32
>640x480   59.94
>720x400   70.08
> DVI-D-1 disconnected (normal left inverted right x axis y axis)
> HDMI-1 disconnected (normal left inverted right x axis y axis)
> DP-1 disconnected (normal left inverted right x axis y axis)
>
> When running linux-image-6.6.15:
>
> # dmesg | grep nouveau | cut -b 16-
> nouveau :01:00.0: vgaarb: deactivate vga console
> nouveau :01:00.0: NVIDIA GK104 (0e4090a2)
> nouveau :01:00.0: bios: version 80.04.19.00.0f
> nouveau :01:00.0: fb: 2048 MiB GDDR5
> nouveau :01:00.0: DRM: VRAM: 2048 MiB
> nouveau :01:00.0: DRM: GART: 1048576 MiB
> nouveau :01:00.0: DRM: TMDS table version 2.0
> nouveau :01:00.0: DRM: DCB version 4.0
> nouveau :01:00.0: DRM: DCB outp 00: 01000f02 00020030
> nouveau :01:00.0: DRM: DCB outp 01: 02000f00 
> nouveau :01:00.0: DRM: DCB outp 02: 08011f82 00020030
> nouveau :01:00.0: DRM: DCB outp 03: 02022f62 00020010
> nouveau :01:00.0: DRM: DCB outp 04: 04833fb6 0f420010
> nouveau :01:00.0: DRM: DCB outp 05: 04033f72 00020010
> nouveau :01:00.0: DRM: DCB conn 00: 1030
> nouveau :01:00.0: DRM: DCB conn 01: 00020131
> nouveau :01:00.0: DRM: DCB conn 02: 00010261
> nouveau :01:00.0: DRM: DCB conn 03: 2346
> nouveau :01:00.0: DRM: MM: using COPY for buffer copies
> snd_hda_intel :01:00.1: bound :01:00.0 (ops
> nv50_audio_component_bind_ops [nouveau])
> [drm] Initialized nouveau 1.4.0 20120801 for :01:00.0 on minor 0
> nouveau :01:00.0: vgaarb: VGA decodes changed:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem
> fbcon: nouveaudrmfb (fb0) is primary device
> nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
> # xrandr
> Screen 0: minimum 320 x 200, current 5120 x 1600, maximum 16384 x 16384
> DVI-I-1 connected 2560x1600+2560+0 (normal left inverted right x axis
> y axis) 641mm x 400mm
>2560x1600 59.97*+
>1920x1200 59.95
>1920x1080 60.00
>1600x1200 60.00
>1680x1050 59.88
>1280x1024 60.02
>1440x900  59.90
>1280x800  59.91
>1280x720  60.00
>1024x768  60.00
>800x600   60.32
>640x480   59.94
>720x400   70.08
> DVI-D-1 connected 2560x1600+0+0 (normal left inverted right x axis y
> axis) 641mm x 400mm
>2560x1600 59.97*+
>1920x1200 59.95
>1920x1080 60.00
>1600x1200 60.00
>1680x1050 59.88
>1280x1024 60.02
>1440x900  59.90
>1280x800  59.91
>1280x720  60.00
>1024x768  60.00
>800x600   60.32
>640x480   59.94
>720x400   70.08
> HDMI-1 disconnected (normal left inverted right x axis y axis)
> DP-1 disconnected (normal left inverted right x axis y axis)
>
> Any suggestions?

File a bug against the kernel: reboot to the 6.7 kernel if it is not
currently running, install the reportbug package if it is not installed
already, then run

$ reportbug linux-image-$(uname -r)

Good luck,
Sven

[Sid] Nouveau: only one monitor after 6.6.15 to 6.7.9 upgrade

2024-04-03 Thread Greg 

Hi there,

I have two HP Z30i connected to Nvidia GeForce GTX 670. After last 
upgrade I'm able to use only one monitor.


When running linux-image-6.7.9:

# dmesg | grep nouveau | cut -b 16-
nouveau :01:00.0: vgaarb: deactivate vga console
nouveau :01:00.0: NVIDIA GK104 (0e4090a2)
nouveau :01:00.0: bios: version 80.04.19.00.0f
nouveau :01:00.0: fb: 2048 MiB GDDR5
nouveau :01:00.0: DRM: VRAM: 2048 MiB
nouveau :01:00.0: DRM: GART: 1048576 MiB
nouveau :01:00.0: DRM: TMDS table version 2.0
nouveau :01:00.0: DRM: MM: using COPY for buffer copies
snd_hda_intel :01:00.1: bound :01:00.0 (ops 
nv50_audio_component_bind_ops [nouveau])

[drm] Initialized nouveau 1.4.0 20120801 for :01:00.0 on minor 0
fbcon: nouveaudrmfb (fb0) is primary device
nouveau :01:00.0: vgaarb: VGA decodes changed: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem

nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
# xrandr
Screen 0: minimum 320 x 200, current 2560 x 1600, maximum 16384 x 16384
DVI-I-1 connected 2560x1600+0+0 (normal left inverted right x axis y 
axis) 641mm x 400mm

   2560x1600 59.97*+
   1920x1200 59.95
   1920x1080 60.00
   1600x1200 60.00
   1680x1050 59.88
   1280x1024 60.02
   1440x900  59.90
   1280x800  59.91
   1280x720  60.00
   1024x768  60.00
   800x600   60.32
   640x480   59.94
   720x400   70.08
DVI-D-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

When running linux-image-6.6.15:

# dmesg | grep nouveau | cut -b 16-
nouveau :01:00.0: vgaarb: deactivate vga console
nouveau :01:00.0: NVIDIA GK104 (0e4090a2)
nouveau :01:00.0: bios: version 80.04.19.00.0f
nouveau :01:00.0: fb: 2048 MiB GDDR5
nouveau :01:00.0: DRM: VRAM: 2048 MiB
nouveau :01:00.0: DRM: GART: 1048576 MiB
nouveau :01:00.0: DRM: TMDS table version 2.0
nouveau :01:00.0: DRM: DCB version 4.0
nouveau :01:00.0: DRM: DCB outp 00: 01000f02 00020030
nouveau :01:00.0: DRM: DCB outp 01: 02000f00 
nouveau :01:00.0: DRM: DCB outp 02: 08011f82 00020030
nouveau :01:00.0: DRM: DCB outp 03: 02022f62 00020010
nouveau :01:00.0: DRM: DCB outp 04: 04833fb6 0f420010
nouveau :01:00.0: DRM: DCB outp 05: 04033f72 00020010
nouveau :01:00.0: DRM: DCB conn 00: 1030
nouveau :01:00.0: DRM: DCB conn 01: 00020131
nouveau :01:00.0: DRM: DCB conn 02: 00010261
nouveau :01:00.0: DRM: DCB conn 03: 2346
nouveau :01:00.0: DRM: MM: using COPY for buffer copies
snd_hda_intel :01:00.1: bound :01:00.0 (ops 
nv50_audio_component_bind_ops [nouveau])

[drm] Initialized nouveau 1.4.0 20120801 for :01:00.0 on minor 0
nouveau :01:00.0: vgaarb: VGA decodes changed: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem

fbcon: nouveaudrmfb (fb0) is primary device
nouveau :01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
# xrandr
Screen 0: minimum 320 x 200, current 5120 x 1600, maximum 16384 x 16384
DVI-I-1 connected 2560x1600+2560+0 (normal left inverted right x axis y 
axis) 641mm x 400mm

   2560x1600 59.97*+
   1920x1200 59.95
   1920x1080 60.00
   1600x1200 60.00
   1680x1050 59.88
   1280x1024 60.02
   1440x900  59.90
   1280x800  59.91
   1280x720  60.00
   1024x768  60.00
   800x600   60.32
   640x480   59.94
   720x400   70.08
DVI-D-1 connected 2560x1600+0+0 (normal left inverted right x axis y 
axis) 641mm x 400mm

   2560x1600 59.97*+
   1920x1200 59.95
   1920x1080 60.00
   1600x1200 60.00
   1680x1050 59.88
   1280x1024 60.02
   1440x900  59.90
   1280x800  59.91
   1280x720  60.00
   1024x768  60.00
   800x600   60.32
   640x480   59.94
   720x400   70.08
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)

Any suggestions?
Greg

Re: Comment installer Bookworm sur un HP elite Mini 600 G9 ? [RESOLU]

2024-04-03 Thread François LE GAD 

Le 03/04/2024 à 10:22, Olivier a écrit :


En redémarrant avec l'installeur Bookworm inséré (j'avais
préalablement donné la priorité du boot aux disques USB), la machine
m'a lancé l'installation de Debian !

En résumé, il faut:
- désactiver le Secure Boot et la Fast Boot
- donner la priorité du boot aux clés USB
- insérer sa clé et démarrer

Avec certains bios mal embouchés (c'est le cas chez moi), il peut être 
nécessaire d'appuyer sur une touche, ESC ou une touche de fonction, pour 
démarrer sur la clé, même si l'USB est prioritaire.


--
François

Re: readonly installer, (SOLVED)

2024-04-03 Thread David Wright 
On Tue 02 Apr 2024 at 05:54:06 (-0700), David Christensen wrote:
> On 4/1/24 11:35, DdB wrote:
> > Am 01.04.2024 um 18:52 schrieb David Christensen:
> > > A bad USB flash drive would explain why you cannot boot the Debian
> > > installer.  Please buy a good quality USB 3.0+ flash drive and try again.
> > 
> > A friend of mine just let me use an external CD-Drive with the netboot
> > image.
> 
> I thought about suggesting that in my last post, but did not want to
> complicate things.  A key advantage of using a CD-R disc is that you
> can verify the disc contents and/or checksum against the ISO and/or
> checksum now and in the future.  This is not true for a USB flash
> drive, because the Debian installer modifies the contents of the USB
> flash drive when it runs.

If this troubles you, you can also use an SD card with a write-lock,
or a µSD card with a lock on the SD adaptor.

Check that the write-lock works with the logs when you plug it in,
or run fdisk/gdisk and immediately quit.

Cheers,
David.

Re: Debian 10 «Buster» (old old stable) se mueve al repositorio archivador

2024-04-03 Thread Camaleón 
El 2024-04-03 a las 12:45 +, Eduardo A. Riquelme escribió:

(mando también a la lista)

>> Hola,
>> 
>> Pues eso, mando la noticia para quien quiera instalar (o usar) esta
>> versión y no la encuentre en las réplicas habituales:
>> 
>> Debian 10 "buster" moved to archive.debian.org
>> https://lists.debian.org/debian-devel-announce/2024/03/msg3.html
>> 
>> Quien todavía use esta versión seguramente tendrá que actualizar su
>> archivo sources.list para reflejar este cambio, si quiere instalar algún
>> paquete, ya que no recibe actualizaciones desde el canal normalizado
>> (sí a través de LTS hasta el 30-6-2024).

> Buen Dia Maestro,
> 
> Me podría guiar como apuntar el sources.list para recibir las actualización a 
> través de LTS, por favor.

Copipego la información de la wiki en inglés porque, para variar, está 
más actualizada que la versión en español:


https://wiki.debian.org/LTS/Using

Using Debian Long Term Support (LTS)

The next LTS version will be Debian 10 buster and will be supported 
from August 2022 to 2024-06-30. To receive security updates, your 
/etc/apt/sources.list should look like this one:

deb http://deb.debian.org/debian/ buster main contrib non-free
deb-src http://deb.debian.org/debian/ buster main contrib non-free

deb http://security.debian.org/ buster/updates main contrib non-free
deb-src http://security.debian.org/ buster/updates main contrib non-free


Ojo, lo anterior es válido para Debian 10 (buster). Versiones anteriores 
(p. ej. Strech) ya no admiten LTS.

> Otra favor muy grande para Strech donde puedo conseguir las ultimas 
> actualizaciones para descargar o apuntar con sources.list

Debian 9 (strech) ya no se actualiza, pero los paquetes estáticos siguen
estando disponibles en el repositorio archivador:

deb http://archive.debian.org/debian/ stretch contrib main non-free

> Un gran abrazo y un cordial saludo
> 
> Edu
> 
> Enviado desde Correo para 
> Windows

Saludos,

-- 
Camaleón

Re: Debian ISOs on USB stick

2024-04-03 Thread Thomas Schmitt 
Hi,

i read from bytes 2085412 to 2085479:
  "Info rrmation Syste rm VolumeSYSTEM~"
which is similar to the alterations of one of the USB sticks shown in
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998#35

The web knows about a Microsoft folder named "System Volume Information".
  
https://answers.microsoft.com/en-us/windows/forum/all/system-volume-information-what-is-it-and-what-is/3bc81844-0baa-46bd-9949-4efb4678b677
  "whenever I put my flash-drive or my micro sd adapter and sd card into
   my windows 8.1 something called "System Volume Information" is always
   getting added on."

So did you perhaps show this USB stick to a running MS-Windows system ?


Have a nice day :)

Thomas

Re: Debian ISOs on USB stick

2024-04-03 Thread Thomas Schmitt 
Hi,

David Christensen wrote:
> # cmp --verbose debian-11.3.0-amd64-netinst.iso /dev/sdb

I got my copy from
  
https://get.debian.org/images/archive/11.3.0/amd64/iso-cd/debian-11.3.0-amd64-netinst.iso
SHA256 matches:
  7892981e1da216e79fb3a1536ce5ebab157afdd20048fe458f2ae34fbc26c19b

In a further mail:
> https://cdimage.debian.org/cdimage/archive/11.3.0/amd64/iso-cd/

Same SHA256 there.


>   2083201   0 377

Byte counting of cmp is decimal and starts at 1. xorriso can search for
files which have their data in a block range. 2083201 / 2048 = block 1017.
Range size in this case is just 1 block:

  $ xorriso -indev debian-11.3.0-amd64-netinst.iso -find / -lba_range 1017 1 
-exec report_lba --
  ...
  Report layout: xt , Startlba ,   Blocks , Filesize , ISO image path
  File data lba:  0 , 1016 , 1296 ,  2654208 , '/boot/grub/efi.img'

So it's indeed occupied by the FAT filesystem image which contains the
EFI-specific boot equipment.

>   4719105   0  56

Byte 4719105 is in block 2304, i.e. still in /boot/grub/efi.img, which
has bytes up to the end of block 2311.

I guess the bytes with the 2xx numbers are the directory change and
the 4xx numbers are content of new files.


You could mount both ISOs (e.g. at /mnt/iso1 and /mnt/iso2) and then the
two FAT image files (e.g. /mnt/iso1/boot/grub/efi.img and
/mnt/iso2/boot/grub/efi.img) in order to learn which files have emerged
or changed in the USB stick's mounted FAT filesystem.

Maybe we find a new ESP groper additionaly to Lenovo and Microsoft.
Usually they leave traces for which one can search in the web.


Have a nice day :)

Thomas

Re: HDD long-term data storage with ensured integrity

2024-04-03 Thread Jonathan Dowland 
On Tue Apr 2, 2024 at 10:57 PM BST, David Christensen wrote:
> AIUI neither LVM nor ext4 have data and metadata checksum and correction 
> features.  But, it should be possible to achieve such by including 
> dm-integrity (for checksumming) and some form of RAID (for correction) 
> in the storage stack.  I need to explore that possibility further.

It would be nice to have checksumming and parity stuff in the filesystem
layer, as BTRFS and XFS offer, but failing that, you can do it above
that layer using tried-and-tested tools such as sha1sum, par2, etc.

I personally would not rely upon RAID for anything except availability.
My advice is once you've detected corruption, which is exceedingly rare,
restore from backup.

-- 
Please do not CC me for listmail.

  Jonathan Dowland
✎j...@debian.org
   https://jmtd.net

Re: HDD long-term data storage with ensured integrity

2024-04-03 Thread David Christensen 

On 4/2/24 14:57, David Christensen wrote:
AIUI neither LVM nor ext4 have data and metadata checksum and correction 
features.  But, it should be possible to achieve such by including 
dm-integrity (for checksumming) and some form of RAID (for correction) 
in the storage stack.  I need to explore that possibility further.



I have RTFM dm-integrity before and it is still experimental.  I need 
something that is production ready:


https://manpages.debian.org/bookworm/cryptsetup-bin/cryptsetup.8.en.html

Authenticated disk encryption (EXPERIMENTAL)


David

Re: Debian ISOs on USB stick, was: SOLVED

2024-04-03 Thread David Christensen 

On 4/3/24 03:36, David Christensen wrote:

On 4/3/24 00:30, Thomas Schmitt wrote:

Hi,

David Christensen wrote:
It's a relatively simple experiment to confirm that a USB flash drive 
with

d-i changes after the first boot.


This could still be
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998
where Lenovo BIOS and/or MS-Windows altered the USB stick.



Same for finding which bytes change.


I fail to find this particular info in
   Date: Tue, 2 Apr 2024 14:46:42 -0700
   From: David Christensen 
   Message-ID: 

If we have the exact ISO name (i.e. URL from where it stems) and the
byte address of the alteration, xorriso can find the affected file, if
any.

In case of bug #1056998 it was the EFI partition image 
/boot/grub/efi.img.

Mounting the altered and unaltered image files showed changes in the
FAT filesystem which point to the culprits Lenovo and Microsoft.


The other plausible way of altering the ISO image on the stick would be
adding a new partition.
The MBR partition table is part of the Debian ISO and thus part of the
checksummed area. Even if all other alterations happen after the end
of the checksummed ISO image, the changed partition table will cause the
Debian checksum to become invalid.

(I am not aware that Debian installer changes the table. If it does 
indeed

then this might be worth a new bug discussion.)


Have a nice day :)

Thomas



2024-04-03 03:29:18 root@laalaa /samba/dpchrist/iso/debian/11.3.0
# cmp --verbose debian-11.3.0-amd64-netinst.iso /dev/sdb
   2083201   0 377
   2083202   0 377
   2083203   0 377
   2085249   0 377
   2085250   0 377
   2085251   0 377
   2085409   0 102
   2085410   0  40
   2085412   0 111
   2085414   0 156
   2085416   0 146
   2085418   0 157
   2085420   0  17
   2085422   0 162
   2085423   0 162
   2085425   0 155
   2085427   0 141
   2085429   0 164
   2085431   0 151
   2085433   0 157
   2085437   0 156
   2085441   0   1
   2085442   0 123
   2085444   0 171
   2085446   0 163
   2085448   0 164
   2085450   0 145
   2085452   0  17
   2085454   0 162
   2085455   0 155
   2085457   0  40
   2085459   0 126
   2085461   0 157
   2085463   0 154
   2085465   0 165
   2085469   0 155
   2085471   0 145
   2085473   0 123
   2085474   0 131
   2085475   0 123
   2085476   0 124
   2085477   0 105
   2085478   0 115
   2085479   0 176
   2085480   0  61
   2085481   0  40
   2085482   0  40
   2085483   0  40
   2085484   0  26
   2085486   0 167
   2085487   0 174
   2085488   0 277
   2085489   0 235
   2085490   0 124
   2085491   0 235
   2085492   0 124
   2085495   0 175
   2085496   0 277
   2085497   0 235
   2085498   0 124
   2085500   0   5
   4719105   0  56
   4719106   0  40
   4719107   0  40
   4719108   0  40
   4719109   0  40
   4719110   0  40
   4719111   0  40
   4719112   0  40
   4719113   0  40
   4719114   0  40
   4719115   0  40
   4719116   0  20
   4719118   0 167
   4719119   0 174
   4719120   0 277
   4719121   0 235
   4719122   0 124
   4719123   0 235
   4719124   0 124
   4719127   0 175
   4719128   0 277
   4719129   0 235
   4719130   0 124
   4719132   0   5
   4719137   0  56
   4719138   0  56
   4719139   0  40
   4719140   0  40
   4719141   0  40
   4719142   0  40
   4719143   0  40
   4719144   0  40
   4719145   0  40
   4719146   0  40
   4719147   0  40
   4719148   0  20
   4719150   0 167
   4719151   0 174
   4719152   0 277
   4719153   0 235
   4719154   0 124
   4719155   0 235
   4719156   0 124
   4719159   0 175
   4719160   0 277
   4719161   0 235
   4719162   0 124
   4719169   0 102
   4719170   0 107
   4719172   0 165
   4719174   0 151
   4719176   0 144
   4719180   0  17
   4719182   0 377
   4719183   0 377
   4719184   0 377
   4719185   0 377
   4719186   0 377
   4719187   0 377
   4719188   0 377
   4719189   0 377
   4719190   0 377
   4719191   0 377
   4719192   0 377
   4719193   0 377
   4719194   0 377
   4719197   0 377
   4719198   0 377
   4719199   0 377
   4719200   0 377
   4719201   0   1
   4719202   0 111
   4719204   0 156
   4719206   0 144
   4719208   0 145
   4719210   0 170
   4719212   0  17
   4719214   0 377
   4719215   0 145
   4719217   0 162
   4719219   0 126
   4719221   0 157
   4719223   0 154
   4719225   0 165
   4719229   0 155
   4719231   0 145
   4719233   0 111
   4719234   0 116
   4719235   0 104
   4719236   0 105
   4719237   0 130
   4719238   0 105
   4719239   0 176
   4719240   0  61
   4719241   0  40
   4719242   0  40
   4719243   0  40
   4719244   0  40
   4719246   0 171
   4719247   0 174
   4719248   0 277
   4719249   0 235
   4719250   0 124
   4719251   0 235
   4719252   0 124
   4719255   0 175
   4719256   0 277
   4719257   0 235
   4719258   0 124
   4719259   0   1
   4719260   0   5
   4719261   0 114
   4721153   0 173
   4721155   0  71
   4721157   0 101
   4721159   0  65
   4721161   0 104
   4721163   0 101
   4721165   0 106
   4721167   0  65
   4721169   0  67
   4721171   0  55
  

Re: Debian ISOs on USB stick, was: SOLVED

2024-04-03 Thread David Christensen 

On 4/3/24 00:30, Thomas Schmitt wrote:

Hi,

David Christensen wrote:

It's a relatively simple experiment to confirm that a USB flash drive with
d-i changes after the first boot.


This could still be
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998
where Lenovo BIOS and/or MS-Windows altered the USB stick.



Same for finding which bytes change.


I fail to find this particular info in
   Date: Tue, 2 Apr 2024 14:46:42 -0700
   From: David Christensen 
   Message-ID: 

If we have the exact ISO name (i.e. URL from where it stems) and the
byte address of the alteration, xorriso can find the affected file, if
any.

In case of bug #1056998 it was the EFI partition image /boot/grub/efi.img.
Mounting the altered and unaltered image files showed changes in the
FAT filesystem which point to the culprits Lenovo and Microsoft.


The other plausible way of altering the ISO image on the stick would be
adding a new partition.
The MBR partition table is part of the Debian ISO and thus part of the
checksummed area. Even if all other alterations happen after the end
of the checksummed ISO image, the changed partition table will cause the
Debian checksum to become invalid.

(I am not aware that Debian installer changes the table. If it does indeed
then this might be worth a new bug discussion.)


Have a nice day :)

Thomas



2024-04-03 03:29:18 root@laalaa /samba/dpchrist/iso/debian/11.3.0
# cmp --verbose debian-11.3.0-amd64-netinst.iso /dev/sdb
  2083201   0 377
  2083202   0 377
  2083203   0 377
  2085249   0 377
  2085250   0 377
  2085251   0 377
  2085409   0 102
  2085410   0  40
  2085412   0 111
  2085414   0 156
  2085416   0 146
  2085418   0 157
  2085420   0  17
  2085422   0 162
  2085423   0 162
  2085425   0 155
  2085427   0 141
  2085429   0 164
  2085431   0 151
  2085433   0 157
  2085437   0 156
  2085441   0   1
  2085442   0 123
  2085444   0 171
  2085446   0 163
  2085448   0 164
  2085450   0 145
  2085452   0  17
  2085454   0 162
  2085455   0 155
  2085457   0  40
  2085459   0 126
  2085461   0 157
  2085463   0 154
  2085465   0 165
  2085469   0 155
  2085471   0 145
  2085473   0 123
  2085474   0 131
  2085475   0 123
  2085476   0 124
  2085477   0 105
  2085478   0 115
  2085479   0 176
  2085480   0  61
  2085481   0  40
  2085482   0  40
  2085483   0  40
  2085484   0  26
  2085486   0 167
  2085487   0 174
  2085488   0 277
  2085489   0 235
  2085490   0 124
  2085491   0 235
  2085492   0 124
  2085495   0 175
  2085496   0 277
  2085497   0 235
  2085498   0 124
  2085500   0   5
  4719105   0  56
  4719106   0  40
  4719107   0  40
  4719108   0  40
  4719109   0  40
  4719110   0  40
  4719111   0  40
  4719112   0  40
  4719113   0  40
  4719114   0  40
  4719115   0  40
  4719116   0  20
  4719118   0 167
  4719119   0 174
  4719120   0 277
  4719121   0 235
  4719122   0 124
  4719123   0 235
  4719124   0 124
  4719127   0 175
  4719128   0 277
  4719129   0 235
  4719130   0 124
  4719132   0   5
  4719137   0  56
  4719138   0  56
  4719139   0  40
  4719140   0  40
  4719141   0  40
  4719142   0  40
  4719143   0  40
  4719144   0  40
  4719145   0  40
  4719146   0  40
  4719147   0  40
  4719148   0  20
  4719150   0 167
  4719151   0 174
  4719152   0 277
  4719153   0 235
  4719154   0 124
  4719155   0 235
  4719156   0 124
  4719159   0 175
  4719160   0 277
  4719161   0 235
  4719162   0 124
  4719169   0 102
  4719170   0 107
  4719172   0 165
  4719174   0 151
  4719176   0 144
  4719180   0  17
  4719182   0 377
  4719183   0 377
  4719184   0 377
  4719185   0 377
  4719186   0 377
  4719187   0 377
  4719188   0 377
  4719189   0 377
  4719190   0 377
  4719191   0 377
  4719192   0 377
  4719193   0 377
  4719194   0 377
  4719197   0 377
  4719198   0 377
  4719199   0 377
  4719200   0 377
  4719201   0   1
  4719202   0 111
  4719204   0 156
  4719206   0 144
  4719208   0 145
  4719210   0 170
  4719212   0  17
  4719214   0 377
  4719215   0 145
  4719217   0 162
  4719219   0 126
  4719221   0 157
  4719223   0 154
  4719225   0 165
  4719229   0 155
  4719231   0 145
  4719233   0 111
  4719234   0 116
  4719235   0 104
  4719236   0 105
  4719237   0 130
  4719238   0 105
  4719239   0 176
  4719240   0  61
  4719241   0  40
  4719242   0  40
  4719243   0  40
  4719244   0  40
  4719246   0 171
  4719247   0 174
  4719248   0 277
  4719249   0 235
  4719250   0 124
  4719251   0 235
  4719252   0 124
  4719255   0 175
  4719256   0 277
  4719257   0 235
  4719258   0 124
  4719259   0   1
  4719260   0   5
  4719261   0 114
  4721153   0 173
  4721155   0  71
  4721157   0 101
  4721159   0  65
  4721161   0 104
  4721163   0 101
  4721165   0 106
  4721167   0  65
  4721169   0  67
  4721171   0  55
  4721173   0  71
  4721175   0 102
  4721177   0  63
  4721179   0  61
  4721181   0  55
  4721183   0  64
  4721185   0  71
  4721187   0  62
  4721189   0 105
  4721191   0  55
  4721193   0 102
  4721195   0  66
  4721197   0 105

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

2024-04-03 Thread Jonathan Chung 
Hi, 

I think that the core problem which led to this also was on GRPCs side.
They should not tell users to compile their library but rather point
them to install it from their distros' packet manager
(https://grpc.io/docs/languages/cpp/quickstart/#install-grpc) if
possible. I will try to do the switch tonight as I just use GRPC as
library in a project and don't need to change anything in the GRPC
source.

Have a nice day,

Jonathan Chung

Am Mittwoch, dem 03.04.2024 um 08:35 +0200 schrieb Thomas Schmitt:
> Hi,
> 
> Chung  Jonathan wrote:
> > Yes, I think the local fix is the way to go.
> 
> I wrote:
> > > (You forgot to Cc: debian-user@lists.debian.org.
> > > Consider to send your mail to the list address, too. I too would
> > > then
> > > resend my following reply to the list.)
> 
> Since my "following reply" is quoted in Jonathan Chung's reply to the
> list
> i don't have to resend it. (I gave my opinion that the problem is not
> a
> bug in the context of Debian 12 or 13 and pointed to
> https://wiki.debian.org/BuildingTutorial for a private fix of the
> problem.)
> 
> 
> Jeffrey Walton wrote:
> > Your problem is one that plagues Linux. You compile and link
> > against
> > one version of a library, and then you runtime link against another
> > version.
> 
> This should not be a problem with a well maintained library which
> cares
> to stay ABI compatible with its older releases.
> In the present case it was a bug in the loading program pigz which
> prevented zlib from being usable.
> 
> 
> > I consider it a
> > security bug since essentially random libraries are being loaded at
> > runtime.
> > To fix the problem yourself, add an RPATH to your LDFLAGS when
> > building your program:
> >     -Wl,-rpath=/path/to/expected/libz -Wl,--enable-new-dtags
> 
> Well, this is nearly as unflexible as static compilation but does not
> seem to prevent the use of a replaced library at the given path.
> 
> Using .so files has its advantages and disadvantages. For a distro
> the
> advantage (without the pigz bug) is that customers of different
> versions
> of a library can be consolidated to using the newest available
> version.
> An advantage for the user is that bugs in a library can be fixed
> without
> the need for re-building all its customers.
> 
> 
> Have a nice day :)
> 
> Thomas
>

Re: Comment installer Bookworm sur un HP elite Mini 600 G9 ? [RESOLU]

2024-04-03 Thread Olivier 
En désactivant l'option Fast Boot du BIOS, le Boot Menu m'a affiché la
possibilité de démarrer avec la clé USB !

En redémarrant avec l'installeur Bookworm inséré (j'avais
préalablement donné la priorité du boot aux disques USB), la machine
m'a lancé l'installation de Debian !

En résumé, il faut:
- désactiver le Secure Boot et la Fast Boot
- donner la priorité du boot aux clés USB
- insérer sa clé et démarrer



Le ven. 29 mars 2024 à 19:31, Lamourec Alain  a écrit :
>
> Bonjour
>
> Vois-tu ta clé dans les médias du BIOS ?
> Utilises-tu Ventoy pour booter l'ISO ?
> Sinon change de clé, ça arrive qu'il y a des clés qui sont
> capricieuses
>
> Olivier  writes:
>
> > Bonjour,
> >
> > Je viens d'acquérir un HP elite Mini 600 G9 d'occasion sur
> > lequel
> > Windows 11 est installé (BIOS U21 Ver 02.05.00 du 08/23/2022).
> > Je souhaite installer Bookworm à la place.
> >
> > J'arrive à accéder au BIOS.
> > J'ai désactivé le Secure Boot et autorisé le boot depuis une clé
> > USB.
> > Le BIOS contient de multiples options exotiques de
> > configuration.
> >
> > Avec le menu de choix de media de boot, la clé USB sur laquelle
> > j'ai
> > installé l'installeur Debian n'est pas proposée.
> >
> > Que faire ?
> >
> > Slts
>
>
> --
> Lamourec Alain
>

Re: Comment installer Bookworm sur un HP elite Mini 600 G9 ?

2024-04-03 Thread Olivier 
Le ven. 29 mars 2024 à 19:31, Lamourec Alain  a écrit :
>
> Bonjour
>
> Vois-tu ta clé dans les médias du BIOS ?
Oui et non !
Dans le Boot Menu, la machine me propose :
- soit de démarrer avec le disque dur (sur lequel Windows 11 est installé),
- soit "de démarrer à partir d'un fichier".

Elle ne me propose pas, malheureusement, de démarrer avec la clé:
donc, la réponse est non

En choisissant l'option " démarrer à partir d'un fichier", je peux
parcourir soit le disque dur, soir la clé USB.
Donc la réponse est oui, je vois la clé !

C'est comme si la clé était lisible mais pas utilisable pour booter.

> Utilises-tu Ventoy pour booter l'ISO ?
> Sinon change de clé, ça arrive qu'il y a des clés qui sont
> capricieuses

J'ai utilisé trois clés différentes (1 avec Ventoy, 2 avec
l'installeur Debian) avec lesquelles j'ai dans le passé, réussi
plusieurs installations.


J'avoue complètement découvrir ce BIOS.
Celui-ci est truffé d'acronymes mystérieux (BIOS Sure Start, Secure
Platform Management, ...) qui multiplient à l'infini les combinaisons
de paramètres.

Si quelqu'un se rappelle avoir réussi à installer Linux sur ce type de
machine, qu'il n'hésite pas ...

Debian ISOs on USB stick, was: SOLVED

2024-04-03 Thread Thomas Schmitt 
Hi,

David Christensen wrote:
> It's a relatively simple experiment to confirm that a USB flash drive with
> d-i changes after the first boot.

This could still be
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056998
where Lenovo BIOS and/or MS-Windows altered the USB stick.


> Same for finding which bytes change.

I fail to find this particular info in
  Date: Tue, 2 Apr 2024 14:46:42 -0700
  From: David Christensen 
  Message-ID: 

If we have the exact ISO name (i.e. URL from where it stems) and the
byte address of the alteration, xorriso can find the affected file, if
any.

In case of bug #1056998 it was the EFI partition image /boot/grub/efi.img.
Mounting the altered and unaltered image files showed changes in the
FAT filesystem which point to the culprits Lenovo and Microsoft.


The other plausible way of altering the ISO image on the stick would be
adding a new partition.
The MBR partition table is part of the Debian ISO and thus part of the
checksummed area. Even if all other alterations happen after the end
of the checksummed ISO image, the changed partition table will cause the
Debian checksum to become invalid.

(I am not aware that Debian installer changes the table. If it does indeed
then this might be worth a new bug discussion.)


Have a nice day :)

Thomas

Re: Debian 12.5: pigz 2.6-1 fails with error message (Upstream issue 111)

2024-04-03 Thread Thomas Schmitt 
Hi,

Chung  Jonathan wrote:
> Yes, I think the local fix is the way to go.

I wrote:
> > (You forgot to Cc: debian-user@lists.debian.org.
> > Consider to send your mail to the list address, too. I too would then
> > resend my following reply to the list.)

Since my "following reply" is quoted in Jonathan Chung's reply to the list
i don't have to resend it. (I gave my opinion that the problem is not a
bug in the context of Debian 12 or 13 and pointed to
https://wiki.debian.org/BuildingTutorial for a private fix of the problem.)


Jeffrey Walton wrote:
> Your problem is one that plagues Linux. You compile and link against
> one version of a library, and then you runtime link against another
> version.

This should not be a problem with a well maintained library which cares
to stay ABI compatible with its older releases.
In the present case it was a bug in the loading program pigz which
prevented zlib from being usable.


> I consider it a
> security bug since essentially random libraries are being loaded at
> runtime.
> To fix the problem yourself, add an RPATH to your LDFLAGS when
> building your program:
> -Wl,-rpath=/path/to/expected/libz -Wl,--enable-new-dtags

Well, this is nearly as unflexible as static compilation but does not
seem to prevent the use of a replaced library at the given path.

Using .so files has its advantages and disadvantages. For a distro the
advantage (without the pigz bug) is that customers of different versions
of a library can be consolidated to using the newest available version.
An advantage for the user is that bugs in a library can be fixed without
the need for re-building all its customers.


Have a nice day :)

Thomas