full-disclosure - Time Expiry Alogorithm??

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <871xelvcf4.fsf@deneb.enyo.de>
From: fw at deneb.enyo.de (Florian Weimer)
Subject: Time Expiry Alogorithm??

* Georgi Guninski:

> would prefer to keep my secrets encrypted with algorithm whose breaking
> requires *provable* average runtime x^4242 or even x^42 instead of 
> *suspected runtime* 2^(x/4).

It depends on the constant factors you omitted, including those in the
lower-order terms. 8-)

AES can be broken with O(1) effort, but the constant is so huge that
it's considered impractical.  IIRC, OpenPGP has an upper bound for key
length, too, so it too can be broken with O(1) effort as well.
Obviously, this isn't particularly meaningful.

For actually breaking algorithms, all that matters is the actual
running time of an attack, and the necessary storage capacitiy.
Big-O?notation and complexity classes are not very helpful.