From owner-freebsd-bugs@freebsd.org Wed Jan 17 16:32:53 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1182BE79C03 for ; Wed, 17 Jan 2018 16:32:53 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB1D0769E7 for ; Wed, 17 Jan 2018 16:32:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id C81B4175A0 for ; Wed, 17 Jan 2018 16:32:52 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w0HGWqTL067747 for ; Wed, 17 Jan 2018 16:32:52 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w0HGWqJ7067746 for freebsd-bugs@FreeBSD.org; Wed, 17 Jan 2018 16:32:52 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 225265] Lack of monotonic clock prolongs the default sudo 5 minutes password caching as long as suspend lasts Date: Wed, 17 Jan 2018 16:32:52 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: postutdelning@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jan 2018 16:32:53 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225265 Bug ID: 225265 Summary: Lack of monotonic clock prolongs the default sudo 5 minutes password caching as long as suspend lasts Product: Base System Version: 11.1-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: freebsd-bugs@FreeBSD.org Reporter: postutdelning@gmail.com The five minute caching period of the password in sudo is prolonged when the laptop is suspended. For example: In the terminal I issue a command with su= do, I enter my password, one minute later I suspend the laptop, after one hour I resume and still can issue sudo cammands without being asked for my password for the rest of the five minutes that remained from before suspending. Freebsd 11.1-RELEASE 64bit Laptop: Thinkpad x220 Sudo is used with defaults, except group wheel can issue any command. Expected bahaviour: The suspend-time should count for the caching period or maybe even stop the caching of the password immediately. Originally I have reported a bug directly to the sudo bugzilla: https://bugzilla.sudo.ws/show_bug.cgi?id=3D779 But as can be seen in the comments Todd C. Miller answered: "FreeBSD doesn't appear to have a monotonic clock that runs while the machi= ne is suspended. The choice is between using a clock that can run backward, potentially defeating the point of the timestamp file, or one that cannot r= un backward but that is not incremented while suspended. Currently, sudo uses the second option. On most other systems, the monoton= ic clock either runs while suspended or an alternate clock is available which does. I consider this a FreeBSD failing, rather than a sudo one." --=20 You are receiving this mail because: You are the assignee for the bug.=