and run it. I think it's
> "scanner:amd".
>
'dpkg-query -L scanner' will display the installed files.
>
>
> Thanks,
> Matt Timpson đ
>
>
> Sent with Proton Mail secure email.
>
> --- Forwarded Message ---
> From: Matt Timpson
>
On Tue, Apr 08, 2025 at 02:37:25PM +, Matt Timpson wrote:
> Hello,
>
> Dan told me to send this to the mailing list instead of individual people.
> This command worked:
>
> sudo apt install ./scanner_x86_64_1.7.2312301E.deb
>
> However, I still need to find the executable and run it. I thin
ith Proton Mail secure email.
--- Forwarded Message ---
From: Matt Timpson
Date: On Monday, April 7th, 2025 at 19:34
Subject: Re: Can you help me run Box64 on my Raspberry Pi 5?
To: Timothy M Butterworth
> Hello,
>
> Never mind, it worked the second time for some reason! Howeve
Hi Matt, all
Am 07.04.2025 um 18:54 schrieb basti:
Hello,
Raspberry pi uses arm and aarch64 (arm64). This is not x64 like Intel or
AMD.
From what I just learnt, Box64 (mentioned in this mail#s subject) is
actually an emulator to run on arm and then used to run x86 code.
So, my question h
Matt Timpson wrote:
You seem to have forgotten to copy the debian-user list, so I
have helpfully corrected that for you.
(Questions on the list are not an invitation to a personalized
support experience. Everyone is a volunteer here, including
you.)
> Hello,
>
> I bought a book scanner from a
o...@gmail.com> wrote:
>
> >
> >
> > On Mon, Apr 7, 2025 at 12:24âŻPM Matt Timpson
> wrote:
> >
> > > Hello all,
> > >
> > > I want to run a .deb file written for x64 processors on my Raspberry
> Pi 5, which I run Linux on. Unfortunate
and
> failed to pay computer technicians online to help me because most of
> them don't work in Linux.
>
>
> Thanks,
> Matt Timpson đ
> And also check this link:
> https://pi-apps.io/install-app/install-box64-on-linux-arm-device/[1]
You may also want to just `apt install box64` since according to
https://tracker.debian.org/pkg/box64 it's in Debian testing.
Stefan
; technicians online to help me because most of them don't work in Linux.
>
Best to start by telling us which .deb package you want to run
and where it comes from.
-dsr-
Timpson:
Hello all,
I want to run a .deb file written for x64 processors on my Raspberry Pi 5,
which I run Linux on. Unfortunately I don't know a damn thing about computers
and need step-by-step instructions. I have tried and failed to pay computer
technicians online to help me because mo
Hello all,
I want to run a .deb file written for x64 processors on my Raspberry Pi 5,
which I run Linux on. Unfortunately I don't know a damn thing about computers
and need step-by-step instructions. I have tried and failed to pay computer
technicians online to help me because most of
On Wed, Mar 26, 2025 at 07:48:16AM -0500, Richard Owlett wrote:
> On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > [SNIP]
> >
> > I normally use "sudo -s", which is the closest sudo approximation to
> > the traditional behvior of "su" (before it was broken in buster).
> >
>
> I don't understand the
Greg (HE12025-03-27):
> I'm certain sudo has its use cases, but all I do personally is su to
> root and update and upgrade my stable Bookworm using apt, so I feel no
> need to complexify the issue with sudo.
The fallacy in here being assuming, without stating it and without
justifying it that sudo
>
> "sudo -i" is meant to approximate the behavior of "su -". Before buster,
> nobody would have used that on a Debian system. It's horrible. The
> fact that people are now embracing it as a norm is even worse.
>
Why horrible?
David Wright writes:
> host!auser 09:57:47 /somewhere/that/is/obnoxiously/long/program-1.2.3$
> /bin/su --login
> Password:
> bullseye on /dev/sda5 toto05
> host 09:57:59 ~# cd /somewhere/that/is/obnoxiously/long/program-1.2.3
> host 09:58:08 /somewhere/that/is/obnoxiously/long/progra
On Wed, Mar 26, 2025 at 02:55:11PM -, Greg wrote:
> On 2025-03-26, Richard Owlett wrote:
>
> >> If he hasn't noticed yet, I doubt it.
> >
> > I agree.
> > If I understand what people want to accomplish by using command-line
> > options, I would likely have gone to System->Log Out ... and the
On 21/03/2025 20:38, J wrote:
But i must mention that *this passage from Debian Wiki seems incorrect*
Bind mount various virtual filesystems:
# for i in /dev /dev/pts /proc /sys /sys/firmware/efi/efivars /run;
do mount -B $i /mnt/$i; done
https://wiki.debian.org/GrubEFIReinstall#
On 20/03/2025 03:22, J wrote:
But before this oopsie deletion I have saved as a back-up at least
something from /boot folder, or maybe even everything.
Copy files from backup to /boot and to the EFI system partition
EFI/debian/BOOTX64.CSV
EFI/debian/fbx64.efi
EFI/debian/grub.cfg
EFI/debian/g
Greg Wooledge wrote:
...
> Maybe. If you haven't created an /etc/default/su file, then something
> like this:
>
> $ su
> # adduser richard
>
> may fail. You could work around it in various ways (e.g. explicitly
> typing out /usr/sbin/adduser richard).
>
> My recommendation is to create a
On Fri, Mar 28, 2025 at 8:42âŻPM Pier Antonio Corradini
wrote:
>
> I think I got it: the final step is to compare the fingerprint of the primary
> key, at the end of the command output
>
> PS C:\Users\CP\Documents\Linux\Debian12.10.0\HTTPVersion> gpg --verify
> SHA512SUMS.sign SHA512SUMS.txt
> gp
thenticated themselves by gpg --verify or alike.
If i'd knew a good solution then i'd post it to
debian...@lists.debian.org and be obstinate until i get a good answer.
But as it is, i cannot do more than offer human help and above wiki
page.
Have a nice day :)
Thomas
Hi,
Pier Antonio Corradini wrote:
> So now the authenticity check is complete and the authenticity is completely
> sure?
Yes. Until a quantum computer cracks the riddle how to generate an own
key with the same fingerprint.
(There are other risks, too, which are not prevented by signature with
unc
thenticity is completely
sure?
Thanks!
PA
Da: Thomas Schmitt
Inviato: VenerdĂŹ, 28 Marzo, 2025 18:04
A: debian-user@lists.debian.org
Cc: pierantonio.corrad...@gmail.com
Oggetto: Re: Help: debian-12.10.0-amd64-netinst.iso autenticity test
Hi,
i realize that i posted t
___
Da: Thomas Schmitt
Inviato: VenerdĂŹ, 28 Marzo, 2025 18:04
A: debian-user@lists.debian.org
Cc: pierantonio.corrad...@gmail.com
Oggetto: Re: Help: debian-12.10.0-amd64-netinst.iso autenticity test
Hi,
i realize that i posted the content of the wrong SHA512SUMS file.
The one i posted was from
Hi,
i realize that i posted the content of the wrong SHA512SUMS file.
The one i posted was from debian 12.7.0.
Nevertheless the SHA512 sums which i posted earlier are of the files
from 12.10.0 which i downloaded yesterday.
Pier Antonio Corradini wrote:
> The content of these links, seen now, is
see the same thing?
PA
Da: Thomas Schmitt
Inviato: VenerdĂŹ, 28 Marzo, 2025 14:42
A: debian-user@lists.debian.org
Cc: pierantonio.corrad...@gmail.com
Oggetto: Re: Help: debian-12.10.0-amd64-netinst.iso autenticity test
Hi,
Pier Antonio Corradini wrote
Max Nikulin (HE12025-03-28):
> Approximately a decade ago I
> noticed that new entries were not added to some history file, I do not
> remember if it was .bash_history or for some other tool, but the owner of
> the file was root. It was the reason why I
On 26/03/2025 18:55, Greg Wooledge wrote:
"sudo -i" is meant to approximate the behavior of "su -". Before buster,
nobody would have used that on a Debian system. It's horrible. The
fact that people are now embracing it as a norm is even worse.
It seems I have to clarify why I suggested name
Thank you for the answer.
The problem was I accidentally removed the */boot *folder, WHILE trying to
back it up. So there were only *OS folders *and something was missing.
I figured out later that *kernels are also stored in /boot *and tried to
reinstall the kernel manually, but ran into a number
Hi,
Pier Antonio Corradini wrote:
> 3D0BA303805111F651A88D96FC64867FFC678E43F3756F5F91B24A810D91015E459...
> C:\Users\CP\Documents\Linux\Debian12.10.0\VersioneHTTP\SHA512SUMS.txt
I get
36bf1f16bc4b9795122b7b3542a32f34c3be0ef294ff3a8bf43232df6554b69b569fe15d93c79ee48a47902e1a6ad87ca9966988cd4b
On 2025-03-28, David Wright wrote:
>
> As end-users are the people that computers are built and run
> for, I don't know why you'd find people's use of the term
> "slightly pejorative". (I assume you aren't calling out me
> in particular.)
I was calling myself out, not you. You have always been he
ntonio.corrad...@gmail.com
Oggetto: Re: Help: debian-12.10.0-amd64-netinst.iso autenticity test
Hi,
(Please Cc: debian-user@lists.debian.org with your replies.
I sent my mail with Cc; to you, because the X-Spam-Status: header of
your list mail did not indicate that you are subscribed to the list.
Da: Thomas Schmitt
Inviato: VenerdĂŹ, 28 Marzo, 2025 08:50
A: debian-user@lists.debian.org
Cc: pierantonio.corrad...@gmail.com
Oggetto: Re: Help: debian-12.10.0-amd64-netinst.iso autenticity test
Hi,
(Please Cc: debian-user@lists.debian.org with your replies.
I
Hi,
(Please Cc: debian-user@lists.debian.org with your replies.
I sent my mail with Cc; to you, because the X-Spam-Status: header of
your list mail did not indicate that you are subscribed to the list.)
Pier Antonio Corradini wrote:
> So... first step:
> PS C:\Users\CP> gpg --keyserver hkps://ke
On Wed, Mar 26, 2025 at 15:46:15 +0100, Nicolas George wrote:
> $ su
> # make install
>
> Whoopsie! The Makefile just pwned you.
That's a COMPLETELY separate discussion. Obviously I was referring to
software from reputable sources.
> $ make DESTDIR=/tmp/i install
> $ sud
On Thu 27 Mar 2025 at 22:14:03 (-0400), Michael Stone wrote:
> On Thu, Mar 27, 2025 at 08:29:50PM -0500, David Wright wrote:
> > Excellent, that solves the problem for those on old terminals or
> > lacking copy/paste. As for me, I'll continue to use /bin/su --login,
> > as I have for nigh on three
On Thu, Mar 27, 2025 at 08:29:50PM -0500, David Wright wrote:
Excellent, that solves the problem for those on old terminals or
lacking copy/paste. As for me, I'll continue to use /bin/su --login,
as I have for nigh on three decades, so that I land in my preferred,
consistent cwd, /root.
su -
do
On Thu 27 Mar 2025 at 17:05:56 (-), Greg wrote:
> On 2025-03-26, David Wright wrote:
> >
> > As posted earlier today, a file in sudoers.d/ makes trivial admin
> > tasks like monitoring and logging easier, particularly where the
> > programs concerned can cause damage if the wrong options are us
On Thu 27 Mar 2025 at 13:58:10 (-0400), Greg Wooledge wrote:
> On Thu, Mar 27, 2025 at 12:48:35 -0500, David Wright wrote:
> > It could be argued that it would be simple enough to communicate
> > the user's cwd to root, as a workaround, so that it didn't have to
> > be retyped.
>
> You know what d
Hi,
Pier Antonio Corradini wrote:
> Autenticity control (gpg --verify SHA512SUMS.sign SHA512SUMS.txt):
> [...]
> gpg: Â Â Â Â Â Â Â Â utilizzando la chiave RSA
> DF9B9C49EAA9298432589D76DA87E80D6294BE9B
> gpg: Firma BAD da "Debian CD signing key "
I assume that "Firma BAD" means bad signature.
I
ata 03/15/25 21:33:08 ora solare Europa occidentale
gpg:utilizzando la chiave RSA
DF9B9C49EAA9298432589D76DA87E80D6294BE9B
gpg: Firma BAD da "Debian CD signing key "
[sconosciuto]
I need help to obtain a good check about autenticity. Thanks!
P.A.
On 2025-03-26, David Wright wrote:
>
> As posted earlier today, a file in sudoers.d/ makes trivial admin
> tasks like monitoring and logging easier, particularly where the
> programs concerned can cause damage if the wrong options are used.
I'm certain sudo has its use cases, but all I do persona
On Thu, Mar 27, 2025 at 12:48:35 -0500, David Wright wrote:
> It could be argued that it would be simple enough to communicate
> the user's cwd to root, as a workaround, so that it didn't have to
> be retyped.
You know what does that for you? sudo -s. Or su if you've configured
it with a one-lin
On Thu 27 Mar 2025 at 12:23:26 (+0200), Anssi Saari wrote:
> David Wright writes:
>
> > host!auser 09:57:47 /somewhere/that/is/obnoxiously/long/program-1.2.3$
> > /bin/su --login
> > Password:
> > bullseye on /dev/sda5 toto05
> > host 09:57:59 ~# cd /somewhere/that/is/obnoxiously/long/p
Anssi Saari wrote:
> David Wright writes:
>
> > host!auser 09:57:47 /somewhere/that/is/obnoxiously/long/program-1.2.3$
> > /bin/su --login
> > Password:
> > bullseye on /dev/sda5 toto05
> > host 09:57:59 ~# cd /somewhere/that/is/obnoxiously/long/program-1.2.3
> > host 09:58:08 /somew
On 3/26/25 6:55 AM, Greg Wooledge wrote:
[SNIP]
I normally use "sudo -s", which is the closest sudo approximation to
the traditional behvior of "su" (before it was broken in buster).
I don't understand the reference to some "brokenness" of "su".
I've not closely followed this thread so I may
On Wed 26 Mar 2025 at 16:37:41 (-), Greg wrote:
> On 2025-03-26, Richard Owlett wrote:
> >
> > I assumed it was effectively the same as power down and then logging in
> > as root on power-up.
>
> It is. But it's unnecessary and dangerous to run your entire DE as root.
> Or maybe you log in t
Greg Wooledge (HE12025-03-26):
> This caused ALL KINDS of problems. People would do things like:
>
> $ su
> # apt update
> # apt install somepkg
>
> And the postinstall script for somepkg would fail because it couldn't
> find commands that are in /sbin or /usr/sbin, because those dir
So, in most cases* sudo -s* is better? Any downsides?
ŃŃ, 26 ĐŒĐ°Ń. 2025âŻĐł. ĐČ 16:10, Greg Wooledge :
> On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> > On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > > I normally use "sudo -s", which is the closest sudo approximation to
> > > the trad
On Wed, Mar 26, 2025 at 07:55:33AM -0400, Greg Wooledge wrote:
[...]
> I normally use "sudo -s", which is the closest sudo approximation to
> the traditional behvior of "su" (before it was broken in buster).
>
> "sudo -i" is meant to approximate the behavior of "su -". Before buster,
> nobody w
On 2025-03-26, Richard Owlett wrote:
>
> I assumed it was effectively the same as power down and then logging in
> as root on power-up.
It is. But it's unnecessary and dangerous to run your entire DE as root.
Or maybe you log in to the console and use startx to run Mate?
At any rate, I do follo
On 2025-03-26, Greg Wooledge wrote:
>>
>> Does this "brokenness" of "su" have any potential effect on my usage?
>
> Maybe. If you haven't created an /etc/default/su file, then something
> like this:
If he hasn't noticed yet, I doubt it.
I noticed when I finally erased Stretch and installed Boo
On 2025-03-26, Richard Owlett wrote:
>> If he hasn't noticed yet, I doubt it.
>
> I agree.
> If I understand what people want to accomplish by using command-line
> options, I would likely have gone to System->Log Out ... and then logged
> in as root.
Not recommended.
On Wed 26 Mar 2025 at 10:03:59 (-0500), Richard Owlett wrote:
> On 3/26/25 9:55 AM, Greg wrote:
> > On 2025-03-26, Richard Owlett wrote:
> >
> > > > If he hasn't noticed yet, I doubt it.
> > >
> > > I agree.
> > > If I understand what people want to accomplish by using command-line
> > > options
On Wed 26 Mar 2025 at 16:24:21 (+0300), J wrote:
> ŃŃ, 26 ĐŒĐ°Ń. 2025âŻĐł. ĐČ 16:10, Greg Wooledge :
> > On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> > > On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > > > I normally use "sudo -s", which is the closest sudo approximation to
> > > > the t
On 3/26/25 9:55 AM, Greg wrote:
On 2025-03-26, Richard Owlett wrote:
If he hasn't noticed yet, I doubt it.
I agree.
If I understand what people want to accomplish by using command-line
options, I would likely have gone to System->Log Out ... and then logged
in as root.
Not recommended.
On 3/26/25 9:04 AM, Greg wrote:
On 2025-03-26, Greg Wooledge wrote:
Does this "brokenness" of "su" have any potential effect on my usage?
Maybe. If you haven't created an /etc/default/su file, then something
like this:
If he hasn't noticed yet, I doubt it.
I agree.
If I understand what
On Wed, Mar 26, 2025 at 04:19:37PM +0300, J wrote:
> >
> > > work with* root?* I will try to test.
> >
> > I fully expect it to, yes.
> >
>
> Oh, yes, it works. I just had to use *sudo su* and not not
I think you never need "sudo su". "sudo -i" and "sudo -s" will do your
bidding, depending on you
>
> > work with* root?* I will try to test.
>
> I fully expect it to, yes.
>
Oh, yes, it works. I just had to use *sudo su* and not not
*su - *
Also it's bad that Wiki doesn't clarify* how to* 'boot the rescue system
including the kernel option "efi=runtime" and mount the EFI variables
before pro
On Wed, Mar 26, 2025 at 07:48:16 -0500, Richard Owlett wrote:
> On 3/26/25 6:55 AM, Greg Wooledge wrote:
> > I normally use "sudo -s", which is the closest sudo approximation to
> > the traditional behvior of "su" (before it was broken in buster).
>
> I don't understand the reference to some "brok
On Wed, Mar 26, 2025 at 12:23:38 +0100, to...@tuxteam.de wrote:
> On Wed, Mar 26, 2025 at 02:15:03PM +0300, J wrote:
> > And i thought *sudo -i*, you speaking about, is something like
> > *--interactive*, which is not, how i see now...
>
> The long form is "--login", not interactive. But the "-i"
On Wed, Mar 26, 2025 at 02:15:03PM +0300, J wrote:
> > In my opinion, "sudo -i" might be added to the wiki articles. I would
> > prefer to see a warning concerning compound shell commands in *sudo* docs.
> >
> > J, my impressions is that you read some docs strongly suggesting to
> > prefix every co
> In my opinion, "sudo -i" might be added to the wiki articles. I would
> prefer to see a warning concerning compound shell commands in *sudo* docs.
>
> J, my impressions is that you read some docs strongly suggesting to
> prefix every command instead of just becoming root.
Actually it is easier
There were also some minor problems which I solved with *apt update/upgrade*
> while being in *chroot*.
>
In particular, there was for some reason no internet connection after I
booted to the restored system. Something wrong was with firmware and/or
initramfs i guess.
On 25/03/2025 19:47, J wrote:
Notice that the page suggests "# for i in /dev /dev/pts /proc "
so it is assumed that users should run
$ sudo -i
sudo *SH -c '...' -* as mentioned above. But it is not written in WIki.
In my opinion, "sudo -i" might be added to the wiki articles. I wo
On Wed, Mar 26, 2025 at 09:25:01AM +0700, Max Nikulin wrote:
> On 25/03/2025 19:47, J wrote:
> > Notice that the page suggests "# for i in /dev /dev/pts /proc "
> > so it is assumed that users should run
> >
> > $ sudo -i
> >
> > sudo *SH -c '...' -* as mentioned above. But it is not
>
> Notice that the page suggests "# for i in /dev /dev/pts /proc "
> so it is assumed that users should run
>
> $ sudo -i
>
sudo *SH -c '...' - *as mentioned above. But it is not written in WIki.
I am thinking about if i should propose the Wiki update.
> The error suggests that you forgot to m
On 25/03/2025 02:40, J wrote:
user@debian:~$ sudo for i in /dev /dev/pts /proc /sys /sys/firmware/efi/
efivars /run; do mount -B $i /mnt/$i; done
Notice that the page suggests "# for i in /dev /dev/pts /proc "
so it is assumed that users should run
$ sudo -i
# # more commands given above...
#
> sudo sh -c '...'
>
Didn't know such a thing. Wasn't mention in the wiki.
Have you considered doing something crazy like creating the mount points?
>
Can't say so. I have fixed my problem a few days ago (see above about
mounting), now i am discussing with Max if Wiki is correct.
https://wiki.d
I have rechecked.
It doesn't work with sudo also.
Not in a one line, not when i tried to make line breaks with \, not in a
bash script.
user@debian:~$ sudo for i in /dev /dev/pts /proc /sys
/sys/firmware/efi/efivars /run; do mount -B $i /mnt/$i; done
bash: syntax error near unexpected token `do'
problem with ârecommended optionsâ of Boot-repair
Live-CD, but it didnât help. I can boot into GRUB but it doesnât see
anything and shows me just a command line (I mean GRUB line, not Debian OS).
I have also tried to install Refind with Gnome Live-CD, it can see grub
file, but again, it boots me
Thanks for the feedback.
That project is currently inactive as it it is tax prep time.
I'll try your suggestions when I get a break.
On 3/12/25 8:53 AM, Greg wrote:
On 2024-12-10, Richard Owlett wrote:
I'm looking for documentation for optimal use of the GUI.
My initial problems revolved aro
On 2024-12-10, Richard Owlett wrote:
>
> I'm looking for documentation for optimal use of the GUI.
> My initial problems revolved around pause/resume.
> Those raised the question "How do I go to point x minutes into a file?"
mpv --start=00:12:34 video.mp4
> Then I started speculating about takin
âŠ
Anyway thanks for your help, I might follow on your suggestion and update
to trixie as it should become quite usable now it is almost time for a
release :)
Thanks
Brieuc
On Wed, 5 Mar 2025 at 00:30 Felix Miata wrote:
> Brieuc Desoutter composed on 2025-03-04 10:02 (UTC+0300):
>
> > I ha
Brieuc Desoutter composed on 2025-03-04 10:02 (UTC+0300):
> I have installed Debian 12.9 from the live image on my System76 Oryx Pro
> (Intel Xe Graphic + nvidia 4060) yesterday.
> I have NOT installed the nvidia-driver yet (previous attempt failed and I
> re-installed fresh), only i915 and nouvea
Brieuc Desoutter composed on 2025-03-04 10:02 (UTC+0300):
...
/etc/X11/xorg.conf is an optional file that most users have had no need for for
most of the past two decades. The main exception in actual practice is that
installation of proprietary NVidia drivers historically has created one.
xorg.co
lt-display-manager
fonts
rgb.txt
xinit
xkb
xorg.conf.d
Xreset
Xreset.d
Xresources
Xsession
Xsession.d
Xsession.options
xsm
XvMCConfig
Xwrapper.config
How can I generate a proper xorg.conf for my setup and/or use my second
monitor on Wayland ?
Thanks for your help
Brieuc
ge.
Anyone who can help?
If the download checks are failing perhaps due to a slow/bad connection
try a torrent.
https://www.debian.org/CD/torrent-cd/
mick
ra...@siliconet.pl wrote:
>
>On 29.01.2025 4:16 PM, Roberto C. SĂÂĄnchez wrote:
>> Yes, it still means that. The minizip binary package you are seeing
>> comes from a different source package, also called minizip:
>>
>> https://packages.debian.org/source/bookworm/minizip
>
>Aha! Got it :-)
>
>And th
On 29.01.2025 4:16 PM, Roberto C. SĂĄnchez wrote:
Yes, it still means that. The minizip binary package you are seeing
comes from a different source package, also called minizip:
https://packages.debian.org/source/bookworm/minizip
Aha! Got it :-)
And there are no binary components in Debian b
vious post above as Re- to Hanno.
>
You are mistaken here. I think my other email elsewhere in this thread
explaining the source and status of the minizip package you are seeing
answers this precisely.
>Anyway thank you for trying to explain me things that are not obvious to
> me.
&
On Wed, Jan 29, 2025 at 04:04:26PM +0100, RafaĆ LichwaĆa wrote:
>
> On 29.01.2025 3:35 PM, Hanno 'Rince' Wagner wrote:
> > > The notes say:
> > > [bookworm] - zlib (contrib/minizip not built and src:zlib not
> > > producing binary packages)
> > > In other words, there's no point in fixing it bec
On 29.01.2025 3:30 PM, Roberto C. SĂĄnchez wrote:
On Wed, Jan 29, 2025 at 03:22:02PM +0100, RafaĆ LichwaĆa wrote:
On 29.01.2025 2:43 PM, Dan Ritter wrote:
CVSS are often bogus.
Hmmm... I'm not sure what you mean. All security announcements in DSAs are
referring to CVSS, so... what's
On 29.01.2025 3:35 PM, Hanno 'Rince' Wagner wrote:
The notes say:
[bookworm] - zlib (contrib/minizip not built and src:zlib not
producing binary packages)
In other words, there's no point in fixing it because Debian doesn't build the
vulnerable binary component.
Very low priority.
so, this
On Wed, Jan 29, 2025 at 03:22:02PM +0100, RafaĆ LichwaĆa wrote:
>On 29.01.2025 2:43 PM, Dan Ritter wrote:
>
> CVSS are often bogus.
>
> Hmmm... I'm not sure what you mean. All security announcements in DSAs are
> referring to CVSS, so... what's the source of such opinion?
>
>
> Most rec
On Wed, Jan 29, 2025 at 08:43:12AM -0500, Dan Ritter wrote:
>
> Most recently: https://daniel.haxx.se/blog/2025/01/23/cvss-is-dead-to-us/
I was going to post a link to this very article when I saw that you
already had :-)
Regards,
-Roberto
--
Roberto C. SĂĄnchez
On 29.01.2025 2:43 PM, Dan Ritter wrote:
CVSS are often bogus.
Hmmm... I'm not sure what you mean. All security announcements in DSAs are
referring to CVSS, so... what's the source of such opinion?
Most recently:https://daniel.haxx.se/blog/2025/01/23/cvss-is-dead-to-us/
Yeah, another blog and
found a confirmation that
bookworm is vulnerable.
So now I suppose I just don't fully understand those information I
found, so that's why I ask you guys for help on this Debian user mailing
list.
This strange scanner found a CVE attached to minizip. minizip is part
of zlib, but
RafaĆ LichwaĆa wrote:
>
> On 29.01.2025 2:12 PM, Dan Ritter wrote:
> > The notes say:
> >
> > [bookworm] - zlib (contrib/minizip not built and src:zlib not
> > producing binary packages)
> >
> > In other words, there's no point in fixing it because Debian
> > doesn't build the vulnerable bina
t least for me)Â it's not the case this time (?)
I hope I am wrong, so please help to to understand.
Could you please send some link which says "yeah, it's fixed in bookworm"?
I cannot find it.
On the other hand there is nothing in package change log about this CVSS:
https://meta
On 29.01.2025 2:12 PM, Dan Ritter wrote:
The notes say:
[bookworm] - zlib (contrib/minizip not built and src:zlib not
producing binary packages)
In other words, there's no point in fixing it because Debian
doesn't build the vulnerable binary component.
Very low priority.
Could you please
RafaĆ LichwaĆa wrote:
> Hi,
>
> I've prepared some docker image based on Debian 12 (bookworm, fully updated)
> and after upload it to local registry it has been automatically scanned for
> possible vulnerabilities.
> Then I was really surprised when discovered that according to this scan
> there
On Wed, 29 Jan 2025 at 12:40, RafaĆ LichwaĆa wrote:
> I've prepared some docker image based on Debian 12 (bookworm, fully
> updated) and after upload it to local registry it has been automatically
> scanned for possible vulnerabilities.
> Then I was really surprised when discovered that according
om these information above?
Similar problem in second critical on the list: package "libaom3" which
is a binary package from "aom":
https://tracker.debian.org/pkg/aom
https://security-tracker.debian.org/tracker/source-package/aom
https://www.cvedetails.com/cve/CVE-2023-6879/
Please help me to understand :-)
Best regards,
Rafal
On Fri, Jan 24, 2025 at 9:32âŻPM Bob McGowan wrote:
> On Fri, 2025-01-24 at 18:23 +, Tim Woodall wrote:
>
> On Fri, 17 Jan 2025, Bob McGowan wrote:
>
> Hello list,
>
> I've been trying to figure out how to use my BD disc writer to create
> backups of files.
>
> What I first found were instruct
On Fri, 2025-01-24 at 18:23 +, Tim Woodall wrote:
> On Fri, 17 Jan 2025, Bob McGowan wrote:
>
> > Hello list,
> >
> > I've been trying to figure out how to use my BD disc writer to
> > create
> > backups of files.
> >
> > What I first found were instructions to create an empty file of the
>
On Fri, 17 Jan 2025, Bob McGowan wrote:
Hello list,
I've been trying to figure out how to use my BD disc writer to create
backups of files.
What I first found were instructions to create an empty file of the
propper size, 'mkudffs file', loop mount it, copy files to it, unmount
and burn to the
ed or the whole site if possible, this website was
> > only created to attack and make fun of several people in the world
> >
> > can you guys please do something against it? thanks already.
>
> This is a mailing list for users of Debian Linux. I'm not sure that we
On Thu, Jan 23, 2025 at 01:45:50PM +, Andrew M.A. Cater wrote:
[...]
> This is a mailing list for users of Debian Linux. I'm not sure that we
> can help with random abuse on the Internet unless it's hosted on
> Debian-provided infrastructure.
You are as friendly as ever :
e in the world
>
> can you guys please do something against it? thanks already.
This is a mailing list for users of Debian Linux. I'm not sure that we
can help with random abuse on the Internet unless it's hosted on
Debian-provided infrastructure.
Can I suggest that you raise
1 - 100 of 19838 matches
Mail list logo
