Path: csiph.com!news.mixmin.net!aioe.org!.POSTED!not-for-mail
From: Kaz Kylheku <kaz@kylheku.com>
Newsgroups: comp.programming
Subject: Re: Researches in quantum computing seem to progress only extremely slowly
Date: Wed, 2 Sep 2015 21:33:31 +0000 (UTC)
Organization: Aioe.org NNTP Server
Lines: 16
Message-ID: <20150902143209.587@kylheku.com>
References: <ms4114$nal$2@news.albasani.net> <20150901072207.925@kylheku.com> <ms4p4g$5ul$1@news.albasani.net> <20150901111251.317@kylheku.com> <ms6d4b$674$1@news.albasani.net> <2gpeua97b9ibtg9sacbcs0oj4a5hoafedt@4ax.com> <ms7pc7$mcq$1@news.albasani.net>
NNTP-Posting-Host: OGJi3KNpFOhM58UHZwXj0w.user.speranza.aioe.org
X-Complaints-To: abuse@aioe.org
User-Agent: slrn/pre1.0.0-18 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: csiph.com comp.programming:5734

On 2015-09-02, Mok-Kong Shen <mok-kong.shen@t-online.de> wrote:
> Am 02.09.2015 um 23:14 schrieb Robert Wessel:
>> Assuming the time value was microsecond resolution, and the attacker
>> can localize the time when you generated the primes to about a year,
>> he'd have to test no more than about 2**45 possible sets of primes.
>> IOW, this is fundamentally broken.
>
> I only know that there is dependency on time but not how Python
> actually does the seeding.

As a crypto software developer, it's your *job* to know!

The fact that you don't know how Python does the seeding doesn't make
your program secure. The attacker knows.

I must ask again, how fucking dumb are you?