From owner-freebsd-security@FreeBSD.ORG  Sun Jun 24 19:26:43 2012
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 38B911065673
	for <freebsd-security@freebsd.org>;
	Sun, 24 Jun 2012 19:26:43 +0000 (UTC)
	(envelope-from rsimmons0@gmail.com)
Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com
	[209.85.220.182])
	by mx1.freebsd.org (Postfix) with ESMTP id E5DE88FC14
	for <freebsd-security@freebsd.org>;
	Sun, 24 Jun 2012 19:26:42 +0000 (UTC)
Received: by vcbfy7 with SMTP id fy7so2048052vcb.13
	for <freebsd-security@freebsd.org>;
	Sun, 24 Jun 2012 12:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type; bh=PGLiY/vpEE8gMl3ElMWDr2y4qMgSksWeVtTqlWAFJdg=;
	b=y0y3J/G9/EzpC/wQs0uZBRXPFkKO/x6jAPZrYXyKM9jPLm7NXukE+F7ZyPmLI+JtC5
	3m23jpSTN084T6nRJ5ACZSK/Ceo7QWMCQE2MYGDIhkA08tYtj/FxIu9MVJlm6u1r6zh5
	oU8p9rsPrgfvSBzqZq0vSdye2uKL9jhUELJMHFTIxgblJl/IgCCAiiEFgl9tGBnF0g2u
	mTiEFLrIVPzduaM7T5Nq0d/HVX8Bz8Ijw8D0ospPu/wt0jX0Tdve4Qe+i5WhqmR6TXf6
	uPblrzqoDX8TUhg0bx374MHXUljLzAo7zhVbMj/KRnK6YAy98064LG8vEv3gPi+00gH+
	Skjg==
MIME-Version: 1.0
Received: by 10.220.149.148 with SMTP id t20mr6007959vcv.12.1340566002465;
	Sun, 24 Jun 2012 12:26:42 -0700 (PDT)
Received: by 10.52.16.148 with HTTP; Sun, 24 Jun 2012 12:26:42 -0700 (PDT)
In-Reply-To: <op.wge77quh34t2sn@skeletor.feld.me>
References: <CA+QLa9A4gdgPEn3YBpExTG05e4mqbgxr2kJ16BQ27OSozVmmwQ@mail.gmail.com>
	<op.wge77quh34t2sn@skeletor.feld.me>
Date: Sun, 24 Jun 2012 15:26:42 -0400
Message-ID: <CA+QLa9BA5+Q+wdiUaUPTRWP5RSQXWWF80EB_FLVjpMC2dt_GXg@mail.gmail.com>
From: Robert Simmons <rsimmons0@gmail.com>
To: freebsd-security@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: Hardware potential to duplicate existing host keys... RSA DSA
 ECDSA was Add rc.conf variables...
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Jun 2012 19:26:43 -0000

On Sun, Jun 24, 2012 at 2:56 PM, Mark Felder <feld@feld.me> wrote:
> On Sun, 24 Jun 2012 13:34:45 -0500, Robert Simmons <rsimmons0@gmail.com>
> wrote:
>
>> In light of advanced in processors and GPUs, what is the potential for
>> duplication of RSA, DSA, and ECDSA keys at the current default key
>> lengths (2048, 1024, and 256 respectively)?
>>
>
> I've been able to duplicate keys for years simply using cp(1)
>
> Define "duplicate". Are you asking about some sort of collision? Are you
> asking about brute forcing an encrypted stream and deducing what the private
> key is?

Collisions or brute forcing an encrypted stream, either one.