Bug#1094576: openssl-provider-fips: package is not FIPS compliant

Package: openssl-provider-fips Version: 3.4.0-2 Severity: important Bug #1050210 requested addition of the OpenSSL FIPS provider to Debian since a FIPS validation certificate is available: https://csrc.nist.gov/projects/cryptographic-module-validation-program/certificate/4282 There are several is

Bug#962102: ITP: ltunify -- Pair and manage Logitech devices that use the unifying receiver

igned with my PGP key, key ID AF74F895D8467CE9050B2B876F256F687D2DF7BB -- Kind regards, Peter Wu https://lekensteyn.nl

Bug#962102: ITP: ltunify -- Pair and manage Logitech devices that use the unifying receiver

for example. For most users this should not be a problem, if arbitrary code is running as your user, you have more problems to worry about. There have some fixes since the 0.2 release, so if it helps I could tag a new version. -- Kind regards, Peter Wu https://lekensteyn.nl P.S. hoi Geert!

Bug#894476: Workarounds for rcc reproducibility issues due to mtime

recommendations are wrong, feel free to edit the page or discuss it here or on IRC, I aimed at having the peculiarities documented somewhere. -- Kind regards, Peter Wu https://lekensteyn.nl

Bug#874590: [bug #51181] Unexpected "Redirecting output to 'wget-log'."

Follow-up Comment #13, bug #51181 (project wget): I can only reproduce it with fork before execve *and* when using the "timeout" command: #include #include #include int main() { char *args[] = { "timeout", "-k", "26s", "25s", "wget", "-O", "test.html", "http://example.com"

Bug#874590: [bug #51181] Unexpected "Redirecting output to 'wget-log'."

Follow-up Comment #9, bug #51181 (project wget): "&" is a special shell character which causes a program to go to the background. When you execute wget https://example.com/dpp&key it will actually be interpreted as: wget https://example.com/dpp & key which will execute "wget https:

Bug#874590: [bug #51181] Unexpected "Redirecting output to 'wget-log'."

Follow-up Comment #7, bug #51181 (project wget): This was already fixed in wget 1.19.3, are you sure that you are using this (or a newer) version? You really have to provide more details on your environment and the steps to reproduce. See for example the original description. ___

Bug#900440: clang-6.0: clang cmake config files are installed to the wrong folder and have invalid path

nded to fix the reported issue. -- Kind regards, Peter Wu https://lekensteyn.nl

Bug#842292: libnss3: re-enable SSLKEYLOGFILE support

average user). Please consider restoring this feature. -- Kind regards, Peter Wu https://lekensteyn.nl --- debian/rules.orig 2018-03-25 16:24:04.86400 + +++ debian/rules2018-03-25 16:24:08.35600 + @@ -109,6 +109,7 @@ NSPR_INCLUDE_DIR=/usr/include/nspr

Bug#874590: [bug #51181] Unexpected "Redirecting output to 'wget-log'."

Follow-up Comment #4, bug #51181 (project wget): I have investigated the issue, found the issue and attached a patch for it. In the provided test case, file descriptors std{in,out,err} (/proc/self/fd/{0,1,2}) seem to refer to /dev/console. This happens even without chroot. __

Bug#874590: [bug #51181] Unexpected "Redirecting output to 'wget-log'."

Additional Item Attachment, bug #51181 (project wget): File name: 0001-Avoid-redirecting-output-to-file-when-tcgetpgrp-fail.patch Size:1 KB ___ Reply to this item at: __

Bug#778827: dmg2img: convert_char8 out of bounds, segmentation fault

Hey vu1tur, Any chance that the patches can be incorporated? Otherwise I'll fork your project and release a new version (as requested at https://aur.archlinux.org/packages/dmg2img/). Kind regards, Peter On Wed, Dec 16, 2015 at 10:26:18AM +0100, Peter Wu wrote: > Control: tags -1 patch

Bug#778827: status

l look into it" with no further follow-up. Consider reviewing / using the dmg2img fork until the original author replies: https://github.com/Lekensteyn/dmg2img -- Kind regards, Peter Wu https://lekensteyn.nl

Bug#778827: dmg2img: convert_char8 out of bounds, segmentation fault

Control: tags -1 patch On Wed, Dec 16, 2015 at 10:13:53AM +0100, Soeren Sonnenburg wrote: > On Wed, 2015-12-16 at 01:15 +0100, Peter Wu wrote: > > Tags: patch > > > > Please find attached patch, it fixes the crash for me. > > This patch can also be found on m

Bug#778827: dmg2img: convert_char8 out of bounds, segmentation fault

Tags: patch Please find attached patch, it fixes the crash for me. This patch can also be found on my develop branch: https://github.com/Lekensteyn/dmg2img/commit/0b1e72d67d (not an official repo) -- Kind regards, Peter Wu https://lekensteyn.nl >From 0b1e72d67d5acf3466cd9745746e6a8a95a86b5f

Bug#787256: sudo.service:7 Failed to unescape command line, ignoring

-- Kind regards, Peter Wu https://lekensteyn.nl -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#782065: Enable HTTP Gunzip module for nginx

s if you think that the use cases are rare. The attached patch is based on the collab-maint repo and tested on Wheezy-backports (and on a half-upgraded Jessie image as well :-)). -- Kind regards, Peter Wu https://lekensteyn.nl [1]: http://nginx.org/en/docs/http/ngx_http_gunzip_module.html [2]:

Bug#724253: "free(): invalid pointer" crash when using %p in printf

retitle 724253 "free(): invalid pointer" crash when using %p in printf tags 724253 + patch upstream stop Hi, It is not a problem specific to mmap, but rather the handling of "%p" (and "%n") format specifiers handling. I have posted a patch to the upstream ltrace-devel list[1]. Regards, Peter

Bug#724253: "free(): invalid pointer" when printing pointer of mmaped() address

Package: ltrace Version: 0.7.3 When trying to ltrace a process that prints a mmap()ed address, the ltrace program dies, thereby taking the ltraced process down with a SIGILL signal. The output just before crashing does not look correct either: printf("%p\n", 0x77ffax77ffa000 I ob

Bug#696543: [PATCH] etc: make bash completion work for colon values

Package: schroot Version: 1.6.4-1 Tags: patch Patch is based on debian/schroot-1.6.3-1-33-g75634db, but should apply to any version (at least 1.3.2-1). --chroot (and -c) accept values like chroot:foo and session:foo-abc. Standard bash completion treats colons as whitespace, hence we need a way t