From owner-freebsd-security@FreeBSD.ORG Sun Jun 24 18:56:12 2012 Return-Path: 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 4D57B106566B for ; Sun, 24 Jun 2012 18:56:12 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id 13BEB8FC20 for ; Sun, 24 Jun 2012 18:56:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:To:Content-Type; bh=wJrmARPjT0zIaIccBX614ttLxBMxeguAh8Fb+a+Ut/Y=; b=Oozc7CuULM1xvHf+JvLcKeITxzCVRVkNN/h3kVLEb/EzClAoyIqXZiD/Bx673xLgla35hU9zHXYwUbMhlSMn8Xv8GMCBcEUv9+jCvhksWrRZbEzmX2xOIILm65erhRvz; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1Siryl-0007aU-8T for freebsd-security@freebsd.org; Sun, 24 Jun 2012 13:56:11 -0500 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpa id 1340564165-94480-94479/5/52; Sun, 24 Jun 2012 18:56:05 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-security@freebsd.org References: Date: Sun, 24 Jun 2012 13:56:04 -0500 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: User-Agent: Opera Mail/12.00 (FreeBSD) X-SA-Score: -1.5 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\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jun 2012 18:56:12 -0000 On Sun, 24 Jun 2012 13:34:45 -0500, Robert Simmons 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?