From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id dece347d for ; Fri, 18 Oct 2019 18:33:43 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id EF3929B846; Sat, 19 Oct 2019 04:33:41 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 830AE9B553; Sat, 19 Oct 2019 04:33:18 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id DBFCA9B553; Sat, 19 Oct 2019 04:33:15 +1000 (AEST) Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) by minnie.tuhs.org (Postfix) with ESMTPS id 372C79B552 for ; Sat, 19 Oct 2019 04:33:15 +1000 (AEST) Received: by mail-wr1-f51.google.com with SMTP id l10so6856709wrb.2 for ; Fri, 18 Oct 2019 11:33:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=epD7lqW6qnZqaHV8chfg6cnE+DnRVREyUE/GnfJ9hrI=; b=a3VIpwuBhlV3pS9khDulkVGwWLTksfwz8ERfQsCk0LeL4cDEcSpLKjotF6jgbHyFAO 4t4aPe4r5+nsHttpYBO5ftModSd3D+X8Rs+Sfuj7DiHpMjEFbhidjRBmOVOHqD+PualS b3yiemKsl2ah/HuMRfO5LYnfLN9gynI9IeaTBYI3Me/mSD1S/f9n/XHrjCGIgREVMHSx 5xQUu9ZBPa3ALyCZjrkF8wuYgwd/m6AcfXbRfne/wK1iQGg7Ah3XczE4Lx3kQq5sOR+Q VFuMR8pzxEGJMiQdnFpRlvaS1t1W5Yr1yVyzhRksEaZzotnFHQAKdWybYiGFxFD/9hFL eHLA== X-Gm-Message-State: APjAAAWQBj8hN60obGkom9AOSXYZXiuL42Eett0rUPDUDyDt5Zq03ICU qL+O0yEpbk7nWLvoBT/XpPewiQhLJe7+Z5SCuhELMoIr X-Google-Smtp-Source: APXvYqz2NKHSD0pQYsh0+agIDqFD1bzouGjjcfpjr+iX3Hjy9RzDdxzZgiD+jNKZ8zzPYaMPk/5IcFgjb+yJrkdahDw= X-Received: by 2002:adf:fd08:: with SMTP id e8mr3263145wrr.42.1571423593359; Fri, 18 Oct 2019 11:33:13 -0700 (PDT) MIME-Version: 1.0 References: <1570559927.29337.for-standards-violators@oclsc.org> <2e6e1005-3bbf-5dcc-3fcc-099864c752dc@kilonet.net> <8088e5bd-3530-d3e1-8066-db6ea9389dea@kilonet.net> <3054d652-7320-a99b-df24-67001f974d39@kilonet.net> <8736g06byw.fsf@vuxu.org> <90ffe509-76b5-6629-c55a-7785815fda2e@kilonet.net> In-Reply-To: From: Royce Williams Date: Fri, 18 Oct 2019 10:32:37 -0800 Message-ID: To: tuhs@minnie.tuhs.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [TUHS] Recovered /etc/passwd files X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" On Fri, Oct 18, 2019 at 7:01 AM Royce Williams wro= te: > What original caught my attention was the logic behind enforcing password= quality in passwd.c during a specific era of BSD code, which exited ambigu= ously in a double negative of sorts, where control characters were not disa= llowed during password entry. (I'll try to dig up the source.) Specifically, see the eras in which passwd.c looked something like this: https://github.com/dank101/4.2BSD/blob/708b3890ac0c2f034f2840b5ee9125b3c83a= 05bc/bin/passwd.c#L69-L107 while (c =3D *p++) { if (c >=3D 'a' && c <=3D 'z') flags |=3D 2; else if (c >=3D 'A' && c <=3D 'Z') flags |=3D 4; else if (c >=3D '0' && c <=3D '9') flags |=3D 1; else flags |=3D 8; } if (flags >=3D 7 && pwlen >=3D 4) ok =3D 1; I was intrigued that the "special characters" character set was defined negatively, such that control characters would also count. Royce