Hi Bob,
On Thu, 27 Apr 2023 19:55:42 +0200,
Robert Relyea wrote:
> A good read indeed.
Thanks, I'm happy you enjoyed it :).
> I do wonder about the error message:
>
> because: SHA1 is not considered secure since 1970-01-01T00:00:00Z
>
> I'm not sure where the date came from, but SHA1 wasn't pu
On 4/27/23 20:55, Robert Relyea wrote:
On 4/27/23 3:51 AM, Neal H. Walfield wrote:
Hi all,
A year and a half ago, I began working with Panu on using Sequoia as
RPM's OpenPGP parser. I wrote up our journey from the initial
analysis, to adding the code to RPM, and to getting it into Fedora 38
(y
On 27-04-2023 19:55, Robert Relyea wrote:
|because: SHA1 is not considered secure since 1970-01-01T00:00:00Z|
I'm not sure where the date came from, but SHA1 wasn't published until
1993. 1970-01-01 looks like an epic of some kind.
It's the beginning of Unix time (time of the epoch):
https://e
On 4/27/23 3:51 AM, Neal H. Walfield wrote:
Hi all,
A year and a half ago, I began working with Panu on using Sequoia as
RPM's OpenPGP parser. I wrote up our journey from the initial
analysis, to adding the code to RPM, and to getting it into Fedora 38
(yay!) in a blog post. I'm mentioning it
On Thu, Apr 27, 2023 at 12:52 PM Neal H. Walfield wrote:
> A year and a half ago, I began working with Panu on using Sequoia as
> RPM's OpenPGP parser. I wrote up our journey from the initial
> analysis, to adding the code to RPM, and to getting it into Fedora 38
> (yay!) in a blog post. I'm men
Hi all,
A year and a half ago, I began working with Panu on using Sequoia as
RPM's OpenPGP parser. I wrote up our journey from the initial
analysis, to adding the code to RPM, and to getting it into Fedora 38
(yay!) in a blog post. I'm mentioning it here, as I believe it is of
general interest t
