[Tools-discuss] Re: Reminder: Action required: Update to IETF Datatracker password requirements starting 8 July
Toerless Eckert <tte@cs.fau.de> Tue, 08 July 2025 19:30 UTC
Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: tools-discuss@mail2.ietf.org
Delivered-To: tools-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E18EB4193DBC; Tue, 8 Jul 2025 12:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.65
X-Spam-Level:
X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.017, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.232, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A_h-Vp9QUZTK; Tue, 8 Jul 2025 12:30:37 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 08F414193C7B; Tue, 8 Jul 2025 12:29:35 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4bcB4r0YxPz1R969; Tue, 8 Jul 2025 21:29:32 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4bcB4q6lg6zl12t; Tue, 8 Jul 2025 21:29:31 +0200 (CEST)
Date: Tue, 08 Jul 2025 21:29:31 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Ken Murchison <murch@fastmail.com>
Message-ID: <aG1xm5QHgijdIHD5@faui48e.informatik.uni-erlangen.de>
References: <a0825f04-1b5a-47d8-b3ad-64b8db97fa79@nostrum.com> <f81ef98e-58de-421b-93a9-0c4c6756f10f@nostrum.com> <aG0236x3_TqDf-7M@faui48e.informatik.uni-erlangen.de> <7669696b-f60d-4e84-92b5-5dea7640908d@fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <7669696b-f60d-4e84-92b5-5dea7640908d@fastmail.com>
Message-ID-Hash: MQ7SWPNLHTGREJ7IIQXCYHP55OUJAT6Z
X-Message-ID-Hash: MQ7SWPNLHTGREJ7IIQXCYHP55OUJAT6Z
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tools-discuss.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Tools Team Discussion <tools-discuss@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tools-discuss] Re: Reminder: Action required: Update to IETF Datatracker password requirements starting 8 July
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/dDwDN0oc4wE1q95x0ZudfYD1dOE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:tools-discuss-owner@ietf.org>
List-Post: <mailto:tools-discuss@ietf.org>
List-Subscribe: <mailto:tools-discuss-join@ietf.org>
List-Unsubscribe: <mailto:tools-discuss-leave@ietf.org>
Ah! nice. Yes, by just accessing the lists anonymously, my MUA also doesn't
keep track of messages i have read. Seems with IMAP that's only done on the
server...
Cheers
Toerless
On Tue, Jul 08, 2025 at 11:32:16AM -0400, Ken Murchison wrote:
> I login to imap.ietf.org with my datatracker credentials so I can subscribe
> to the lists that I care about and have the \Seen flag set on messages that
> I have read. This allows me the same UX on multiple clients.
>
>
> On 7/8/25 11:18 AM, Toerless Eckert wrote:
> > Thanks for the reminder, Robert,...
> >
> > One question: where and when would i need my account/password for IMAP ? (if at all).
> >
> > Is that for folks with @ietf.org email accounts ? Not a participant/wgchair, right ?
> >
> > I am using IMAP only to read lists:
> >
> > imaps://anonymous:<id>@imap.ietf.org/Shared Folders
> >
> > Any other use of imap on ietf that i am missing out on ?
> >
> > Cheers
> > Toerless
> >
> > On Tue, Jul 08, 2025 at 09:53:41AM -0500, Robert Sparks wrote:
> > > These password requirements are now in effect.
> > >
> > > The IETF IMAP service uses your datatracker credentials, remember to change
> > > your password in your IMAP client after changing your datatracker password.
> > >
> > > Also note that mailman3 (postorious) uses a different set of credentials and
> > > is not involved in this change.
> > >
> > > RjS
> > >
> > > On 7/1/25 3:07 PM, Robert Sparks wrote:
> > > > (also available at https://mailarchive.ietf.org/arch/msg/ietf-announce/Xy4PpQHnkZCLXQ4j8J3s2aWeDFc/)
> > > >
> > > > Beginning with a Datatracker update scheduled for 8 July, after the I-D
> > > > submission deadline for IETF 123 Madrid has passed, passwords for the
> > > > IETF Datatracker will be required to have at least 12 characters and be
> > > > sufficiently complex.[1]
> > > >
> > > >
> > > > You should verify your password meets the new requirements using the
> > > > “New password” field on the change password form after logging in:
> > > >
> > > > https://datatracker.ietf.org/accounts/password/
> > > >
> > > > On that form, a complexity bar and text below the new password field
> > > > will provide guidance. When the bar is green, the password will be
> > > > accepted. If your current password does not meet the requirements,
> > > > please go through the password change process to set a new one that does
> > > > meet them. If you are not already logged into Datatracker, this process
> > > > requires confirmation via your primary Datatracker email address.
> > > >
> > > > IMPORTANT: If you are already logged into the Datatracker, do not assume
> > > > that your password will continue to work without verifying it.
> > > >
> > > > Especially if you plan to participate in IETF 123, you should verify
> > > > your password meets these requirements as soon as possible. Datatracker
> > > > login is required to join MeetEcho for meeting sessions, whether you are
> > > > participating in-person or remotely. Logging into the Datatracker well
> > > > before the meeting starts will help ensure you don’t encounter delays
> > > > when joining a meeting session for the first time.
> > > >
> > > > If you are the chair of an IETF working group or IRTF research group,
> > > > please share this update with your group.
> > > >
> > > > This change eases a future migration to an authentication system that
> > > > will allow for federated login, MFA, and passkeys. The new system also
> > > > will allow the authentication process used for various IETF-provided
> > > > services to be more robust.
> > > >
> > > > Another reminder about this change will be sent shortly after the
> > > > Datatracker update is deployed on 8 July.
> > > >
> > > > Robert Sparks
> > > > Senior Director of Information Technology for the IETF LLC
> > > >
> > > > [1] zxcvbn is being used to determine complexity
> > > > (https://github.com/dropbox/zxcvbn)
> > > >
> > > >
> --
> Kenneth Murchison
> Senior Software Developer
> Fastmail US LLC
> IETF MailMaint Chair
--
---
tte@cs.fau.de
- [Tools-discuss] Re: Reminder: Action required: Up… Toerless Eckert
- [Tools-discuss] Re: Reminder: Action required: Up… Ken Murchison
- [Tools-discuss] Re: Reminder: Action required: Up… Robert Sparks
- [Tools-discuss] Re: Reminder: Action required: Up… Toerless Eckert