Your message dated Tue, 20 Dec 2005 13:45:06 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#322445: your bug -- screen C-a x lock feature doesn't work
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Aug 2005 17:14:21 +0000
>From [EMAIL PROTECTED] Wed Aug 10 10:14:21 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c-24-61-206-174.hsd1.ma.comcast.net (osiris.978.org)
[24.61.206.174] (qmailr)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E2u9f-0000ro-00; Wed, 10 Aug 2005 10:14:15 -0700
Received: (qmail 15798 invoked by uid 1000); 10 Aug 2005 17:14:04 -0000
Received: by osiris.978.org (hashcash-sendmail, from uid 1000);
Wed, 10 Aug 2005 13:13:51 -0400
Date: Wed, 10 Aug 2005 13:13:50 -0400
From: Brian Ristuccia <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: screen C-a x lock feature doesn't work
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="azLHFNyN32YCQGCU"
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Hashcash: 1:21:050810:[EMAIL PROTECTED]::YTElcHLUYZlnauqk:000000000000000
0000000000000000000000008hL7
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Package: screen
Version: 3.9.11-5woody1
When pressing C-a x to lock the screen, any password allows an unlock.
--
Brian Ristuccia
[EMAIL PROTECTED]
--azLHFNyN32YCQGCU
Content-Type: text/plain; charset=us-ascii
Content-Description: /etc/pam.d/screen
Content-Disposition: attachment; filename=screen
# $Id: screen.pam,v 1.1 2002/02/06 19:06:42 laz Exp $
#
# This is the PAM configuration file for screen(1)
#
auth required pam_unix.so
--azLHFNyN32YCQGCU--
---------------------------------------
Received: (at 322445-done) by bugs.debian.org; 20 Dec 2005 18:45:09 +0000
>From [EMAIL PROTECTED] Tue Dec 20 10:45:09 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ms-smtp-01.nyroc.rr.com ([24.24.2.55])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EomU1-0005Jg-JS
for [EMAIL PROTECTED]; Tue, 20 Dec 2005 10:45:09 -0800
Received: from andromeda (cpe-69-202-136-66.twcny.res.rr.com [69.202.136.66])
by ms-smtp-01.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id
jBKIj7Fe002582
for <[EMAIL PROTECTED]>; Tue, 20 Dec 2005 13:45:07 -0500 (EST)
Received: from pryzbyj by andromeda with local (Exim 4.60)
(envelope-from <[EMAIL PROTECTED]>)
id 1EomTy-0000Oj-PP
for [EMAIL PROTECTED]; Tue, 20 Dec 2005 13:45:06 -0500
Date: Tue, 20 Dec 2005 13:45:06 -0500
To: [EMAIL PROTECTED]
Subject: Re: Bug#322445: your bug -- screen C-a x lock feature doesn't work
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11
From: Justin Pryzby <[EMAIL PROTECTED]>
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-5.5 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER,
RCVD_IN_SORBS autolearn=no version=2.60-bugs.debian.org_2005_01_02
Version: 4.0.2-4.1
On Tue, Dec 20, 2005 at 01:40:08PM -0500, Brian Ristuccia wrote:
> On Tue, Dec 20, 2005 at 01:23:17PM -0500, Justin Pryzby wrote:
> > Hello Brian,
> >
> > Could you confirm that this bug is fixed in current releases?
> >
>
> Yes. It's fixed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
