Authentication-Results: mail-b.sr.ht; dkim=pass header.d=bitfehler.net header.i=@bitfehler.net Received: from mx.bitfehler.net (mx.bitfehler.net [213.239.215.46]) by mail-b.sr.ht (Postfix) with ESMTPS id 1A2E511F053 for <~sircmpwn/sr.ht-discuss@lists.sr.ht>; Thu, 24 Nov 2022 19:55:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bitfehler.net; s=default; t=1669319756; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6SsrwUHirIlMCZ3Ora8UX+jWd9itKL8d3yG0ZLqx5d4=; b=YwAekPp91lgoF8V9vsdYSG2RWlCDtLxMCp2yrEOQ4TFMpoRt803CPLyuATLOrVMmKSY4mx oXEWABMfavlhUkS0VMCLzPkEYRURDGMTqh+o7np++AGZMmeyC2qVjj10w9wKORmb2Hu/8z BajmZCztnfZetkyt7PrvuhN2FaAIApndepFxqKgDPmvTyPyh2NR7QM/LpnF5Wao/b0VhhX Dbib2V/s9Zvn/sAK3ukrF4+CQGPpR81/UhFOZ3qW9F1nxbIMyPzQyDBOFwvG6/frEaZAme jxRadeS1pbf6xhre/lgI6XYFYgqvW/Gk7EYm5VIwfucyCTxw87Dm8O22BhxSbw== Received: from [IPV6:2a02:2454:31d:5f00::bab] (2a02-2454-31d-5f00--bab.dyn6.pyur.net [2a02:2454:31d:5f00::bab]) by mx.bitfehler.net (OpenSMTPD) with ESMTPSA id 63fd6e77 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 24 Nov 2022 19:55:56 +0000 (UTC) Message-ID: Date: Thu, 24 Nov 2022 20:55:55 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: SSH key last used indicator broken? Content-Language: en-US To: =?UTF-8?Q?Adam_M=2e_St=c3=bcck?= , ~sircmpwn/sr.ht-discuss@lists.sr.ht References: <8613258f-4ed5-2a1b-d844-95e5107222f2@adast.xyz> From: Conrad Hoffmann In-Reply-To: <8613258f-4ed5-2a1b-d844-95e5107222f2@adast.xyz> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/24/22 18:45, Adam M. Stück wrote: > I setup my account 4/5 days ago and have been working with git > exclusively through SSH. > > In my meta.sr.ht, the key states Last Used: Never Not entirely sure if this is the case here, but the "last used" date gets updated during the user lookup for an incoming SSH key, which in turn is subject to caching (up to a week). Hence, the date can be off up to a week. I'm just guessing that the key might get cached on creation, too. If the date is still the same in a week, then something is broken for sure :) Drew: given that this date is displayed prominently and can be considered somewhat sensitive, how do you feel about lowering the TTL for this, so that it is somewhat more precise? Cheers, Conrad