I believe this is fixed by:
https://www.sudo.ws/repos/sudo/rev/ebf9a6477d5d
I was able to reproduce the issue by running "make check" and
checking syslog.
- todd
M: AppArmor: enabled
Versions of packages debsigs depends on:
ii binutils 2.35.2-2
ii gnupg 2.2.27-2
ii perl 5.32.1-4+deb11u2
Versions of packages debsigs recommends:
ii debsig-verify 0.23+b2
debsigs suggests no packages.
-- no debconf information
commit 9cd7c457001ec6b10fc77ae370
.
-- no debconf information
commit b2dbd703b1b40d6e616b2246a84ef3b53e578497
Author: Todd C. Miller
Date: Sun Sep 26 19:51:18 2021 -0600
Do not hard-code the path to gpg.
There's no need to do this as perl will use execvp() which searches PATH.
diff --git a/debsigs b/debsigs
index 25b5d44..dc12b02 100644
--- a/debsi
Versions of packages debsigs recommends:
ii debsig-verify 0.23+b2
debsigs suggests no packages.
-- no debconf information
commit 5311625df0d485e16fd674b452c5ecf2b0df160f
Author: Todd C. Miller
Date: Mon Sep 27 08:37:28 2021 -0600
Pass options from -g/--gpgops to gpg when signin
I have implemented verify mode. There is a merge request at
GitLab: https://gitlab.com/debsigs/debsigs/-/merge_requests/5
- todd
This has been fixed in sudo 1.9.0:
https://www.sudo.ws/repos/sudo/rev/b45608f29a02
In sudo 1.9.0, the sudoers grammar in the manual now indicates that
"sudoedit" requires one or more arguments.
- todd
Sudo 1.9.0 includes a fix for this:
www.sudo.ws/repos/sudo/rev/98cb9d98f547
This was fixed in sudo 1.8.20.
- todd
This was fixed in the following commit on 2014-09-17:
https://www.sudo.ws/repos/sudo/rev/588c41d2eab5
On Sat, 26 Oct 2019 07:49:33 -0500, "Serge E. Hallyn" wrote:
> second option sounds nicer but sure is a lot more code. So I'm
> leaning towards the first. Do you mind creating a github issue
> at github.com/shadow-maint/shadow for this, or would you prefer that
> I do it?
I opened a github iss
Package: passwd
Version: 1:4.5-1.1
Severity: normal
Tags: patch
Dear Maintainer,
* What led up to the situation?
If vipw is suspended (e.g. via control-Z) and then resumed, it
often gets immediately suspended. This is easier to reproduce
on a multi-core system.
* What exactly
It looks like the root of the problem is in libgcrypt, see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566351
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
This bug is being tracked at:
http://www.gratisoft.us/bugzilla/show_bug.cgi?id=511
The problem is that ldap_initialize() is modifying the effective
uid. Before the call to ldap_start_tls_s(), the euid is 0, aftter
ldap_start_tls_s(), the effective and saved uids are the same as
the real uid. Bec
This bug was fixed in sudo 1.7.4p1.
- todd
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
This will be fixed in sudo 1.7.8. The problem does not manifest
in the sudo 1.8.x branch.
- todd
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
This was fixed in sudo 1.7.5; sudo now uses the "self pipe trick"
which solves both problems.
- todd
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Sudo does its own ldap.conf parsing and does not use the values
preloaded by the OpenLDAP libraries since that also reads $HOME/.ldaprc
and ./ldaprc. The actual problem is that sudo doesn't recognize
the DEREF setting in ldap.conf. This will be fixed in sudo 1.8.3.
Very old versions of sudo did
A bus error is usually an alignment problem. I can see how this
could happen on 64-bit machines with strict alignment requirements
(such as sparc64).
The following patch fixes the problem for me. It will be part of
a sudo 1.8.2p1 release.
- todd
diff -r d161b82321da plugins/sudoers/pwutil.c
-
In message <[EMAIL PROTECTED]>
so spake Didier Raboud (didier):
> I have a bug that I think is similar to that one.
>
> While using libpam-fprint with this in /etc/pam.d/common-auth
>
> authsufficient pam_fprint.so
> authrequiredpam_unix.so nullok_secure
>
> This is
In message <[EMAIL PROTECTED]>
so spake Justin Pryzby (justinpryzby):
> The following feature request was received from a Debian user.
>
> http://bugs.debian.org./469526
>
> > The sudo() configuration file /etc/sudoers should accept a "mailfrom"
> > variable to specify the "From:" head
21 matches
Mail list logo
