[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#367058: existing wrong ~/.gnupg/gpg-agent.conf prevents window manager from starting, X still runs



unmerge 367058
reopen 367058
reassign 367058 gnupg-agent
severity 367058 grave
thanks

On Thu, Jun 01, 2006 at 10:50:08PM +0200, Adeodato Simó wrote:
> severity 367058 wishlist
> reassign 367058 x11-common 6.8.2.dfsg.1-7
> close 367058 1:7.0.19
> merge 367058 331553
> thanks

> * Robin Haunschild [Sat, 13 May 2006 11:03:48 +0200]:

> > Package: gnupg
> > Version: 1.4.3-1
> > Severity: critical
> > Tags: security
> > Justification: breaks unrelated software

> Hello Robin,

> > An exsiting file ~/.gnupg/gpg-agent.conf that is syntactically wrong
> > disables the window manager from starting. The display manager and x.org
> > are still running. Even
> > $ startx /usr/bin/startfluxbox -- :1
> > does not start a working Fluxbox.

> This happened because the exit status of /etc/X11/Xsession.d/90gpg-agent
> was non-zero, and the script was executed from /etc/X11/Xsession, which
> runs with set -e, thus aborting the X11 startup process.

> Some months ago, developer Eduard Bloch submitted a wishlist bug against
> x11-common, the package responsible for /etc/X11/Xsession*, asking that
> external scripts under set +e, so that failures to start like the one
> you experienced.

> The bug was fixed in version 7.0.19 of x11-common (see #331553), so I'm
> merging your report with Eduard's, and marking it as closed, since the
> X11 startup process does not fail anymore even if an incorrect
> gpg-agent.conf is present.

Well, I don't agree that the change to x11-common was a correct fix; we have
every reason to demand the same high quality of error handling for Xsession
scripts as we do for other scripts in Debian, which is undermined by this
casual use of set +e as a workaround.  Isn't it reasonable to expect that I
may *want* a failed Xsession script to cause the session to abort?

Either way, there is still a bug in gnupg-agent here; at most, the
x11-common workaround affects the severity of the gnupg-agent bug, but it's
still a gnupg-agent bug.  And it's still a bug that would manifest when
installing gnupg-agent on a sarge system (partial upgrades), so it should
still be fixed.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature


Reply to: