[prev in list] [next in list] [prev in thread] [next in thread] 

List:       racf-l
Subject:    Re: [EXTERNAL] Solar flare bit flip (was Re: Another RACF password question - about the encryption)
From:       "Pommier, Rex" <RPommier () SFGMEMBERS ! COM>
Date:       2023-03-31 14:26:01
Message-ID: de29f50493ed49879a333c93a86f568b () sfgmembers ! com
[Download RAW message or body]

As the OP, I can attest to the fact that I wasn't concerned about a collision, but \
had a coworker who was.  He is now no longer concerned either.  :-)

Rex

-----Original Message-----
From: RACF Discussion List <RACF-L@LISTSERV.UGA.EDU> On Behalf Of Binyamin Dissen
Sent: Friday, March 31, 2023 9:13 AM
To: RACF-L@LISTSERV.UGA.EDU
Subject: [EXTERNAL] Solar flair bit flip (was Re: Another RACF password question - \
about the encryption)

On Fri, 31 Mar 2023 09:39:41 -0400 Phil Smith III <lists@AKPHS.COM> wrote:

> > To pile onto what Mark Jacobs wrote: one of our big-brain crypto guys once \
> > characterized the odds of a collision like this as being lower than the odds of a \
> > random bit-flip due to a solar flare/neutron/whatever causing a problem. So \
> > unless you worry a lot about those, don't even think about this risk.

I vaguely remember that there were several cases of bit flip due to solar flare \
causing failures which was handle by adding error checking bits.

--
Binyamin Dissen <bdissen@dissensoftware.com> \
https://urldefense.com/v3/__http://www.dissensoftware.com__;!!KjMRP1Ixj6eLE0Fj!qKI0l3L \
guz5avffli6vIRsAbbZfn8A87x-qgKTF73gvR0kOM6oKkBCdpzqReMRAMwwdSNz3fOFpywYeRtivE8V3y$ 

Director, Dissen Software, Bar & Grill - Israel

----------------------------------------------------------------------
The information contained in this message is confidential, protected from disclosure \
and may be legally privileged. If the reader of this message is not the intended \
recipient or an employee or agent responsible for delivering this message to the \
intended recipient, you are hereby notified that any disclosure, distribution, \
copying, or any action taken or action omitted in reliance on it, is strictly \
prohibited and may be unlawful. If you have received this communication in error, \
please notify us immediately by replying to this message and destroy the material in \
its entirety, whether in electronic or hard copy format. Thank you.


[prev in list] [next in list] [prev in thread] [next in thread]