From owner-freebsd-security@FreeBSD.ORG Thu Feb 12 10:00:40 2009 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC100106566B for ; Thu, 12 Feb 2009 10:00:40 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 49D368FC16 for ; Thu, 12 Feb 2009 10:00:40 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (pD9E2D969.dip.t-dialin.net [217.226.217.105]) by redbull.bpaserver.net (Postfix) with ESMTP id 542762E13F; Thu, 12 Feb 2009 10:41:24 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 29C6C5E023; Thu, 12 Feb 2009 10:41:20 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1234431680; bh=1TZt39kKAMrp7gjd0zfnXxrlvlb69Rro9 a94nro1n0o=; h=Message-ID:Date:From:To:Cc:Subject:References: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=rOI26FanF/wFHWK7A2fTo7FBUJGwtdEMViuQSRGC0HC1gpebQ9P+WgGzPpgk5RJQU Pegfnw0El1B5bWgj7bpNPw1W6dYW1fpEmrZnDa5o7kujRz7C81/sA0UZgJZ1tRnZ1L5 9RmZQFkb9+/11q/8xrqqsNetwOee9UanYeC4ap6BDd+pGvEk4wo+YfdhnphPoncK43z KtNYPVSRDnvGno59vwitm1VhtrP050aiXyPjutI82l6zHu9CM44djEwkeUVwnnN0NbG ZmR3Mug0Eb5TR+Pgx7anfg1bmhNI2Dg8vBcQi/nZz4YPi8r3DLDQFIpvtkhP4MCQrWU Hqm8WFgAw== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id n1C9fJRj022163; Thu, 12 Feb 2009 10:41:19 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Luna.Leidinger.net (Luna.Leidinger.net [192.168.2.100]) by webmail.leidinger.net (Horde Framework) with HTTP; Thu, 12 Feb 2009 10:41:19 +0100 Message-ID: <20090212104119.45583e6fcp63gcmc@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Thu, 12 Feb 2009 10:41:19 +0100 From: Alexander Leidinger To: Benjamin Lutz References: <200902090957.27318.mail@maxlor.com> <200902111821.53437.mail@maxlor.com> In-Reply-To: <200902111821.53437.mail@maxlor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.3) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 542762E13F.8441D X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-14.9, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Thu, 12 Feb 2009 12:22:45 +0000 Cc: freebsd-security@freebsd.org Subject: Re: OPIE considered insecure X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Feb 2009 10:00:41 -0000 Quoting Benjamin Lutz (from Wed, 11 Feb 2009 =20 18:21:53 +0100): > Hello, > > I've been thinking about what to do about OPIE, and I see the following > possibilities. (Note: this is mainly just a braindump to collect my > thoughts; many details that seem obvious to me are omitted. I'm making it > public because others might be interested in it too.) [...] > - Implement another algorithm: OTPW [...] - Implement something which is similar o freeauth.org, just better =20 implemented and without the "not so good" stuff / design decissions. Short: they need something you know (PIN) + something you have (e.g. =20 token, or mobile phone with java with some fixed key). You then enter =20 your arbitrary long PIN into the phone, and it will give you a time =20 limited key to login (so the time needs to be in sync to some extend). =20 On the machine you login you need the cleartext version of your PIN, =20 the fixed key, and ideally it saves the the PW you just used to login =20 to prevent a relogin with the same PW. If you've seen the remote login =20 tokens from RSA or similar, then you should get the idea what this is =20 about. I wrote down a while ago the algorithm somewhere (based upon my own =20 thoughts how to do it, this was before I've seen freeauth, so it's =20 independent), and also thought about the bells and whistles (some =20 security pitfalls you need to think about). If you are interested in =20 implementing this (ideally with a BSD license for inclusion into the =20 base system) --=20 Oh, yeah, life goes on, long after the thrill of livin' is gone. =09=09-- John Cougar, "Jack and Diane" http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137