Bug#1065696: Fwd: E: unsupported command: poweroff.no-molly-guard
On 2024-03-08 at 22:26:25, Helmut Grohne (hel...@subdivi.de) wrote: > Yes, I think this is a duplicate of #1059691. Could you give feedback on > the contained patch? Indeed, it does look like the same thing. I'm sorry I missed the original bug and never saw your patch. It looks good to me. I agree it feels like adding another layer of duct tape, but hopefully we can clean that up later once we no longer have to support usr-not-merged. I'm going to go ahead and upload to unstable. Many thanks for the patch. Francois -- https://fmarier.org/
Bug#1065696: Fwd: E: unsupported command: poweroff.no-molly-guard
Hi Helmut, This looks like an unexpected edge case from the recent usr-merge changes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065696 It sounds like a system using sysvinit, instead of systemd, which was recently upgraded using usrmerge. Francois -- https://fmarier.org/
Bug#1065696: Fwd: E: unsupported command: poweroff.no-molly-guard
Hi Helmut, This looks like an unexpected edge case from the recent usr-merge changes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065696 It sounds like a system using sysvinit, instead of systemd, which was recently upgraded using usrmerge. Francois -- https://fmarier.org/
Bug#1033306: The tor package in stable will soon become unusable
I received the email below from the Tor team. The package that's currently in stable should be updated ASAP since it's going to stop working very soon. I will be switching temporarily to the package in backports, but IMO an update should be pushed to bookworm either via the security repo, or failing that as a stable update. Francois -- Hi, You are running a bunch of Tor relays, which is great. However, that relays' Tor version is obsolete, and because of old bugs, we will soon cut relays and bridges running that version out of the network. Please consider upgrading ASAP! You can find Tor packages and instructions for your distro / OS here: https://community.torproject.org/relay/setup/guard/ If you need help upgrading your relay, please use the Tor Forum: https://forum.torproject.org/c/support/relay-operator/17 ::Stay Connected with the Tor Community:: - Join our Monthly Tor relay operators meetups: https://forum.torproject.org/t/tor-relays-next-tor-relay-operator-meetup-march-2nd-2024-19-00-utc/11568 - Subscribe to the Tor relays mailing list: https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays Thanks, Gus -- The Tor Project Community Team Lead
Bug#1033306: The tor package in stable will soon become unusable
I received the email below from the Tor team. The package that's currently in stable should be updated ASAP since it's going to stop working very soon. I will be switching temporarily to the package in backports, but IMO an update should be pushed to bookworm either via the security repo, or failing that as a stable update. Francois -- Hi, You are running a bunch of Tor relays, which is great. However, that relays' Tor version is obsolete, and because of old bugs, we will soon cut relays and bridges running that version out of the network. Please consider upgrading ASAP! You can find Tor packages and instructions for your distro / OS here: https://community.torproject.org/relay/setup/guard/ If you need help upgrading your relay, please use the Tor Forum: https://forum.torproject.org/c/support/relay-operator/17 ::Stay Connected with the Tor Community:: - Join our Monthly Tor relay operators meetups: https://forum.torproject.org/t/tor-relays-next-tor-relay-operator-meetup-march-2nd-2024-19-00-utc/11568 - Subscribe to the Tor relays mailing list: https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays Thanks, Gus -- The Tor Project Community Team Lead
Bug#966218: Warning about the work-around listed here
A warning to anybody considering to use the suggested work-around. Based on the information suggested in this bug, I put the following in `/etc/modprobe.d/local.conf` on my laptop: options iwlwifi enable_ini=0 in order to suppress the "failed to load iwl-debug-yoyo.bin (-2)" log message. Versions 66 and above of the iwlwifi-ty-a0-gf-a0 firmware would refuse to load with these error messages: [ 18.222536] iwlwifi :aa:00.0: api flags index 2 larger than supported by driver [ 18.222549] iwlwifi :aa:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [ 18.222921] iwlwifi :aa:00.0: loaded firmware version 72.a764baac.0 ty-a0-gf-a0-72.ucode op_mode iwlmvm [ 18.375105] iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 ... [ 19.395451] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 19.395569] iwlwifi :aa:00.0: Loaded firmware version: 72.a764baac.0 ty-a0-gf-a0-72.ucode [ 19.395570] iwlwifi :aa:00.0: 0x | ADVANCED_SYSASSERT [ 19.395572] iwlwifi :aa:00.0: 0x | trm_hw_status0 [ 19.395573] iwlwifi :aa:00.0: 0x | trm_hw_status1 [ 19.395573] iwlwifi :aa:00.0: 0x | branchlink2 [ 19.395574] iwlwifi :aa:00.0: 0x | interruptlink1 [ 19.395575] iwlwifi :aa:00.0: 0x | interruptlink2 ... [ 19.395846] iwlwifi :aa:00.0: Failed to start RT ucode: -110 [ 19.395848] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 20.873263] iwlwifi :aa:00.0: Failed to run INIT ucode: -110 [ 20.886268] iwlwifi :aa:00.0: retry init count 0 [ 20.907324] iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 ... [ 21.951601] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 21.951753] iwlwifi :aa:00.0: Loaded firmware version: 72.a764baac.0 ty-a0-gf-a0-72.ucode [ 21.951754] iwlwifi :aa:00.0: 0x | ADVANCED_SYSASSERT [ 21.951756] iwlwifi :aa:00.0: 0x | trm_hw_status0 [ 21.951757] iwlwifi :aa:00.0: 0x | trm_hw_status1 [ 21.951758] iwlwifi :aa:00.0: 0x | branchlink2 [ 21.951759] iwlwifi :aa:00.0: 0x | interruptlink1 [ 21.951760] iwlwifi :aa:00.0: 0x | interruptlink2 ... [ 21.952064] iwlwifi :aa:00.0: Failed to start RT ucode: -110 [ 21.952066] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 23.529800] iwlwifi :aa:00.0: Failed to run INIT ucode: -110 [ 23.542843] iwlwifi :aa:00.0: retry init count 1 [ 23.555687] iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 ... [ 24.575479] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 24.575586] iwlwifi :aa:00.0: Loaded firmware version: 72.a764baac.0 ty-a0-gf-a0-72.ucode [ 24.575588] iwlwifi :aa:00.0: 0x | ADVANCED_SYSASSERT [ 24.575589] iwlwifi :aa:00.0: 0x | trm_hw_status0 [ 24.575590] iwlwifi :aa:00.0: 0x | trm_hw_status1 [ 24.575590] iwlwifi :aa:00.0: 0x | branchlink2 [ 24.575591] iwlwifi :aa:00.0: 0x | interruptlink1 [ 24.575592] iwlwifi :aa:00.0: 0x | interruptlink2 ... [ 24.575879] iwlwifi :aa:00.0: Failed to start RT ucode: -110 [ 24.575880] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 26.049956] iwlwifi :aa:00.0: Failed to run INIT ucode: -110 [ 26.063392] iwlwifi :aa:00.0: retry init count 2 Versions 63 and below of the firmware would load just fine with "enable_ini=0" which suggests to me that this version of the firmware would simply ignore it. Much worse, versions 74 or newer of the firmware would lock up and require a full power off (unplugged from power) to successfully load a firmware again (even 63 or below). Hopefully this comment will save someone some troubleshooting time. My solution is simple: ignore the "failed to load iwl-debug-yoyo.bin (-2)" for now. Francois -- https://fmarier.org/
Bug#966218: Warning about the work-around listed here
A warning to anybody considering to use the suggested work-around. Based on the information suggested in this bug, I put the following in `/etc/modprobe.d/local.conf` on my laptop: options iwlwifi enable_ini=0 in order to suppress the "failed to load iwl-debug-yoyo.bin (-2)" log message. Versions 66 and above of the iwlwifi-ty-a0-gf-a0 firmware would refuse to load with these error messages: [ 18.222536] iwlwifi :aa:00.0: api flags index 2 larger than supported by driver [ 18.222549] iwlwifi :aa:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36 [ 18.222921] iwlwifi :aa:00.0: loaded firmware version 72.a764baac.0 ty-a0-gf-a0-72.ucode op_mode iwlmvm [ 18.375105] iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 ... [ 19.395451] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 19.395569] iwlwifi :aa:00.0: Loaded firmware version: 72.a764baac.0 ty-a0-gf-a0-72.ucode [ 19.395570] iwlwifi :aa:00.0: 0x | ADVANCED_SYSASSERT [ 19.395572] iwlwifi :aa:00.0: 0x | trm_hw_status0 [ 19.395573] iwlwifi :aa:00.0: 0x | trm_hw_status1 [ 19.395573] iwlwifi :aa:00.0: 0x | branchlink2 [ 19.395574] iwlwifi :aa:00.0: 0x | interruptlink1 [ 19.395575] iwlwifi :aa:00.0: 0x | interruptlink2 ... [ 19.395846] iwlwifi :aa:00.0: Failed to start RT ucode: -110 [ 19.395848] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 20.873263] iwlwifi :aa:00.0: Failed to run INIT ucode: -110 [ 20.886268] iwlwifi :aa:00.0: retry init count 0 [ 20.907324] iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 ... [ 21.951601] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 21.951753] iwlwifi :aa:00.0: Loaded firmware version: 72.a764baac.0 ty-a0-gf-a0-72.ucode [ 21.951754] iwlwifi :aa:00.0: 0x | ADVANCED_SYSASSERT [ 21.951756] iwlwifi :aa:00.0: 0x | trm_hw_status0 [ 21.951757] iwlwifi :aa:00.0: 0x | trm_hw_status1 [ 21.951758] iwlwifi :aa:00.0: 0x | branchlink2 [ 21.951759] iwlwifi :aa:00.0: 0x | interruptlink1 [ 21.951760] iwlwifi :aa:00.0: 0x | interruptlink2 ... [ 21.952064] iwlwifi :aa:00.0: Failed to start RT ucode: -110 [ 21.952066] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 23.529800] iwlwifi :aa:00.0: Failed to run INIT ucode: -110 [ 23.542843] iwlwifi :aa:00.0: retry init count 1 [ 23.555687] iwlwifi :aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 ... [ 24.575479] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 24.575586] iwlwifi :aa:00.0: Loaded firmware version: 72.a764baac.0 ty-a0-gf-a0-72.ucode [ 24.575588] iwlwifi :aa:00.0: 0x | ADVANCED_SYSASSERT [ 24.575589] iwlwifi :aa:00.0: 0x | trm_hw_status0 [ 24.575590] iwlwifi :aa:00.0: 0x | trm_hw_status1 [ 24.575590] iwlwifi :aa:00.0: 0x | branchlink2 [ 24.575591] iwlwifi :aa:00.0: 0x | interruptlink1 [ 24.575592] iwlwifi :aa:00.0: 0x | interruptlink2 ... [ 24.575879] iwlwifi :aa:00.0: Failed to start RT ucode: -110 [ 24.575880] iwlwifi :aa:00.0: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 26.049956] iwlwifi :aa:00.0: Failed to run INIT ucode: -110 [ 26.063392] iwlwifi :aa:00.0: retry init count 2 Versions 63 and below of the firmware would load just fine with "enable_ini=0" which suggests to me that this version of the firmware would simply ignore it. Much worse, versions 74 or newer of the firmware would lock up and require a full power off (unplugged from power) to successfully load a firmware again (even 63 or below). Hopefully this comment will save someone some troubleshooting time. My solution is simple: ignore the "failed to load iwl-debug-yoyo.bin (-2)" for now. Francois -- https://fmarier.org/
Bug#1062046: [hel...@subdivi.de: Bug#1062046: libfko3t64 has an undeclared file conflict]
Looks like there's a missing conflict in the package that was just uploaded to experimentatl. - Message transféré de Helmut Grohne - Package: libfko3t64 Version: 2.6.10-20.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libfko3 X-Debbugs-Cc: Lukas Märdian , vor...@debian.org libfko3t64 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/libfko.so.3 * /usr/lib/x86_64-linux-gnu/libfko.so.3.0.0 are contained in the packages * libfko3 * 2.6.10-12 as present in bullseye * 2.6.10-16 as present in bookworm * 2.6.10-20+b2 as present in trixie|unstable * libfko3t64/2.6.10-20.1~exp1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. - Fin du message transféré -
Bug#1062046: [hel...@subdivi.de: Bug#1062046: libfko3t64 has an undeclared file conflict]
Looks like there's a missing conflict in the package that was just uploaded to experimentatl. - Message transféré de Helmut Grohne - Package: libfko3t64 Version: 2.6.10-20.1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + libfko3 X-Debbugs-Cc: Lukas Märdian , vor...@debian.org libfko3t64 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/x86_64-linux-gnu/libfko.so.3 * /usr/lib/x86_64-linux-gnu/libfko.so.3.0.0 are contained in the packages * libfko3 * 2.6.10-12 as present in bullseye * 2.6.10-16 as present in bookworm * 2.6.10-20+b2 as present in trixie|unstable * libfko3t64/2.6.10-20.1~exp1 as present in experimental These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance. - Fin du message transféré -
Bug#1061958: fwknop: NMU diff for 64-bit time_t transition
On 2024-01-30 at 05:48:11, Lukas Märdian (sl...@debian.org) wrote: > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a > period of several days before we begin uploads to unstable; so if information > becomes available that your package should not be included in the transition, > there is time for us to amend the planned uploads. No objections from me. If you'd like to create a merge request on https://salsa.debian.org/debian/fwknop, then I can merge and then you can upload to unstable at your convenience. Francois signature.asc Description: PGP signature
Bug#1061958: fwknop: NMU diff for 64-bit time_t transition
On 2024-01-30 at 05:48:11, Lukas Märdian (sl...@debian.org) wrote: > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a > period of several days before we begin uploads to unstable; so if information > becomes available that your package should not be included in the transition, > there is time for us to amend the planned uploads. No objections from me. If you'd like to create a merge request on https://salsa.debian.org/debian/fwknop, then I can merge and then you can upload to unstable at your convenience. Francois signature.asc Description: PGP signature
Bug#1061592: cryptsetup: Password prompt during boot echoes characters to the screen in plaintext
Package: cryptsetup
Version: 2:2.6.1-6+b1
Severity: normal
On my machine, if I ESC out of the plymouth password prompt (which does hide
the characters I type), I get the a text-mode prompt ("Please unlock disk
nvme0n1p4_crypt") which echoes to the screen the characters I type. Then it
repeats the prompt with asterisks. So it looks like this:
Please unlock disk nvme0n1p4_crypt: SooperSekretPassword1!@
Please unlock disk nvme0n1p4_crypt: ***
which isn't great because anybody looking over my shoulder can see it, or
anybody who Ctrl+F1 into the console later on and then scrolls back up.
Francois
-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.6.13-amd64 root=UUID=4d44aae6-2235-47f2-9de5-595ed5cd4a4c
ro rootflags=subvol=@rootfs mem_sleep_default=deep
module_blacklist=hid_sensor_hub memtest=1 quiet splash
-- /etc/crypttab
nvme0n1p3_crypt /dev/nvme0n1p3 /dev/urandom
cipher=aes-xts-plain64,size=256,swap,discard
nvme0n1p4_crypt UUID=29be86f7-f2fe-412f-afd8-5740f70f5a2e none luks,discard
-- /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
#
/dev/mapper/nvme0n1p4_crypt / btrfs
noatime,nodiratime,subvol=@rootfs 0 0
# /boot was on /dev/nvme0n1p2 during installation
UUID=7543aee2-af70-44da-bae2-4f059801f08d /boot ext4
ro,noatime,nodiratime,nodev,nosuid,noexec 0 2
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=0B84-3C60 /boot/efi vfatro,nodev,nosuid,noexec,umask=0077
0 1
/dev/mapper/nvme0n1p3_crypt noneswapsw 0 0
# Harden pid directories from normal users
proc/proc prochidepid=2
0 0
# Safe tmp directory
tmpfs /tmptmpfs size=8G,noexec,nosuid,nodev
0 0
# Removable storage
/dev/sr0/media/cdromudf,iso9660 user,noauto,nodev,nosuid
0 0
/dev/sdb1 /media/usbdisk autouser,noauto,nodev,nosuid,noexec
0 0
-- lsmod
Module Size Used by
snd_seq_dummy 12288 0
snd_hrtimer12288 1
snd_seq 114688 7 snd_seq_dummy
snd_seq_device 16384 1 snd_seq
nfnetlink_queue32768 1
xt_comment 12288 0
xt_NFQUEUE 12288 1
xt_MASQUERADE 16384 2
xt_mark12288 0
nft_chain_nat 12288 2
nf_nat 65536 2 nft_chain_nat,xt_MASQUERADE
tun69632 2
ip6t_frag 16384 1
ip6t_REJECT12288 2
nf_reject_ipv6 20480 1 ip6t_REJECT
xt_LOG 16384 2
nf_log_syslog 24576 2
ipt_REJECT 12288 1
nf_reject_ipv4 16384 1 ipt_REJECT
xt_tcpudp 16384 0
xt_conntrack 12288 4
nf_conntrack 212992 3 xt_conntrack,nf_nat,xt_MASQUERADE
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 12288 1 nf_conntrack
nft_compat 20480 13
nf_tables 372736 479 nft_compat,nft_chain_nat
qrtr 57344 4
chaoskey 20480 0
sg 45056 0
uvcvideo 147456 0
videobuf2_vmalloc 20480 1 uvcvideo
uvc12288 1 uvcvideo
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 36864 1 uvcvideo
videodev 368640 2 videobuf2_v4l2,uvcvideo
videobuf2_common 77824 4
videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
mc 94208 4
videodev,videobuf2_v4l2,uvcvideo,videobuf2_common
binfmt_misc28672 1
nls_ascii 12288 1
nls_cp437 16384 1
vfat 20480 1
fat 102400 1 vfat
snd_sof_pci_intel_tgl12288 0
iwlmvm589824 0
snd_sof_intel_hda_common 217088 1 snd_sof_pci_intel_tgl
soundwire_intel73728 1 snd_sof_intel_hda_common
soundwire_generic_allocation12288 1 soundwire_intel
snd_sof_intel_hda_mlink40960 2 soundwire_intel,snd_sof_intel_hda_common
soundwire_cadence 45056 1 soundwire_intel
mac80211 1392640 1 iwlmvm
snd_sof_intel_hda 24576 1 snd_sof_intel_hda_common
snd_sof_pci24576 2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl
snd_sof_xtensa_dsp 16384 1 snd_sof_intel_hda_common
snd_sof 360448 3
snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_hda
ext4 1134592 1
snd_sof_utils 16384 1 snd_sof
snd_soc_hdac_hda 28672 1 snd_sof_intel_hda_common
Bug#1059781: xwayland: Xwayland.desktop is broken: it contains Type=Application, but no Exec key/value pair.
Package: xwayland Version: 2:23.2.3-1 Severity: normal Whenever I start dmenu, I get the following message in my logs: File /usr/share/applications/org.freedesktop.Xwayland.desktop is broken: it contains Type=Application, but no Exec key/value pair. at /usr/bin/i3-dmenu-desktop line 256. Francois -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.8-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xwayland depends on: ii libc6 2.37-13 ii libdecor-0-00.2.1-1 ii libdrm2 2.4.117-1 ii libepoxy0 1.5.10-1 ii libgbm1 23.3.1-4 ii libgcrypt20 1.10.3-2 ii libgl1 1.7.0-1 ii libpixman-1-0 0.42.2-1 ii libtirpc3 1.3.4+ds-1 ii libwayland-client0 1.22.0-2.1 ii libxau6 1:1.0.9-1 ii libxcvt00.1.2-1 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.6-1 ii libxshmfence1 1.3-1 ii xserver-common 2:21.1.10-1 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information
Bug#1059781: xwayland: Xwayland.desktop is broken: it contains Type=Application, but no Exec key/value pair.
Package: xwayland Version: 2:23.2.3-1 Severity: normal Whenever I start dmenu, I get the following message in my logs: File /usr/share/applications/org.freedesktop.Xwayland.desktop is broken: it contains Type=Application, but no Exec key/value pair. at /usr/bin/i3-dmenu-desktop line 256. Francois -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.8-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xwayland depends on: ii libc6 2.37-13 ii libdecor-0-00.2.1-1 ii libdrm2 2.4.117-1 ii libepoxy0 1.5.10-1 ii libgbm1 23.3.1-4 ii libgcrypt20 1.10.3-2 ii libgl1 1.7.0-1 ii libpixman-1-0 0.42.2-1 ii libtirpc3 1.3.4+ds-1 ii libwayland-client0 1.22.0-2.1 ii libxau6 1:1.0.9-1 ii libxcvt00.1.2-1 ii libxdmcp6 1:1.1.2-3 ii libxfont2 1:2.0.6-1 ii libxshmfence1 1.3-1 ii xserver-common 2:21.1.10-1 xwayland recommends no packages. xwayland suggests no packages. -- no debconf information
Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones
Thank you Helmut and Chris for the helpful discussion. I have finally found some time to review your comments and the proposed molly-guard patches. While I'm still not 100% confident I understand the problem (and the fix), the solution you have settled on makes sense to me. With respect to the presence of the real commands in the path, I'm not too worried about it personally. I do agree it's unfortunate and it would be great if we could do this reliably without putting the diverted binary within easy reach, but at the end of the day, molly-guard will never catch all possible mistakes. As Helmut pointed out, it's already missing some cases (and it's always been possible to "init 6" as well), but I think it still provides a useful service if it catches the most common cases of accidental reboots. I had a similar dilemma for another package I maintain (safe-rm) and I've decided there to focus on the most common cases again to reduce complexity, and improve reliability. I will leave this for a few days in case others like Simó want to also chime in, but otherwise I am planning to upload to experimental this week and then unstable a few days later. Again many thanks for all of the work that has gone into solving this thorny problem. Francois
Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones
Thank you Helmut and Chris for the helpful discussion. I have finally found some time to review your comments and the proposed molly-guard patches. While I'm still not 100% confident I understand the problem (and the fix), the solution you have settled on makes sense to me. With respect to the presence of the real commands in the path, I'm not too worried about it personally. I do agree it's unfortunate and it would be great if we could do this reliably without putting the diverted binary within easy reach, but at the end of the day, molly-guard will never catch all possible mistakes. As Helmut pointed out, it's already missing some cases (and it's always been possible to "init 6" as well), but I think it still provides a useful service if it catches the most common cases of accidental reboots. I had a similar dilemma for another package I maintain (safe-rm) and I've decided there to focus on the most common cases again to reduce complexity, and improve reliability. I will leave this for a few days in case others like Simó want to also chime in, but otherwise I am planning to upload to experimental this week and then unstable a few days later. Again many thanks for all of the work that has gone into solving this thorny problem. Francois
Bug#1057470: Outdated rkhunter since 2018-02
On 2023-12-05 at 20:28:44, Jörg Frings-Fürst (debian@jff.email) wrote: > I did not search for Vulnerabilities. However, I am of the opinion that using > rkhunter in its current form is equivalent to using a 6 year old virus scanner > and therefore involves an increased security risk. Ideally I agree that it would be great if more signatures could be added so that new threats could be detected. I don't see any indication that of vulnerabilities in this software however. Lack of new upstream development is not necessarily an indication that the software is unsafe. Francois -- https://fmarier.org/
Bug#1057470: Outdated rkhunter since 2018-02
On 2023-12-05 at 20:28:44, Jörg Frings-Fürst (debian@jff.email) wrote: > I did not search for Vulnerabilities. However, I am of the opinion that using > rkhunter in its current form is equivalent to using a 6 year old virus scanner > and therefore involves an increased security risk. Ideally I agree that it would be great if more signatures could be added so that new threats could be detected. I don't see any indication that of vulnerabilities in this software however. Lack of new upstream development is not necessarily an indication that the software is unsafe. Francois -- https://fmarier.org/
Bug#1057470: Outdated rkhunter since 2018-02
On 2023-12-05 at 07:07:23, Jörg Frings-Fürst (debian@jff.email) wrote: > I noticed that the program and the data available on the internet are from > 2018-02. > So almost 6 years old data suggests a non-existent security. Hi Jörg, are you aware of security vulnerabilities in rkhunter or you are simply guessing that it might contain security vulnerabilities? As far as I am aware, rkhunter is not under active development anymore, but it also doesn't have any known vulnerabilities. Francois -- https://fmarier.org/
Bug#1057470: Outdated rkhunter since 2018-02
On 2023-12-05 at 07:07:23, Jörg Frings-Fürst (debian@jff.email) wrote: > I noticed that the program and the data available on the internet are from > 2018-02. > So almost 6 years old data suggests a non-existent security. Hi Jörg, are you aware of security vulnerabilities in rkhunter or you are simply guessing that it might contain security vulnerabilities? As far as I am aware, rkhunter is not under active development anymore, but it also doesn't have any known vulnerabilities. Francois -- https://fmarier.org/
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
On 2023-11-27 at 03:54:16, Helmut Grohne (hel...@subdivi.de) wrote: > I don't have time to update the patch right now. Let me promise an update > this week, ok? Hi Helmut, My apologies for not responding earlier, but this is a rather thorny problem to solve and I have not had the mental "bandwidth" to dig into this yet. I wanted however to express my sincere appreciation for all of the work you have put into both understanding this problem and coming up with a solution. Francois
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
On 2023-11-27 at 03:54:16, Helmut Grohne (hel...@subdivi.de) wrote: > I don't have time to update the patch right now. Let me promise an update > this week, ok? Hi Helmut, My apologies for not responding earlier, but this is a rather thorny problem to solve and I have not had the mental "bandwidth" to dig into this yet. I wanted however to express my sincere appreciation for all of the work you have put into both understanding this problem and coming up with a solution. Francois
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
CCing Helmut who wrote the initial patch for systemd 255+ support (see Bug#1055510). I also see the same thing: $ ls -lh /usr/lib/molly-guard/ Permissions Size User Group Date Modified Name .rwxr-xr-x 3,4k root root 11 nov 14:02 molly-guard* lrwxrwxrwx31 root root 14 nov 2019 pm-hibernate -> /usr/lib/pm-utils/bin/pm-action* lrwxrwxrwx31 root root 14 nov 2019 pm-suspend -> /usr/lib/pm-utils/bin/pm-action* lrwxrwxrwx31 root root 14 nov 2019 pm-suspend-hybrid -> /usr/lib/pm-utils/bin/pm-action* $ sudo reboot --help E: not a regular file: /usr/lib/molly-guard/reboot I'm also a little confused by the diverts. Perhaps something changed in systemd (which owns the ultimate underlying symlinks)? Francois -- https://fmarier.org/
Bug#1056279: Looks like the systemctl links are gone but not the pm-utils ones
CCing Helmut who wrote the initial patch for systemd 255+ support (see Bug#1055510). I also see the same thing: $ ls -lh /usr/lib/molly-guard/ Permissions Size User Group Date Modified Name .rwxr-xr-x 3,4k root root 11 nov 14:02 molly-guard* lrwxrwxrwx31 root root 14 nov 2019 pm-hibernate -> /usr/lib/pm-utils/bin/pm-action* lrwxrwxrwx31 root root 14 nov 2019 pm-suspend -> /usr/lib/pm-utils/bin/pm-action* lrwxrwxrwx31 root root 14 nov 2019 pm-suspend-hybrid -> /usr/lib/pm-utils/bin/pm-action* $ sudo reboot --help E: not a regular file: /usr/lib/molly-guard/reboot I'm also a little confused by the diverts. Perhaps something changed in systemd (which owns the ultimate underlying symlinks)? Francois -- https://fmarier.org/
Bug#1055510: Best way to coordinate this fix
On 2023-11-10 at 02:45:14, Helmut Grohne (hel...@subdivi.de) wrote: > Thank you. The package built and dumat has imported it. I locally forked > its analysis database pretending that systemd would not declare a > conflict for molly-guard and reran it on that database. It does not > report any issues for molly-guard 0.8. I also checked the underlying > database and see that it recognizes the duplicated diversions there. Thanks for all of the help Helmut! I have uploaded 0.8.1 to unstable. Francois -- https://fmarier.org/
Bug#1055510: Best way to coordinate this fix
On 2023-11-10 at 02:45:14, Helmut Grohne (hel...@subdivi.de) wrote: > Thank you. The package built and dumat has imported it. I locally forked > its analysis database pretending that systemd would not declare a > conflict for molly-guard and reran it on that database. It does not > report any issues for molly-guard 0.8. I also checked the underlying > database and see that it recognizes the duplicated diversions there. Thanks for all of the help Helmut! I have uploaded 0.8.1 to unstable. Francois -- https://fmarier.org/
Bug#1055510: Best way to coordinate this fix
On 2023-11-08 at 21:15:58, Helmut Grohne (hel...@subdivi.de) wrote: > Thank you. I suggest going via experimental first. I've just uploaded to experimental. If there are any tests you can easily run there, please do so. I've upgraded in unstable from the current version to 0.8 without problems, so that should in theory work when I eventually upload to unstable. Francois -- https://fmarier.org/
Bug#1055510: Best way to coordinate this fix
On 2023-11-08 at 21:15:58, Helmut Grohne (hel...@subdivi.de) wrote: > Thank you. I suggest going via experimental first. I've just uploaded to experimental. If there are any tests you can easily run there, please do so. I've upgraded in unstable from the current version to 0.8 without problems, so that should in theory work when I eventually upload to unstable. Francois -- https://fmarier.org/
Bug#1055670: fwknop-server: must Depends: apparmor-profiles-extra
> The latest update breaks apparmor for the whole system. > > /etc/apparmor.d/usr.sbin.fwknopd: > include > > This must declare Depends: apparmor-profiles-extra. > > Otherwise the apparmor service can't parse the file and will refuse to start. Ah, that's annoying. I don't think I'll want to make fwknop-server require apparmor. I guess this means I need to reintroduce the fwknop-apparmor package. Thanks for flagging this. Francois -- https://fmarier.org/
Bug#1055670: fwknop-server: must Depends: apparmor-profiles-extra
> The latest update breaks apparmor for the whole system. > > /etc/apparmor.d/usr.sbin.fwknopd: > include > > This must declare Depends: apparmor-profiles-extra. > > Otherwise the apparmor service can't parse the file and will refuse to start. Ah, that's annoying. I don't think I'll want to make fwknop-server require apparmor. I guess this means I need to reintroduce the fwknop-apparmor package. Thanks for flagging this. Francois -- https://fmarier.org/
Bug#1055510: Best way to coordinate this fix
If anybody would like to double-check (or test) the package I've prepared, it's in salsa right now. Francois
Bug#1055510: Best way to coordinate this fix
If anybody would like to double-check (or test) the package I've prepared, it's in salsa right now. Francois
Bug#1055510: Best way to coordinate this fix
Hi Luca, What's the best way to coordinate a fix for this? I assume that we shouldn't upload a new molly-guard packages until the files have actually moved in the systemd package? Should we wait until systemd is in unstable to push a new molly-guard out? Francois -- https://fmarier.org/
Bug#1055510: Best way to coordinate this fix
Hi Luca, What's the best way to coordinate a fix for this? I assume that we shouldn't upload a new molly-guard packages until the files have actually moved in the systemd package? Should we wait until systemd is in unstable to push a new molly-guard out? Francois -- https://fmarier.org/
Re: [Libravatar-fans] blog.libravatar.org access
On 2023-10-22 at 08:25:51, Oliver Falk (oli...@linux-kernel.at) wrote: > I wanted to correct a link on blog.libravatar.org, but whatever I try, I > always end up with the message that the page I want to edit is locked. It > also seems like I do not have any kind of admin access. > Does anybody have admin access and/or knowledge how to get rid of the > locked pages issue? I don't have admin access, but from memory, I think ad...@libravatar.org might. Francois -- https://fmarier.org/ ___ Mailing list: https://launchpad.net/~libravatar-fans Post to : libravatar-fans@lists.launchpad.net Unsubscribe : https://launchpad.net/~libravatar-fans More help : https://help.launchpad.net/ListHelp
Bug#1052115: Workrave 1.10.52 ready for GNOME 45
I've just uploaded workrave 1.10.52 which is ready for GNOME 45, but I've not yet enabled that support since support for GNOME 44 and 45 are mutually exclusive. Francois -- https://fmarier.org/
Bug#1051896: rkhunter: CVE-2023-4413
On 2023-09-13 at 14:15:53, Moritz Mühlenhoff (j...@inutil.org) wrote: > https://gist.github.com/MatheuZSecurity/16ef0219db8f85f49f945a25d5eb42d7 My summary of this is: it's possible to figure out what files/ports/etc. rkhunter is looking for by looking at the log file. That log file is: -rw-r- 1 root adm 502K 13 sep 07:41 rkhunter.log and on my machine that means only root and logcheck can see it: $ grep adm /etc/group adm:x:4:logcheck Of course, it's also possible to find out what files/ports/etc. rkhunter is looking for by looking in /usr/share/rkhunter/scripts/ or looking at the source code (https://sourceforge.net/p/rkhunter/rkh_code/ci/develop/tree/files/). So am I missing something here or is this simply not relevant given the rkhunter threat model of being an Open Source tool with a public database? Francois
Bug#1041374: fwknop-client: Cannot resolve own IP address
Sorry for the long delay Patrick. On 2023-07-18 at 00:26:18, pa...@mailbox.org (pa...@mailbox.org) wrote: > currently it is not possible to create a SPA packet without configuring a > RESOLVE_URL in .fwknoprc file. The error message is: > > [-] Could not resolve IP via: '/usr/bin/wget -U Fwknop/2.6.10 > --secure-protocol=auto --quiet -O - https://www.cipherdyne.org/cgi-bin/myip' I also noticed this on one of my machines. > I expect this to be an upstream problem – but I'm not 100% sure :-) Yes, I would say so. It would be good if the fallback could cases like these, though maybe it's not easy to do, I'm not sure. Would you like to suggest this upstream (https://github.com/mrash/fwknop/issues), or would you prefer I do it? The only somewhat related issue I could find is https://github.com/mrash/fwknop/issues/168 (from 8 years ago). Francois -- https://fmarier.org/
Bug#1050303: extension no longer works with Gnome 44
On 2023-08-22 at 14:31:31, Sébastien Villemot (sebast...@debian.org) wrote: > Actually I reported this problem in the Debian BTS because I was not > 100% > sure that this is an upstream issue (the error message is actually > compatible > with a missing file in the .deb). You're right. It turns out the reason why that 2.0 typelib file was missing is that it requires that GTK4 support be enabled: https://github.com/rcaelers/workrave/commit/5fe6e9c0060cae3a4bf1210c92c26b01022ddb1e#diff-67b94d110f4fed7b4a0ea8d4f780209ebbf5b69010701e5e3c646f641c730425 and there was a missing build dependency preventing the GTK4 support from being built. Francois
Bug#1050303: extension no longer works with Gnome 44
Bonjours Sébastien, It does look like a different error message indeed. Are you happy to also report this new problem upstream, or would you prefer I forward your email to upstream's GitHub issue tracker myself? Francois On 2023-08-22 at 12:35:24, Sébastien Villemot (sebast...@debian.org) wrote: > Package: workrave-gnome > Version: 1.10.51.1-2 > Severity: normal > > Dear Maintainer, > > After upgrading to gnome-shell 44, the extension no longer works. > > In the Extensions application, I am unable to activate the extension, and the > following message is displayed: > > Requiring Workrave, version 2.0: Typelib file for namespace 'Workrave', > version '2.0' not found > > Note that this seems to be a different issue than the following upstream one: > https://github.com/rcaelers/workrave/issues/487 > > Thanks for your work, > > -- > ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot > ⣾⠁⢠⠒⠀⣿⡁ Debian Developer > ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name > ⠈⠳⣄ https://www.debian.org
Bug#1043003: RFP: node-socket-cli -- CLI tool for Socket.dev
Package: wnpp Severity: wishlist * Package name: node-socket-cli Version : 0.7.1 Upstream Contact: Socket (https://github.com/SocketDev/) * URL : https://github.com/SocketDev/socket-cli-js * License : MIT Programming Lang: JavaScript Description : CLI tool for Socket.dev This tool can be used to pull useful security information out of the socket.dev (proprietary) service, but more interestingly, it can also be used as a safety wrapper around the npm: https://socket.dev/blog/introducing-safe-npm
Bug#1043003: RFP: node-socket-cli -- CLI tool for Socket.dev
Package: wnpp Severity: wishlist * Package name: node-socket-cli Version : 0.7.1 Upstream Contact: Socket (https://github.com/SocketDev/) * URL : https://github.com/SocketDev/socket-cli-js * License : MIT Programming Lang: JavaScript Description : CLI tool for Socket.dev This tool can be used to pull useful security information out of the socket.dev (proprietary) service, but more interestingly, it can also be used as a safety wrapper around the npm: https://socket.dev/blog/introducing-safe-npm
Bug#1038207: 6.4 is now the default kernel
I just hit this bug upgrading the kernel package in unstable. The patch worked for me as well. It would be good to get that uploaded as soon as possible since it's going to affect lots of people now that 6.4 is the default. Francois
Bug#1038431: FAILED: was not updated because protocol is not supported.
Package: ddclient Version: 3.10.0-2 Severity: normal Since upgrading to bookworm (from bullseye), I see these failures in my logs: ddclient[1081]: FAILED:was not updated because protocol is not supported. This is what my /etc/ddclient.conf contains: ssl=yes protocol=noip use=web, web=https://ip-address-reflector.example/ server=dynupdate.no-ip.com login=username password='...' hostname.dyn.domain.example I thought the systemd unit file was having problems reading the config file in /etc/: -rw--- 1 root root 268 Feb 14 2022 ddclient.conf and so I added this in /lib/systemd/system/ddclient.service: [Service] User=root but it didn't seem to do anything. Francois -- https://fmarier.org/
Bug#1037163: workrave-gnome: Incompatible with GNOME Shell 44
On 2023-06-06 at 11:33:17, Jeremy Bícha (jeremy.bi...@canonical.com) wrote: > If this bug is still not fixed, workrave will need to be removed from > Debian Testing when the Debian GNOME team performs the GNOME Shell 44 > transition which could happen as early as next month. A workaround is > to temporarily stop building the workrave-gnome binary package from > the workrave source. Looks like upstream has a fix: https://github.com/rcaelers/workrave/commit/5fe6e9c0060cae3a4bf1210c92c26b01022ddb1e I'll wait a bit to see if a new upstream release comes. Francois -- https://fmarier.org/
Andrew Ruthven: Advocate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 For nm.debian.org, at 2023-06-11: I support Andrew Ruthven 's request to become a Debian Developer, uploading. I have worked with Andrew Ruthven on mythtv-request for more than 15 years and I consider him as having sufficient technical competence. In addition to Debian work, we have also worked together at Catalyst IT and I have always been impressed with Andrew's breadth and depth of knowledge when it comes to Linux, operations and networking topics. I have personally worked with Andrew Ruthven (key C603FC4E600F1CECD1C8D97C4B53D931E4D3E863) for more than 15 years, and I know Andrew Ruthven can be trusted to be a full member of Debian, and have unsupervised, unrestricted upload rights, right now. -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAmSGFCNfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8 mNFpHA/+P+jDXsTvHwANtxFlUdrHM28VmMiSLyLHIZqI9kpAASsH2/6xyH2PdYdI RR0G+Y+TJR5F7eMzEUUb+8bnrg6SN2KCLYIEVtAW4CfM5ci1IF3prhFr4QwJPt63 /bMByGc1KEx/zcNeJ5mdb+p/FpIu/ufif2qsrJteTtePaQvPGT6p5jzd0Y9SGNXG yJvHBfnqBMN/gOOxe70csiX5sb7Cb/lYVCp9ERA0OaEJsGDAa+9YC3u0zIkLB5iP qbeKrf/JTYEKWYv22Ddx16djDhKS3uKaoQ9NOTvcNueQ0rFMNGzZUjCuBMch85ma fnJf7EQaPTXtlB0T+MAaLS173QJPMAgoNbiZO3+2OlXkJSsJ9F8fINsY2KRPoprW xwq0iGqssfcTzZ8aFOJJyrEIV/H8F0I4vnaYJ7fWqMuId8GXi0hPdIul2DcTtER5 KXgVGAxAeP1CkAwOfLy58Ej/Kd7FTiG9mXyKGvYl0slYI7Ry7FGBushYu7m9lgRP zUY76ziIJsftoTQm/TpO9onemWMj6QtToFCuUwlZ0kJoWtQN7DCe4LsCri4LYCJ/ sXrcvsgUJowq3yazA9dbA9jB26qwM0Oe/IH/JeQi0hSEMtI21gPQJ6Q4ITpnaA8K Gf2BWUedoVPyzJXmK9jQppSMOjKXJM5qkTbwxVhoQ6M+vN6WNz0= =JbxL -END PGP SIGNATURE- Francois Marier (via nm.debian.org) For details and to comment, visit https://nm.debian.org/process/1190/ -- https://nm.debian.org/process/1190/
Bug#1034596: RFP: pdfsizeopt -- PDF file size optimizer
Package: wnpp Severity: wishlist * Package name: pdfsizeopt Version : v9 Upstream Contact: Péter Szabó (https://keybase.io/pts) * URL : https://github.com/pts/pdfsizeopt * License : GPL-2.0 Programming Lang: Python Description : PDF file size optimizer pdfsizeopt is a program for converting large PDF files to small ones, without decreasing visual quality or removing interactive features (such as hyperlinks). More specifically, pdfsizeopt is a command-line application and a collection of best practices to optimize the size of PDF files, with focus on PDFs created from TeX and LaTeX documents.
Bug#1034596: RFP: pdfsizeopt -- PDF file size optimizer
Package: wnpp Severity: wishlist * Package name: pdfsizeopt Version : v9 Upstream Contact: Péter Szabó (https://keybase.io/pts) * URL : https://github.com/pts/pdfsizeopt * License : GPL-2.0 Programming Lang: Python Description : PDF file size optimizer pdfsizeopt is a program for converting large PDF files to small ones, without decreasing visual quality or removing interactive features (such as hyperlinks). More specifically, pdfsizeopt is a command-line application and a collection of best practices to optimize the size of PDF files, with focus on PDFs created from TeX and LaTeX documents.
Bug#1034276: unblock: fwknop/2.6.10-16
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: fwk...@packages.debian.org Control: affects -1 + src:fwknop Please unblock package fwknop [ Reason ] The AppArmor profile was incorrectly installed in the systemd system service path: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034055 [ Impact ] I'm not sure whether it would cause any actual problems, but it is likely a policy violation and the bug reporter did file it as an RC bug. [ Tests ] I upgraded to the version I uploaded to unstable yesterday and confirmed that the file is in the new location: $ dpkg -L fwknop-apparmor-profile | grep usr.sbin.fwknopd /usr/share/apparmor/extra-profiles/usr.sbin.fwknopd [ Risks ] Trivial fix. I made it so that the AppArmor profile is not automatically enabled either to avoid changing (i.e. fixing) the behavior compared to what it was in -15. So this should be a no-op in terms of functionality. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock fwknop/2.6.10-16 diff -Nru fwknop-2.6.10/debian/changelog fwknop-2.6.10/debian/changelog --- fwknop-2.6.10/debian/changelog 2023-01-10 21:23:46.0 -0800 +++ fwknop-2.6.10/debian/changelog 2023-04-10 20:52:01.0 -0700 @@ -1,3 +1,12 @@ +fwknop (2.6.10-16) unstable; urgency=high + + * Install apparmor profile in /usr/share/apparmor/extra-profiles/ +instead of the systemd service directory. Note that the profile +will not be used unless manually copied into /etc/apparmor.d/ +(Closes: #1034055). + + -- Francois Marier Mon, 10 Apr 2023 20:52:01 -0700 + fwknop (2.6.10-15) unstable; urgency=medium [ Helmut Grohne ] diff -Nru fwknop-2.6.10/debian/fwknop-apparmor-profile.install fwknop-2.6.10/debian/fwknop-apparmor-profile.install --- fwknop-2.6.10/debian/fwknop-apparmor-profile.install 2023-01-10 21:23:46.0 -0800 +++ fwknop-2.6.10/debian/fwknop-apparmor-profile.install 2023-04-10 20:52:01.0 -0700 @@ -1 +1 @@ -extras/apparmor/usr.sbin.fwknopd /usr/lib/systemd/system/ +extras/apparmor/usr.sbin.fwknopd /usr/share/apparmor/extra-profiles/
Bug#1034276: unblock: fwknop/2.6.10-16
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: fwk...@packages.debian.org Control: affects -1 + src:fwknop Please unblock package fwknop [ Reason ] The AppArmor profile was incorrectly installed in the systemd system service path: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034055 [ Impact ] I'm not sure whether it would cause any actual problems, but it is likely a policy violation and the bug reporter did file it as an RC bug. [ Tests ] I upgraded to the version I uploaded to unstable yesterday and confirmed that the file is in the new location: $ dpkg -L fwknop-apparmor-profile | grep usr.sbin.fwknopd /usr/share/apparmor/extra-profiles/usr.sbin.fwknopd [ Risks ] Trivial fix. I made it so that the AppArmor profile is not automatically enabled either to avoid changing (i.e. fixing) the behavior compared to what it was in -15. So this should be a no-op in terms of functionality. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing unblock fwknop/2.6.10-16 diff -Nru fwknop-2.6.10/debian/changelog fwknop-2.6.10/debian/changelog --- fwknop-2.6.10/debian/changelog 2023-01-10 21:23:46.0 -0800 +++ fwknop-2.6.10/debian/changelog 2023-04-10 20:52:01.0 -0700 @@ -1,3 +1,12 @@ +fwknop (2.6.10-16) unstable; urgency=high + + * Install apparmor profile in /usr/share/apparmor/extra-profiles/ +instead of the systemd service directory. Note that the profile +will not be used unless manually copied into /etc/apparmor.d/ +(Closes: #1034055). + + -- Francois Marier Mon, 10 Apr 2023 20:52:01 -0700 + fwknop (2.6.10-15) unstable; urgency=medium [ Helmut Grohne ] diff -Nru fwknop-2.6.10/debian/fwknop-apparmor-profile.install fwknop-2.6.10/debian/fwknop-apparmor-profile.install --- fwknop-2.6.10/debian/fwknop-apparmor-profile.install 2023-01-10 21:23:46.0 -0800 +++ fwknop-2.6.10/debian/fwknop-apparmor-profile.install 2023-04-10 20:52:01.0 -0700 @@ -1 +1 @@ -extras/apparmor/usr.sbin.fwknopd /usr/lib/systemd/system/ +extras/apparmor/usr.sbin.fwknopd /usr/share/apparmor/extra-profiles/
Bug#1034055: fwknop-apparmor-profile: AppArmor profile installed in systemd system service path
On 2023-04-07 at 07:23:07, Laurent Bigonville (bi...@debian.org) wrote: > It seems that you install the apparmor profile in the path for systemd system > service > > The following change should be reverted: > https://salsa.debian.org/debian/fwknop/-/commit/d3a5aaef39fedc1bb94e26921afbf63f79b31af7 Hm, that does look like a mistake. I don't remember what might have caused me to make that change. I guess the apparmor profile hasn't been in use for a while then. It seems like it's too late in the release process to re-add it in bookworm. Here's what I'm thinking of doing: - move it to /usr/share/apparmor/extra-profiles/ (so it's not turned on by default) for bookworm - move it back to /etc/apparmor.d/ after bookworm Alternatively, I could also not change anything for bookworm since it's not enabled as an AppArmor profile and it will be ignored as a systemd unit file. What do you think? Francois
Bug#1034055: fwknop-apparmor-profile: AppArmor profile installed in systemd system service path
On 2023-04-07 at 07:23:07, Laurent Bigonville (bi...@debian.org) wrote: > It seems that you install the apparmor profile in the path for systemd system > service > > The following change should be reverted: > https://salsa.debian.org/debian/fwknop/-/commit/d3a5aaef39fedc1bb94e26921afbf63f79b31af7 Hm, that does look like a mistake. I don't remember what might have caused me to make that change. I guess the apparmor profile hasn't been in use for a while then. It seems like it's too late in the release process to re-add it in bookworm. Here's what I'm thinking of doing: - move it to /usr/share/apparmor/extra-profiles/ (so it's not turned on by default) for bookworm - move it back to /etc/apparmor.d/ after bookworm Alternatively, I could also not change anything for bookworm since it's not enabled as an AppArmor profile and it will be ignored as a systemd unit file. What do you think? Francois
Bug#1033306: tor: Tor relays running 0.4.5.16 will soon be cut off from the network
Package: tor Version: 0.4.5.16-1 Severity: grave Justification: renders package unusable I received the following email from the Tor Project: Hi, You are running a bunch of Tor relays, which is great: However, those relays' Tor version is obsolete, and because of old bugs, we will soon cut relays and bridges running that version out of the network. Please consider upgrading! You can find Tor packages and instructions for your distro / OS here: https://community.torproject.org/relay/setup/guard/ If you need help upgrading your relays, please use the Tor Forum: https://forum.torproject.net/c/support/relay-operator/17 Let us know if we can do anything to make the process easier. Thanks! Georg They are currently aiming for a cut-off date 4-6 weeks from now. This means that the version of tor that's in bullseye will essentially stop working for most uses. There is already a version in backports that will work fine, but perhaps it's worth also uploading it to stable for the next point release? Francois -- https://fmarier.org/
Bug#1033306: tor: Tor relays running 0.4.5.16 will soon be cut off from the network
Package: tor Version: 0.4.5.16-1 Severity: grave Justification: renders package unusable I received the following email from the Tor Project: Hi, You are running a bunch of Tor relays, which is great: However, those relays' Tor version is obsolete, and because of old bugs, we will soon cut relays and bridges running that version out of the network. Please consider upgrading! You can find Tor packages and instructions for your distro / OS here: https://community.torproject.org/relay/setup/guard/ If you need help upgrading your relays, please use the Tor Forum: https://forum.torproject.net/c/support/relay-operator/17 Let us know if we can do anything to make the process easier. Thanks! Georg They are currently aiming for a cut-off date 4-6 weeks from now. This means that the version of tor that's in bullseye will essentially stop working for most uses. There is already a version in backports that will work fine, but perhaps it's worth also uploading it to stable for the next point release? Francois -- https://fmarier.org/
Bug#1028394: fwknop FTCBFS: builds the perl extension for the build architecture
On 2023-01-10 at 02:44:41, Helmut Grohne (hel...@subdivi.de) wrote: > fwknop fails to cross build from source, because it attempts to build > its perl extension for the build architecture. In order to get the > development files for the host architecture, a dependency on perl-xs-dev > is needed and since there is no dh_auto_foo involved in the perl > extension, the PERL5LIB needs to be set up manually. I'm attaching a > patch for your convenience. Thanks for the patch Helmut. It's much appreciated given how little I know about the Perl ecosystem these days. Francois signature.asc Description: PGP signature
Bug#1021693: Initial packaging
Initial packaging work: https://salsa.debian.org/debian/buskill Discussion with upstream: https://github.com/BusKill/buskill-app/issues/31 Francois -- https://fmarier.org/
Bug#1021693: Initial packaging
Initial packaging work: https://salsa.debian.org/debian/buskill Discussion with upstream: https://github.com/BusKill/buskill-app/issues/31 Francois -- https://fmarier.org/
Bug#1022940: tiger: diff for NMU version 1:3.2.4~rc1-3.2
Control: tags 1022940 + patch Control: tags 1022940 + pending Dear maintainer, I've prepared an NMU for tiger (versioned as 1:3.2.4~rc1-3.2) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. Francois -- https://fmarier.org/ diff -u tiger-3.2.4~rc1/debian/changelog tiger-3.2.4~rc1/debian/changelog --- tiger-3.2.4~rc1/debian/changelog +++ tiger-3.2.4~rc1/debian/changelog @@ -1,3 +1,10 @@ +tiger (1:3.2.4~rc1-3.2) unstable; urgency=medium + + * Non-maintainer upload. + * debian/rules: add symlink for Linux 6 (Closes: #1022940) + + -- Francois Marier Thu, 27 Oct 2022 21:35:23 -0700 + tiger (1:3.2.4~rc1-3.1) unstable; urgency=medium * Non-maintainer upload. diff -u tiger-3.2.4~rc1/debian/rules tiger-3.2.4~rc1/debian/rules --- tiger-3.2.4~rc1/debian/rules +++ tiger-3.2.4~rc1/debian/rules @@ -60,13 +60,15 @@ # Adjust the permissions of directories that might contain confidential information chmod 0700 debian/tiger/var/lib/tiger/work chmod 0700 debian/tiger/var/log/tiger - # Create symbolic links for Linux versions 3, 4, 5, and default + # Create symbolic links for Linux versions 3, 4, 5, 6 and default [ -e debian/tiger/usr/lib/tiger/systems/Linux/3 ] || \ ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/3 [ -e debian/tiger/usr/lib/tiger/systems/Linux/4 ] || \ ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/4 [ -e debian/tiger/usr/lib/tiger/systems/Linux/5 ] || \ ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/5 + [ -e debian/tiger/usr/lib/tiger/systems/Linux/6 ] || \ + ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/6 [ -e debian/tiger/usr/lib/tiger/systems/Linux/default ] || \ ln -fs 2 debian/tiger/usr/lib/tiger/systems/Linux/default # Remove unneeded Makefile files.
Bug#1022940: tiger doesn't support version 6 of the Linux kernel properly
Package: tiger Version: 1:3.2.4~rc1-3.1 Severity: important While there is a `default` symlink in /usr/lib/tiger/systems/Linux/, it doesn't seem to work because I received a very large number of bogus warnings after upgrading to Linux 6: NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket 24455 (raw6 on 24455 interface) is run by root. NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket 28195 (IPv6 on 28195 interface) is run by 1596. NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket 28195 (IPv6 on 28195 interface) is run by 1599. NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket UDP (0t0 on UDP interface) is run by root. NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket raw6 (root on raw6 interface) is run by 1596. NEW: --WARN-- [lin003w] The process `NetworkMa' is listening on socket raw6 (root on raw6 interface) is run by 1599. NEW: --WARN-- [lin003w] The process `apache2' is listening on socket TCP (0t0 on TCP interface) is run by root. NEW: --WARN-- [lin003w] The process `apache2' is listening on socket TCP (0t0 on TCP interface) is run by www-data. NEW: --WARN-- [lin003w] The process `avahi-dae' is listening on socket UDP (0t0 on UDP interface) is run by avahi. NEW: --WARN-- [lin003w] The process `cupsd' is listening on socket TCP (0t0 on TCP interface) is run by root. NEW: --WARN-- [lin003w] The process `dnsmasq' is listening on socket TCP (0t0 on TCP interface) is run by dnsmasq. NEW: --WARN-- [lin003w] The process `dnsmasq' is listening on socket UDP (0t0 on UDP interface) is run by dnsmasq. ... The fix is to create a symlink for version 6 of the kernel explicitly: cd /usr/lib/tiger/systems/Linux/ sudo ln -s 5 6 Francois -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tiger depends on: ii binutils 2.39-8 ii bsdutils 1:2.38.1-1.1+b1 ii debconf [debconf-2.0] 1.5.79 ii debianutils5.7-0.3 ii libc6 2.35-3 ii lsb-release12.0-1 ii net-tools 1.60+git20181103.0eebece-1 ii ucf3.0043 Versions of packages tiger recommends: ii chkrootkit 0.55-4+b2 pn john ii postfix [mail-transport-agent] 3.7.3-2 pn tripwire | aide Versions of packages tiger suggests: ii lsof 4.95.0-1 ii lynis 3.0.8-1.1 -- Configuration Files: /etc/cron.d/tiger [Errno 13] Permission non accordée: '/etc/cron.d/tiger' -- debconf information: * tiger/mail_rcpt: root * tiger/policy_adapt: -- https://fmarier.org/
Bug#1021693: RFP: buskill -- app for arming/disarming/configuring the BusKill laptop kill cord
Package: wnpp Severity: wishlist * Package name: buskill Version : 0.5.0 Upstream Author : Michael Altfield * URL : https://github.com/BusKill/buskill-app * License : GPL-3.0 Programming Lang: Python Description : app for arming/disarming/configuring the BusKill laptop kill cord BusKill is a laptop kill cord that can trigger your computer to lock or shutdown when it's physically separated from you.
Bug#1021693: RFP: buskill -- app for arming/disarming/configuring the BusKill laptop kill cord
Package: wnpp Severity: wishlist * Package name: buskill Version : 0.5.0 Upstream Author : Michael Altfield * URL : https://github.com/BusKill/buskill-app * License : GPL-3.0 Programming Lang: Python Description : app for arming/disarming/configuring the BusKill laptop kill cord BusKill is a laptop kill cord that can trigger your computer to lock or shutdown when it's physically separated from you.
Bug#976626: Similar package
On 2022-10-01 at 09:57:35, Antoine Beaupré (anar...@debian.org) wrote: > Yeah, so tldr is similar, but cheat has a number of improvements, from > my perspective. Thanks for those details. I had not looked into cheat all that much, but now I'm curious to check it out! Francois -- https://fmarier.org/
Bug#976626: Similar package
On 2022-10-01 at 09:57:35, Antoine Beaupré (anar...@debian.org) wrote: > Yeah, so tldr is similar, but cheat has a number of improvements, from > my perspective. Thanks for those details. I had not looked into cheat all that much, but now I'm curious to check it out! Francois -- https://fmarier.org/
Bug#1020590: tiger: diff for NMU version 1:3.2.4~rc1-3.1
Package: tiger
Version: 1:3.2.4~rc1-3
Severity: normal
Tags: patch
Dear maintainer,
I've prepared an NMU for tiger (versioned as 1:3.2.4~rc1-3.1) and uploaded
it to DELAYED/5. Please feel free to tell me if I should delay it longer.
It consists of a single fix for bug #987512. Attached is the debdiff.
Regards.
Francois
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.19.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tiger depends on:
ii binutils 2.38.90.20220713-2
ii bsdutils 1:2.38.1-1
ii debconf [debconf-2.0] 1.5.79
ii debianutils5.7-0.3
ii libc6 2.35-1
ii lsb-release11.4
ii net-tools 1.60+git20181103.0eebece-1
ii ucf3.0043
Versions of packages tiger recommends:
ii chkrootkit 0.55-4+b2
pn john
ii postfix [mail-transport-agent] 3.6.4-1+b3
pn tripwire | aide
Versions of packages tiger suggests:
ii lsof 4.95.0-1
ii lynis 3.0.8-1
-- debconf information:
* tiger/mail_rcpt: root
* tiger/policy_adapt:
--
https://fmarier.org/
diff -u tiger-3.2.4~rc1/debian/changelog tiger-3.2.4~rc1/debian/changelog
--- tiger-3.2.4~rc1/debian/changelog
+++ tiger-3.2.4~rc1/debian/changelog
@@ -1,3 +1,10 @@
+tiger (1:3.2.4~rc1-3.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Teach tiger about fuse.portal (Closes: #987512)
+
+ -- Francois Marier Fri, 23 Sep 2022 12:03:08 -0700
+
tiger (1:3.2.4~rc1-3) unstable; urgency=medium
* Acknowledge NMU (Closes: #969303)
diff -u tiger-3.2.4~rc1/systems/Linux/2/gen_mounts tiger-3.2.4~rc1/systems/Linux/2/gen_mounts
--- tiger-3.2.4~rc1/systems/Linux/2/gen_mounts
+++ tiger-3.2.4~rc1/systems/Linux/2/gen_mounts
@@ -184,6 +184,7 @@
[ "$1" = "fuse.gvfsd-fuse" ] && LOCAL=1 # Used in Ubuntu 13.10 (Saucy Salamander) replaces fuse.gvfs-fuse-daemon
[ "$1" = "fuse.ltspfs" ] && LOCAL=0 # Used by LTSP 5.x
[ "$1" = "fuse.lxcfs" ] && LOCAL=0
+ [ "$1" = "fuse.portal" ] && LOCAL=0
[ "$1" = "fuse.clamfs" ] && LOCAL=0 # ClamFS anti-virus protected file system
[ "$1" = "fuse.javafs" ] && LOCAL=0 # Java FS, used by Wuala secure online storage, see:
# https://github.com/puniverse/javafs
only in patch2:
unchanged:
--- tiger-3.2.4~rc1.orig/configure
+++ tiger-3.2.4~rc1/configure
@@ -1,9 +1,10 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.69.
+# Generated by GNU Autoconf 2.71.
#
#
-# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
+# Copyright (C) 1992-1996, 1998-2017, 2020-2021 Free Software Foundation,
+# Inc.
#
#
# This configure script is free software; the Free Software Foundation
@@ -14,14 +15,16 @@
# Be more Bourne compatible
DUALCASE=1; export DUALCASE # for MKS sh
-if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
+as_nop=:
+if test ${ZSH_VERSION+y} && (emulate sh) >/dev/null 2>&1
+then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
setopt NO_GLOB_SUBST
-else
+else $as_nop
case `(set -o) 2>/dev/null` in #(
*posix*) :
set -o posix ;; #(
@@ -31,46 +34,46 @@
fi
+
+# Reset variables that may have inherited troublesome values from
+# the environment.
+
+# IFS needs to be set, to space, tab, and newline, in precisely that order.
+# (If _AS_PATH_WALK were called with IFS unset, it would have the
+# side effect of setting IFS to empty, thus disabling word splitting.)
+# Quoting is to prevent editors from complaining about space-tab.
as_nl='
'
export as_nl
-# Printing a long string crashes Solaris 7 /usr/bin/printf.
-as_echo='\\\'
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
-as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
-# Prefer a ksh shell builtin over an external printf program on Solaris,
-# but without wasting forks for bash or zsh.
-if test -z "$BASH_VERSION$ZSH_VERSION" \
-&& (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/
Bug#1017648: How to apply the patch in bug 987512
To apply the patch in the other bug, simply open /usr/lib/tiger/systems/Linux/2/gen_mounts in a text editor (as root) and then insert this line: [ "$1" = "fuse.portal" ] && LOCAL=0 in between: [ "$1" = "fuse.lxcfs" ] && LOCAL=0 and: [ "$1" = "fuse.clamfs" ] && LOCAL=0 # ClamFS anti-virus protected file system The patch itself can be found here: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=987512;filename=tiger-fuse_portal.patch;msg=5 Francois -- https://fmarier.org/
Bug#1019701: RFP: rpi-imager -- Raspberry Pi Imaging Utility
Package: wnpp Severity: wishlist * Package name: rpi-imager Version : 1.7.3 Upstream Author : Raspberry Pi * URL : https://github.com/raspberrypi/rpi-imager * License : Apache-2.0 Programming Lang: C++ Description : Raspberry Pi Imaging Utility Raspberry Pi Imager is the quick and easy way to install Raspberry Pi OS and other operating systems (but not Debian) to a microSD card, ready to use with your Raspberry Pi.
Bug#1019701: RFP: rpi-imager -- Raspberry Pi Imaging Utility
Package: wnpp Severity: wishlist * Package name: rpi-imager Version : 1.7.3 Upstream Author : Raspberry Pi * URL : https://github.com/raspberrypi/rpi-imager * License : Apache-2.0 Programming Lang: C++ Description : Raspberry Pi Imaging Utility Raspberry Pi Imager is the quick and easy way to install Raspberry Pi OS and other operating systems (but not Debian) to a microSD card, ready to use with your Raspberry Pi.
Bug#1019325: Patch
Here's the patch I applied locally to my /etc to fix these warnings.
Francois
--
https://fmarier.org/
diff --git a/logcheck/ignore.d.server/anon-proxy b/logcheck/ignore.d.server/anon-proxy
index 6b111708..31a442fd 100644
--- a/logcheck/ignore.d.server/anon-proxy
+++ b/logcheck/ignore.d.server/anon-proxy
@@ -1,2 +1,2 @@
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ AnonMix: \[[0-9]+/[0-9]+/[0-9]+-[:0-9]+, info +\] +Try connecting to next Mix\.\.\.$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ AnonMix: \[[0-9]+/[0-9]+/[0-9]+-[:0-9]+, info +\] +connected\!$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ AnonMix: \[[0-9]+/[0-9]+/[0-9]+-[:0-9]+, info +\] +connected!$
diff --git a/logcheck/ignore.d.server/cyrus b/logcheck/ignore.d.server/cyrus
index c483b8e9..566b3fb7 100644
--- a/logcheck/ignore.d.server/cyrus
+++ b/logcheck/ignore.d.server/cyrus
@@ -2,5 +2,5 @@
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ cyrus/imapd\[[0-9]+\]: SQUAT failed( to open index file)?$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ cyrus/imapd\[[0-9]+\]: SQUAT returned [0-9]+ messages$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ cyrus/lmtpd\[[0-9]+\]: DBERROR db3: [12] lockers$
-^\w{3} [ :0-9]{11} [._[:alnum:]-]+ cyrus/notifyd\[[0-9]+\]: MAIL, , [^[:space:]]+, [^[:space:]]+, \"[ [:alnum:][:punct:]]+\"$
+^\w{3} [ :0-9]{11} [._[:alnum:]-]+ cyrus/notifyd\[[0-9]+\]: MAIL, , [^[:space:]]+, [^[:space:]]+, "[ [:alnum:][:punct:]]+"$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ cyrus/squatter\[[0-9]+\]: (skipping|indexing) mailbox [[:alpha:]^\.]+\.\.\.$
diff --git a/logcheck/ignore.d.server/dhcp b/logcheck/ignore.d.server/dhcp
index 3b34ef10..2f19495e 100644
--- a/logcheck/ignore.d.server/dhcp
+++ b/logcheck/ignore.d.server/dhcp
@@ -39,9 +39,9 @@
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: TLS session successfully started to [:_.[:alnum:]-]+$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: Successfully logged into LDAP server [._[:alnum:]-]+$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: (Found dhcpServer LDAP entry|LDAP: Parsing dhcpServer options|LDAP: Parsing dhcpService DN|Found LDAP entry|Parsing external DNs for) '[%=.,_[:alnum:]-]+'( \.\.\.)?$
-^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: (Searching|No host entry) for \(\&\(objectClass=dhcpHost\)\(dhcpHWAddress=ethernet [[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}\)\) in LDAP tree [=,.[:alnum:]]+$
+^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: (Searching|No host entry) for \(&\(objectClass=dhcpHost\)\(dhcpHWAddress=ethernet [[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}:[[:xdigit:]]{2}\)\) in LDAP tree [=,.[:alnum:]]+$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: Found dhcpHWAddress LDAP entry [-_=,.[:alnum:]]+$
-^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: Sending the following options: '(filename \"[.[:alnum:]]+\"|(fixed-address|next-server) [.[:digit:]]{7,15}|;#012)+'$
+^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: Sending the following options: '(filename "[.[:alnum:]]+"|(fixed-address|next-server) [.[:digit:]]{7,15}|;#012)+'$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: Sending config line '(allow booting|allow bootp|ddns-update-style (ad-hoc|interim|none)|(default|max|min)-lease-time [[:digit:]]+|authoritative|option domain-name "[._[:alnum:]-]+"|option domain-name-servers [._,[:alnum:][:space:]-]+|option subnet-mask [.[:digit:]]{7,15}|;#012)+'$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: Sending config line '((subnet|netmask|option routers|option subnet-mask) [.[:digit:]]{7,15}|(default|max|min)-lease-time [[:digit:]]+|[[:space:]]|\{#012|\}#012|;#012)+'$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dhcpd[[[:digit:]]+]: Sending config line 'pool (range [.[:digit:]]{7,15} [.[:digit:]]+|(default|min|max)-lease-time [[:digit:]]+|failover peer "[-._[:alnum:]]+"|deny dynamic bootp clients|[[:space:]]|\{#012|\}#012|;#012)+'$
diff --git a/logcheck/ignore.d.server/dovecot b/logcheck/ignore.d.server/dovecot
index 8f4dcb60..b59ad6da 100644
--- a/logcheck/ignore.d.server/dovecot
+++ b/logcheck/ignore.d.server/dovecot
@@ -5,7 +5,7 @@
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dovecot-auth: \(pam_unix\) check pass; user unknown$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dovecot-auth: pam_unix\(dovecot:[[:alnum:]]+\): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=([-_.@[:alnum:]]+)? rhost=([.:[:xdigit:]]+)?( user=[-_.@[:alnum:]]+)?$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dovecot-auth: pam_unix\(dovecot:[[:alnum:]]+\): check pass; user unknown$
-^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dovecot-auth: pam_ldap: error trying to bind as user \".*\" \(Invalid credentials\)$
+^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dovecot-auth: pam_ldap: error trying to bind as user ".*" \(Invalid credentials\)$
^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ dovecot: (imap|pop3)-login: Login: [.[:alnum:]@-]+
Bug#1019587: qflipper: Missing dependency on qml-module-qt-labs-platform
Package: qflipper Version: 1.1.1-2 Severity: important I installed qflipper and was unable to run it: $ qFlipper 34 [default] QQmlApplicationEngine failed to load component 35 [default] qrc:/main.qml:29:5: Type MainWindow unavailable 35 [default] qrc:/components/MainWindow.qml:7:1: module "Qt.labs.platform" is not installed 35 [APP] qFlipper version 1.1.1-2 commit unknown 2022-08-10T10:13:42 35 [APP] OS info: Debian GNU/Linux bookworm/sid unknown 5.18.0-4-amd64 After installing the qml-module-qt-labs-platform package, everything starts up fine. Please add the missing dependency (or at the very least a Recommends). Francois -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qflipper depends on: ii libc6 2.34-8 ii libgcc-s1 12.2.0-2 ii libqt5core5a5.15.4+dfsg-5 ii libqt5gui5 5.15.4+dfsg-5 ii libqt5network5 5.15.4+dfsg-5 ii libqt5qml5 5.15.4+dfsg-4 ii libqt5quick55.15.4+dfsg-4 ii libqt5quickcontrols2-5 5.15.4+dfsg-2 ii libqt5serialport5 5.15.4-2 ii libqt5widgets5 5.15.4+dfsg-5 ii libstdc++6 12.2.0-2 ii libusb-1.0-02:1.0.26-1 ii zlib1g 1:1.2.11.dfsg-4.1 qflipper recommends no packages. qflipper suggests no packages. -- no debconf information
Bug#848578: Also running into this problem
On 2022-09-07 at 12:42:31, Nicolas Schier (nico...@fjasle.eu) wrote: > Francois, might you be able to patch your ts with the attached patch > and re-check? As August has gone, I used > > echo test | faketime "2022-08-01" ./ts > > for testing with your specified locale settings. I've patched my /usr/bin/ts as you indicated and the above works well now: $ echo test | faketime "2022-01-04" ts jan 04 00:00:00 test $ echo test | faketime "2022-02-04" ts fév 04 00:00:00 test $ echo test | faketime "2022-07-04" ts jui 04 00:00:00 test $ echo test | faketime "2022-08-04" ts aoû 04 00:00:00 test Also, faketime is really handy! Thanks. Francois
Bug#1018794: RFP: fx -- terminal JSON viewer
Package: wnpp Severity: wishlist * Package name: fx Version : 24.0.0 Upstream Author : Anton Medvedev * URL : https://github.com/antonmedv/fx * License : MIT Programming Lang: Go Description : terminal JSON viewer Function eXecution (fx) is a terminal JSON viewer which includes these features: - Mouse support - Streaming support - Preserves key order - Preserves big numbers
Bug#1018794: RFP: fx -- terminal JSON viewer
Package: wnpp Severity: wishlist * Package name: fx Version : 24.0.0 Upstream Author : Anton Medvedev * URL : https://github.com/antonmedv/fx * License : MIT Programming Lang: Go Description : terminal JSON viewer Function eXecution (fx) is a terminal JSON viewer which includes these features: - Mouse support - Streaming support - Preserves key order - Preserves big numbers
Bug#1018733: RFP: htmlq -- uses CSS selectors to extract bits of content from HTML file
Package: wnpp Severity: wishlist * Package name: htmlq Version : 0.4.0 Upstream Author : Michael Maclean * URL : https://github.com/mgdm/htmlq * License : MIT Programming Lang: Rust Description : uses CSS selectors to extract bits of content from HTML file Like jq, but for HTML. Uses CSS selectors to extract bits of content from HTML files.
Bug#1018733: RFP: htmlq -- uses CSS selectors to extract bits of content from HTML file
Package: wnpp Severity: wishlist * Package name: htmlq Version : 0.4.0 Upstream Author : Michael Maclean * URL : https://github.com/mgdm/htmlq * License : MIT Programming Lang: Rust Description : uses CSS selectors to extract bits of content from HTML file Like jq, but for HTML. Uses CSS selectors to extract bits of content from HTML files.
Bug#1018258: RFP: procs -- modern replacement for ps
Package: wnpp Severity: wishlist * Package name: procs Version : 0.13.0 Upstream Author : Dalance * URL : https://github.com/dalance/procs * License : MIT Programming Lang: Rust Description : modern replacement for ps procs is a replacement for ps written in Rust. Features: - Colored and human-readable output - Automatic theme detection based on terminal background - Multi-column keyword search - Some additional information which are not supported by ps - TCP/UDP port - Read/Write throughput - Docker container name - More memory information - Pager support - Watch mode (like top) - Tree view
Bug#1018258: RFP: procs -- modern replacement for ps
Package: wnpp Severity: wishlist * Package name: procs Version : 0.13.0 Upstream Author : Dalance * URL : https://github.com/dalance/procs * License : MIT Programming Lang: Rust Description : modern replacement for ps procs is a replacement for ps written in Rust. Features: - Colored and human-readable output - Automatic theme detection based on terminal background - Multi-column keyword search - Some additional information which are not supported by ps - TCP/UDP port - Read/Write throughput - Docker container name - More memory information - Pager support - Watch mode (like top) - Tree view
Bug#1017956: RFP: croc -- easily and securely send things from one computer to another
Package: wnpp Severity: wishlist * Package name: croc Version : 9.6.0 Upstream Author : Zack Schollz * URL : https://schollz.com/software/croc6 * License : MIT Programming Lang: Go Description : easily and securely send things from one computer to another croc is a tool that allows any two computers to simply and securely transfer files and folders and does all of the following: - allows any two computers to transfer data (using a relay) - provides end-to-end encryption (using PAKE) - enables easy cross-platform transfers (Windows, Linux, Mac) - allows multiple file transfers - allows resuming transfers that are interrupted - local server or port-forwarding not needed - ipv6-first with ipv4 fallback - can use proxy, like tor
Bug#1017956: RFP: croc -- easily and securely send things from one computer to another
Package: wnpp Severity: wishlist * Package name: croc Version : 9.6.0 Upstream Author : Zack Schollz * URL : https://schollz.com/software/croc6 * License : MIT Programming Lang: Go Description : easily and securely send things from one computer to another croc is a tool that allows any two computers to simply and securely transfer files and folders and does all of the following: - allows any two computers to transfer data (using a relay) - provides end-to-end encryption (using PAKE) - enables easy cross-platform transfers (Windows, Linux, Mac) - allows multiple file transfers - allows resuming transfers that are interrupted - local server or port-forwarding not needed - ipv6-first with ipv4 fallback - can use proxy, like tor
Bug#1017687: RFP: xsv -- fast CSV command line toolkit
Package: wnpp Severity: wishlist * Package name: xsv Version : 0.13.0 Upstream Author : Andrew Gallant * URL : https://github.com/BurntSushi/xsv * License : MIT Programming Lang: Rust Description : fast CSV command line toolkit xsv is a command line program for indexing, slicing, analyzing, splitting and joining CSV files. Commands should be simple, fast and composable: 1. Simple tasks should be easy. 2. Performance trade offs should be exposed in the CLI interface. 3. Composition should not come at the expense of performance.
Bug#1017687: RFP: xsv -- fast CSV command line toolkit
Package: wnpp Severity: wishlist * Package name: xsv Version : 0.13.0 Upstream Author : Andrew Gallant * URL : https://github.com/BurntSushi/xsv * License : MIT Programming Lang: Rust Description : fast CSV command line toolkit xsv is a command line program for indexing, slicing, analyzing, splitting and joining CSV files. Commands should be simple, fast and composable: 1. Simple tasks should be easy. 2. Performance trade offs should be exposed in the CLI interface. 3. Composition should not come at the expense of performance.
Bug#1017575: RFP: jless -- command-line JSON viewer
Package: wnpp Severity: wishlist * Package name: jless Version : 0.8.0 Upstream Author : Paul Julius Martinez * URL : https://jless.io/ * License : MIT Programming Lang: Rust Description : command-line JSON viewer jless is a command-line JSON viewer. Use it as a replacement for whatever combination of less, jq, cat and your editor you currently use for viewing JSON files. Features: - Clean syntax highlighted display of JSON data, omitting quotes around object keys, closing object and array delimiters, and trailing commas. - Expand and collapse objects and arrays so you can see both the high- and low-level structure of the data. - A wealth of vim-inspired movement commands for efficiently moving around and viewing data. - Full regex-based search for finding exactly the data you're looking for.
Bug#1017575: RFP: jless -- command-line JSON viewer
Package: wnpp Severity: wishlist * Package name: jless Version : 0.8.0 Upstream Author : Paul Julius Martinez * URL : https://jless.io/ * License : MIT Programming Lang: Rust Description : command-line JSON viewer jless is a command-line JSON viewer. Use it as a replacement for whatever combination of less, jq, cat and your editor you currently use for viewing JSON files. Features: - Clean syntax highlighted display of JSON data, omitting quotes around object keys, closing object and array delimiters, and trailing commas. - Expand and collapse objects and arrays so you can see both the high- and low-level structure of the data. - A wealth of vim-inspired movement commands for efficiently moving around and viewing data. - Full regex-based search for finding exactly the data you're looking for.
Bug#1016995: RFP: sublist3r -- subdomains enumeration tool for penetration testers
Package: wnpp Severity: wishlist * Package name: sublist3r Version : 1.1 Upstream Author : Ahmed Aboul-Ela * URL : https://github.com/aboul3la/Sublist3r * License : GPL-2.0 Programming Lang: Python Description : subdomains enumeration tool for penetration testers Sublist3r is a python tool designed to enumerate subdomains of websites using OSINT. It helps penetration testers and bug hunters collect and gather subdomains for the domain they are targeting. Sublist3r enumerates subdomains using many search engines such as Google, Yahoo, Bing, Baidu and Ask. Sublist3r also enumerates subdomains using Netcraft, Virustotal, ThreatCrowd, DNSdumpster and ReverseDNS. subbrute was integrated with Sublist3r to increase the possibility of finding more subdomains using bruteforce with an improved wordlist.
Bug#1016995: RFP: sublist3r -- subdomains enumeration tool for penetration testers
Package: wnpp Severity: wishlist * Package name: sublist3r Version : 1.1 Upstream Author : Ahmed Aboul-Ela * URL : https://github.com/aboul3la/Sublist3r * License : GPL-2.0 Programming Lang: Python Description : subdomains enumeration tool for penetration testers Sublist3r is a python tool designed to enumerate subdomains of websites using OSINT. It helps penetration testers and bug hunters collect and gather subdomains for the domain they are targeting. Sublist3r enumerates subdomains using many search engines such as Google, Yahoo, Bing, Baidu and Ask. Sublist3r also enumerates subdomains using Netcraft, Virustotal, ThreatCrowd, DNSdumpster and ReverseDNS. subbrute was integrated with Sublist3r to increase the possibility of finding more subdomains using bruteforce with an improved wordlist.
Bug#1016929: RFP: sd -- intuitive find & replace command-line tool (sed alternative)
Package: wnpp Severity: wishlist * Package name: sd Version : 0.7.6 Upstream Author : Gregory * URL : https://github.com/chmln/sd * License : MIT Programming Lang: Rust Description : intuitive find & replace command-line tool (sed alternative) sd is an intuitive find & replace CLI. sd uses regex syntax that you already know from JavaScript and Python. Find & replace expressions are split up, which makes them easy to read and write. Defaults follow common sense and are tailored for typical daily use.
Bug#1016929: RFP: sd -- intuitive find & replace command-line tool (sed alternative)
Package: wnpp Severity: wishlist * Package name: sd Version : 0.7.6 Upstream Author : Gregory * URL : https://github.com/chmln/sd * License : MIT Programming Lang: Rust Description : intuitive find & replace command-line tool (sed alternative) sd is an intuitive find & replace CLI. sd uses regex syntax that you already know from JavaScript and Python. Find & replace expressions are split up, which makes them easy to read and write. Defaults follow common sense and are tailored for typical daily use.
Bug#976626: Similar package
This seems very similar to the tldr package: https://packages.debian.org/stable/tldr See https://tldr.sh/ for examples. Francois
Bug#976626: Similar package
This seems very similar to the tldr package: https://packages.debian.org/stable/tldr See https://tldr.sh/ for examples. Francois
Bug#848578: Also running into this problem
I can also reproduce this problem with `ts` while `date` works fine: $ date | ts ao� 06 10:33:36 sam 06 aoû 2022 10:33:36 PDT $ date sam 06 aoû 2022 10:35:39 PDT $ echo test | ts ao� 06 10:36:04 test This is what my locale is set to: $ locale LANG=fr_CA.utf8 LANGUAGE= LC_CTYPE="fr_CA.utf8" LC_NUMERIC="fr_CA.utf8" LC_TIME="fr_CA.utf8" LC_COLLATE="fr_CA.utf8" LC_MONETARY="fr_CA.utf8" LC_MESSAGES="fr_CA.utf8" LC_PAPER="fr_CA.utf8" LC_NAME="fr_CA.utf8" LC_ADDRESS="fr_CA.utf8" LC_TELEPHONE="fr_CA.utf8" LC_MEASUREMENT="fr_CA.utf8" LC_IDENTIFICATION="fr_CA.utf8" LC_ALL= $ cat /etc/locale.gen | grep -v '^#' en_CA.UTF-8 UTF-8 en_NZ.UTF-8 UTF-8 fr_CA.UTF-8 UTF-8 Let me know if there's anything else I can provide to help reproduce the problem. Francois -- https://fmarier.org/
Bug#1016605: RFP: dust -- tool to get an instant overview of which directories are using disk space without requiring sort or head
Package: wnpp Severity: wishlist * Package name: dust Version : 0.8.1 Upstream Author : Andy Boot * URL : https://github.com/bootandy/dust * License : Apache-2.0 Programming Lang: Rust Description : tool to get an instant overview of which directories are using disk space without requiring sort or head Dust is meant to give you an instant overview of which directories are using disk space without requiring sort or head. Dust will print a maximum of one 'Did not have permissions message'. Dust will list a slightly-less-than-the-terminal-height number of the biggest subdirectories or files and will smartly recurse down the tree to find the larger ones. There is no need for a '-d' flag or a '-h' flag. The largest subdirectories will be colored. The different colors on the bars: These represent the combined tree hierarchy & disk usage. The shades of grey are used to indicate which parent folder a subfolder belongs to.
Bug#1016605: RFP: dust -- tool to get an instant overview of which directories are using disk space without requiring sort or head
Package: wnpp Severity: wishlist * Package name: dust Version : 0.8.1 Upstream Author : Andy Boot * URL : https://github.com/bootandy/dust * License : Apache-2.0 Programming Lang: Rust Description : tool to get an instant overview of which directories are using disk space without requiring sort or head Dust is meant to give you an instant overview of which directories are using disk space without requiring sort or head. Dust will print a maximum of one 'Did not have permissions message'. Dust will list a slightly-less-than-the-terminal-height number of the biggest subdirectories or files and will smartly recurse down the tree to find the larger ones. There is no need for a '-d' flag or a '-h' flag. The largest subdirectories will be colored. The different colors on the bars: These represent the combined tree hierarchy & disk usage. The shades of grey are used to indicate which parent folder a subfolder belongs to.
Bug#1016389: RFP: choose -- human-friendly and fast alternative to cut and (sometimes) awk
Package: wnpp Severity: wishlist * Package name: choose Version : 1.3.4 Upstream Author : Ryan Geary * URL : https://github.com/theryangeary/choose * License : GPL-3.0 Programming Lang: Rust Description : human-friendly and fast alternative to cut and (sometimes) awk This is choose, a human-friendly and fast alternative to cut and (sometimes) awk. . Features: - terse field selection syntax similar to Python's list slices - negative indexing from end of line - optional start/end index - zero-indexed - reverse ranges - slightly faster than cut for sufficiently long inputs, much faster than awk - regular expression field separators using Rust's regex syntax
Bug#1016389: RFP: choose -- human-friendly and fast alternative to cut and (sometimes) awk
Package: wnpp Severity: wishlist * Package name: choose Version : 1.3.4 Upstream Author : Ryan Geary * URL : https://github.com/theryangeary/choose * License : GPL-3.0 Programming Lang: Rust Description : human-friendly and fast alternative to cut and (sometimes) awk This is choose, a human-friendly and fast alternative to cut and (sometimes) awk. . Features: - terse field selection syntax similar to Python's list slices - negative indexing from end of line - optional start/end index - zero-indexed - reverse ranges - slightly faster than cut for sufficiently long inputs, much faster than awk - regular expression field separators using Rust's regex syntax
Bug#1016361: RFP: dog -- command-line DNS client with colorful output and support for DoH and DoT
Package: wnpp Severity: wishlist * Package name: dog Version : 0.1.0 Upstream Author : Benjamin Sago * URL : https://dns.lookup.dog/ * License : EUPL-1.2 Programming Lang: Rust Description : command-line DNS client with colorful output and support for DoH and DoT dog is a command-line DNS client, like dig. It has colourful output, understands normal command-line argument syntax, supports the DNS-over-TLS and DNS-over-HTTPS protocols, and can emit JSON.
Bug#1016361: RFP: dog -- command-line DNS client with colorful output and support for DoH and DoT
Package: wnpp Severity: wishlist * Package name: dog Version : 0.1.0 Upstream Author : Benjamin Sago * URL : https://dns.lookup.dog/ * License : EUPL-1.2 Programming Lang: Rust Description : command-line DNS client with colorful output and support for DoH and DoT dog is a command-line DNS client, like dig. It has colourful output, understands normal command-line argument syntax, supports the DNS-over-TLS and DNS-over-HTTPS protocols, and can emit JSON.
Bug#1014425: rkhunter: rkunter is unable to find config file for 'syslog' daemon
Hi Tim, > I'm getting these emails Daily: > Warning: The 'syslog' daemon is running, but no configuration file can be > found. I'm not sure why you're getting that message, I've never seen it myself. Are you using rsyslog or syslog-ng? Francois -- https://fmarier.org/
Bug#1011290: tor: Unhandled OpenSSL errors found at ../src/lib/tls/tortls.c:190
Package: tor
Version: 0.4.7.7-1
Severity: normal
Every day when I restart the tor daemon, I see the following in my logs:
May 19 05:05:01 Tor[2928143]: Unhandled OpenSSL errors found at
../src/lib/tls/tortls.c:190:
May 19 05:05:01 Tor[2928143]: TLS error: could not load the shared library
(in DSO support routines:dlfcn_load:---)
May 19 05:05:01 Tor[2928143]: TLS error: could not load the shared library
(in DSO support routines:DSO_load:---)
May 19 05:05:01 Tor[2928143]: TLS error: error loading dso (in configuration
file routines:module_load_dso:---)
May 19 05:05:01 Tor[2928143]: TLS error: unknown module name (in
configuration file routines:module_run:---)
I haven't noticed it causing any problems so far, but I've not really looked
into it.
Francois
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.17.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tor depends on:
ii adduser 3.121
ii libc6 2.33-7
ii libcap2 1:2.44-1
ii libevent-2.1-7 2.1.12-stable-5+b1
ii liblzma55.2.5-2.1
ii libseccomp2 2.5.4-1
ii libssl1.1 1.1.1o-1
ii libsystemd0 250.4-1
ii libzstd11.5.2+dfsg-1
ii lsb-base11.1.0
ii runit-helper2.13.0
ii zlib1g 1:1.2.11.dfsg-4
Versions of packages tor recommends:
ii logrotate3.19.0-2
ii tor-geoipdb 0.4.7.7-1
ii torsocks 2.3.0-3
Versions of packages tor suggests:
ii apparmor-utils 3.0.4-2
pn mixmaster
pn nyx
pn obfs4proxy
pn socat
pn torbrowser-launcher
-- Configuration Files:
/etc/apparmor.d/system_tor changed:
profile system_tor flags=(attach_disconnected) {
#include
#include
#include
}
-- no debconf information
Bug#1010777: RFP: qflipper -- application for updating Flipper Zero firmware
Package: wnpp Severity: wishlist * Package name: qflipper Version : 1.0.2 Upstream Author : Georgii Surkov * URL : https://github.com/flipperdevices/qFlipper * License : GPL-3.0 Programming Lang: C++ Description : application for updating Flipper Zero firmware qFlipper is a graphical desktop application for updating Flipper Zero firmware. . Features: . - Update Flipper's firmware and supplemental data with a press of one button - Repair a broken fimware installation - Stream Flipper's display and control it remotely - Install firmware from a .dfu file - Backup and restore settings, progress and pairing data - Automatic self-update feature - Command line interface
Bug#1010777: RFP: qflipper -- application for updating Flipper Zero firmware
Package: wnpp Severity: wishlist * Package name: qflipper Version : 1.0.2 Upstream Author : Georgii Surkov * URL : https://github.com/flipperdevices/qFlipper * License : GPL-3.0 Programming Lang: C++ Description : application for updating Flipper Zero firmware qFlipper is a graphical desktop application for updating Flipper Zero firmware. . Features: . - Update Flipper's firmware and supplemental data with a press of one button - Repair a broken fimware installation - Stream Flipper's display and control it remotely - Install firmware from a .dfu file - Backup and restore settings, progress and pairing data - Automatic self-update feature - Command line interface
Bug#1007135: uscan: add support for checking version numbers based on HTTP redirects
Package: devscripts Version: 2.22.1 Severity: wishlist The libhdhomerun package has this debian/watch file: version=4 https://www.silicondust.com/support/linux/ https://download.silicondust.com/hdhomerun/libhdhomerun_(\d.*).tgz but due to a recent change upstream, they no longer have the version number in the HTML of the page and instead have a single .tgz link which redirects to the latest version: $ curl -i https://download.silicondust.com/hdhomerun/libhdhomerun.tgz HTTP/1.1 302 Found Date: Fri, 11 Mar 2022 19:23:40 GMT Content-Type: text/html; charset=iso-8859-1 Transfer-Encoding: chunked Connection: keep-alive Location: https://download.silicondust.com/hdhomerun/libhdhomerun_20220303.tgz [...] 302 Found Found The document has moved https://download.silicondust.com/hdhomerun/libhdhomerun_20220303.tgz;>here. Apache/2.4.41 (Ubuntu) Server at download.silicondust.com Port 80 I therefore changed the watch file to this so that it could parse the HTML of the 302 page: version=4 https://download.silicondust.com/hdhomerun/libhdhomerun.tgz https://download.silicondust.com/hdhomerun/libhdhomerun_(\d.*).tgz but it doesn't work because there's no way to tell uscan not to follow the redirect all the way to the tarball. If there was a way to specify something like opts="noredirects" then I could make the watch work again. Alternatively, there could be another mode entirely which looks at the Location header instead. Francois -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_CA.utf8, LC_CTYPE=fr_CA.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages devscripts depends on: ii dpkg-dev 1.21.1 ii fakeroot 1.28-1 ii file 1:5.41-2 ii gnupg 2.2.27-3 ii gpgv 2.2.27-3 ii libc6 2.33-7 ii libfile-dirlist-perl 0.05-2 ii libfile-homedir-perl 1.006-1 ii libfile-touch-perl0.12-1 ii libfile-which-perl1.23-1 ii libipc-run-perl 20200505.0-1 ii libmoo-perl 2.005004-3 ii libwww-perl 6.61-1 ii patchutils0.4.2-1 ii perl 5.34.0-3 ii python3 3.9.8-1 ii sensible-utils0.0.17 ii wdiff 1.2.2-2+b1 Versions of packages devscripts recommends: ii apt 2.4.1 ii curl7.82.0-1 ii dctrl-tools 2.24-3+b1 ii debian-keyring 2021.12.24 ii dput-ng [dput] 1.34 ii dupload 2.9.7 ii equivs 2.3.1 ii libdistro-info-perl 1.1 ii libdpkg-perl1.21.1 ii libencode-locale-perl 1.05-1.1 ii libgit-wrapper-perl 0.048-1 ii libgitlab-api-v4-perl 0.26-1 ii liblist-compare-perl0.55-1 ii liblwp-protocol-https-perl 6.10-1 pn libsoap-lite-perl ii libstring-shellquote-perl 1.04-1 ii libtry-tiny-perl0.31-1 ii liburi-perl 5.10-1 ii licensecheck3.2.14-2 ii lintian 2.114.0 ii man-db 2.10.1-1 ii patch 2.7.6-7 ii pristine-tar1.49 ii python3-apt 2.3.0+b1 ii python3-debian 0.1.43 ii python3-magic 2:0.4.24-2 ii python3-requests2.25.1+dfsg-2 ii python3-unidiff 0.7.3-1 ii python3-xdg 0.27-2 ii strace 5.10-1 ii unzip 6.0-26 ii wget1.21.2-2+b1 ii xz-utils5.2.5-2 Versions of packages devscripts suggests: pn adequate ii at 3.2.5-1 ii autopkgtest 5.20 pn bls-standalone ii bsd-mailx [mailx]8.1.2-0.20180807cvs-2 ii build-essential 12.9 pn check-all-the-things pn cvs-buildpackage ii debhelper13.6 pn diffoscope pn disorderfs ii dose-extra 7.0.0-1+b1 ii duck 0.13.3 ii elpa-devscripts 40.5 pn faketime pn gnuplot pn how-can-i-help ii libauthen-sasl-perl 2.1600-1.1 pn libdbd-pg-perl ii libfile-desktopentry-perl0.22-2 pn libnet-smtps-perl pn libterm-size-perl ii libtimedate-perl 2.3300-2 pn libyaml-syck-perl ii mailutils [mailx]1:3.14-1
