| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Andres Freund <andres(at)anarazel(dot)de>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Security lessons from liblzma |
| Date: | 2024-04-04 21:01:12 |
| Message-ID: | CAKAnmmL2oxKNG7o35fbWjOgN6V65kJZi8BAOKvfygNYqD81_iA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> It would be better if we created the required test files as part of the
> test run. (Why not? Too slow?) Alternatively, I have been thinking
> that maybe we could make the output more reproducible by messing with
> whatever random seed OpenSSL uses. Or maybe use a Python library to
> create the files. Some things to think about.
>
I think this last idea is the way to go. I've hand-crafted GIF images and
PGP messages in the past; surely we have enough combined brain power around
here to craft our own SSL files? It may even be a wheel that someone has
invented already.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2024-04-04 21:01:32 | Re: Security lessons from liblzma |
| Previous Message | Thomas Munro | 2024-04-04 21:00:51 | Re: Streaming read-ready sequential scan code |