07.02.2024 11:06, Helmut Grohne :
..
pam seems difficult:
| extern time_t pam_misc_conv_warn_time; /* time that we should warn user */
| extern time_t pam_misc_conv_die_time; /* cut-off time for input */
Attached is a sketch to make pam compatible.
I had a more complete and *tested* fi
On 2/1/24 10:38, Simon Josefsson wrote:
Hi
I'm exploring how to defend against an attacker who can create valid
signatures for cryptographic private keys (e.g., PGP) that users need to
trust when using an operating system such as Debian. A signature like
that can be used in a targetted attacks
> On 7 Feb 2024, at 18:27, Dima Kogan wrote:
>
> Hi. Thanks for your contribution. I looked at the upstream code a tiny
> bit, and it looks like it might have portability bug, at least on
> big-endian architectures. For instance:
>
>
> https://github.com/missinglinkelectronics/libuio/blob/
Hi. Thanks for your contribution. I looked at the upstream code a tiny
bit, and it looks like it might have portability bug, at least on
big-endian architectures. For instance:
https://github.com/missinglinkelectronics/libuio/blob/6ef3d8d096a641686bfdd112035aa04aa16fe81a/irq.c#L78
This assumes
Hi Andreas,
On Wed, Feb 07, 2024 at 03:47:37PM +0100, Andreas Metzler wrote:
> Package: libselinux1t64
> Replaces: libselinux1
> Provides: libselinux1 (= 3.5-2.1~exp1)
> Breaks: libselinux1 (<< 3.5-2.1~exp1)
>
> Afaiui libselinux1t64 must not fullfill dpkg 1.22.4's dependency on
> "libselinux1 (>
On Tue, Feb 06, 2024 at 06:38:18PM +0100, Paride Legovini wrote:
> Hi Tobias!
>
> On 2024-02-05 10:43, Tobias Heider wrote:
> > On Sat, Jan 26, 2013 at 12:38:07AM +, Stuart Prescott wrote:
> >>
> >> The maintainer for the "nvi" package has indicated that he is unable to
> >> maintain this pack
On 2024-02-06 Helmut Grohne wrote:
> Package: libselinux1t64
[...]> This looks fairly innocuous. We create a minimal sid chroot and install
> libselinux1t64 using apt. What could possibly go wrong? Well, apt thinks
> that it would be a good idea to avoid coinstalling breaking packages and
> first
Package: wnpp
Severity: wishlist
Owner: Kari Pahula
X-Debbugs-Cc: debian-devel@lists.debian.org, debian-scie...@lists.debian.org
* Package name: chuffed
Version : 0.13.1
* URL : https://github.com/chuffed/chuffed
* License : MIT/X
Programming Lang: C++
Descri
Hi Guillem,
On Wed, Feb 07, 2024 at 04:32:45AM +0100, Guillem Jover wrote:
> Yes, I'm not sure I understand either. This is what symbol versioning
> makes possible, even providing different variants for the same symbol,
> see for example glibc or libbsd.
I think symbol versioning is subtly differ
Le Fri, Feb 02, 2024 at 08:23:42PM +0100, Bill Allombert a écrit :
> > I don't see any practical reason why not.
>
> Because packages are not required to use dpkg-buildflags.
And more generally, does this scheme will require to build third-party
packages on 32bit Debian system to set
CFLAGS=D_FIL
Package: wnpp
Severity: wishlist
Owner: Manuel Traut
X-Debbugs-Cc: debian-devel@lists.debian.org, ma...@mecka.net
* Package name: libuio
Version : 0.2.8
Upstream Contact: Benedikt Spranger
* URL : https://github.com/missinglinkelectronics/libuio
* License : LGP
11 matches
Mail list logo
