From owner-freebsd-hackers@freebsd.org Fri Nov 1 00:16:44 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D0CE117AFB6 for ; Fri, 1 Nov 2019 00:16:44 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4742mq6m86z41Pm for ; Fri, 1 Nov 2019 00:16:43 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id xA10GM3m037473 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 31 Oct 2019 17:16:23 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id xA10GM8j037472; Thu, 31 Oct 2019 17:16:22 -0700 (PDT) (envelope-from jmg) Date: Thu, 31 Oct 2019 17:16:22 -0700 From: John-Mark Gurney To: Wojciech Puchar Cc: freebsd-hackers@freebsd.org Subject: Re: converting password hashes Message-ID: <20191101001622.GB8521@funkthat.com> Mail-Followup-To: Wojciech Puchar , freebsd-hackers@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Thu, 31 Oct 2019 17:16:23 -0700 (PDT) X-Rspamd-Queue-Id: 4742mq6m86z41Pm X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of jmg@gold.funkthat.com has no SPF policy when checking 208.87.223.18) smtp.mailfrom=jmg@gold.funkthat.com X-Spamd-Result: default: False [-1.24 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.94)[-0.938,0]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; IP_SCORE(-0.51)[ip: (-1.31), ipnet: 208.87.216.0/21(-0.65), asn: 32354(-0.52), country: US(-0.05)]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[funkthat.com]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-1.00)[-0.998,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[jmg@funkthat.com,jmg@gold.funkthat.com]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:32354, ipnet:208.87.216.0/21, country:US]; FROM_NEQ_ENVFROM(0.00)[jmg@funkthat.com,jmg@gold.funkthat.com]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Nov 2019 00:16:44 -0000 Wojciech Puchar wrote this message on Tue, Oct 29, 2019 at 13:13 +0100: > i want to convert accouts from one system where there was mail-only > accounts using dovecot/postfix based system and SQL tables to my system, > where accounts are real unix accounts - that do mail and other things. > > I don't know all people's plaintext passwords, and i don't need to and > want to, but i want new accounts to work with the same passwords > > in SQL tables there are entries like this: > > $1$aab7638c$Cn7BA/oU4mzr0QltXzV7Z0 > > and these works by simple cut and paste to /etc/master.passwd file > > > but there are entries like: > > {PLAIN-MD5}c575f55800a549930b9063b43af04f47 > > that doesn't > > > is there a way to make it work without contacting over hundred people and > telling them what new password they have? There's two ways, one is to write a PAM module or extend crypt(3) to support the plain md5 format from postgresql. The other option is to do what is called on-line conversion. Ask all the affected users to login using their existing password, and as part of the process, you now have their original password, so you jsut re-crypt them w/ a compatible format, and then store and use the new format. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."