[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <33bfd925041121001439184281@mail.gmail.com>
From: jacqueline.singh at gmail.com (Jacqueline Singh)
Subject: Re; Time Expiry Algorithm
/me shakes her head at Andrew Farmer.
Okay, now it's just ridiculous to suggest that you wouldn't be able to
implement a time limitation on something encrypted simply because
"clocks can be changed".
What 'clocks' are talking about -- which are you basing it off of?
What if you decided to code into the encryption the use of atomic
clocks, and include more than one or two as a redundancy/security
check?
Someone's really going create a huge conspiracy to change a few of the
world's atomic clocks drastically to be able to crack someone's
encrypted data? :P
-jax
>To: "Gautam R. Singh" <gautam.singh@...il.com>
>Cc: Full-Disclosure Full-Disclosure <full-disclosure@...ts.netsys.com>
>From: Andrew Farmer <andfarm@...novis.com>
>Subject: Re: [Full-Disclosure] Time Expiry Alogorithm??
>Date: Fri, 19 Nov 2004 10:28:20 -0800
Gautam R. Singh <gautam.singh@...il.com> wrote:
> I was just wondering is there any encrytpion alogortim which expires
> with time.
> For example an email message maybe decrypted withing 48 hours of its
> delivery otherwise it become usless or cant be decrypted with the
> orignal key
>>No. Think about it for a moment.
>>(Clocks can be changed.)
Powered by blists - more mailing lists