Hello,
from time to time someone asks how secure (a)symmetric crypto really was and
then our math and physics teacher Rob has his performance.
Somebody just pointed me at this:
http://2012.sharcs.org/slides/biryukov.pdf
Of course, they say "No practical impact due to reliance on related
keys"
Dear list,
I am working on a read-only filesystem and I am using following command:
echo "hello" | gpg -e -a -r mar...@example.com
This command fails with the following errors:
gpg: failed to create temporary file `/root/.gnupg/.#lk0x847421':
Read-only file system
gpg: fatal: can't create l
Am So 17.11.2013, 19:02:12 schrieb Martin Vegter:
> gpg: fatal: can't create lock for `/root/.gnupg/trustdb.gpg'
> Could somebody please advice how I can use gpg without temporary files ?
That is a lock file. Try --lock-never
Hauke
--
Crypto für alle: http://www.openpgp-schulungen.de/fuer/unt
| ... Further, getting two
| computers to generate the exact same binary code from the exact same
| source code is a surprisingly difficult challenge. It requires a
| perfect match of everything from compiler versions to C library
| versions right down to identical *clocks* -- becau
On 11/17/2013 11:44 AM, d...@geer.org wrote:
> Well said. Two binaries can be execution identical except for their
> use of registers -- their use of registers being an artefact of the
> compiler.
In fact, it goes even deeper than that: many architectures allow their
processor to dynamically reor
On 18-11-2013 6:21, Robert J. Hansen wrote:
> So even if
> you're running two binaries that are completely identical, the CPU may
> process them quite differently depending on the state of the system.
> This has some extraordinary implications for those who are trying to
> guarantee their CPU is o
