Same with digital timestamping.
Here in Europe, e-invoicing very slowly seems to be
becoming a (or should I say the?) long-awaited
application for (qualified) electronic signatures.
Since electronic invoices need to be archived in
most countries some vendors apply time-stamps and
recommend to
On Wed, Apr 18, 2007 at 11:29:45PM -0700, Aram Perez wrote:
Is there any danger in using AES128-CBC with a fixed IV of all zeros? This is
being proposed for a standard because that's how SD cards implemented it.
Is the same key ever used to encrypt multiple streams?
This is a protocol
Am Mittwoch, den 18.04.2007, 23:29 -0700 schrieb Aram Perez:
Hi Folks,
Is there any danger in using AES128-CBC with a fixed IV of all zeros? This is
being proposed for a standard because that's how SD cards implemented it.
That depends. What would be a valid attack on a SD-card?
Aram Perez wrote, On 19/4/07 6:29 PM:
Is there any danger in using AES128-CBC with a fixed IV of all zeros?
Here is some discussion about doing this, in the context of PGP doing
just that and why PGP inserts random characters at the begining of the
plaintext.
Stefan Kelm wrote:
Same with digital timestamping.
Here in Europe, e-invoicing very slowly seems to be
becoming a (or should I say the?) long-awaited
application for (qualified) electronic signatures.
Hmmm... last I heard, qualified certificates can only be
issued to individuals, and
On Fri, Apr 20, 2007 at 08:56:32AM +1200, Sidney Markowitz wrote:
Aram Perez wrote, On 19/4/07 6:29 PM:
Is there any danger in using AES128-CBC with a fixed IV of all zeros?
Here is some discussion about doing this, in the context of PGP doing
just that and why PGP inserts random characters
Stefan Kelm wrote:
Here in Europe, e-invoicing very slowly seems to be
becoming a (or should I say the?) long-awaited
application for (qualified) electronic signatures.
Since electronic invoices need to be archived in
most countries some vendors apply time-stamps and
recommend to re-apply
