0
C Japan
P Osaka
T Osaka
Z
O Scqr Inc.
I
A
M contact@obsd.solutions
U https://obsd.solutions/
B
X
N We are experienced ICT designers/developers and security monks, using OpenBSD as primary servers
for years. [ Company Website ] https://www.scqr.net/;>scqr.net
Hi,
Is it intentional or is there any good reason that OpenBSD 6.9 released May
2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
version v1.2.11 (Jan 2017) is 4 years old.
Background here: https://github.com/Rdatatable/data.table/pull/5049
Best,
Matt
Maintainer of
On 2021-06-23, Diana Eichert wrote:
> On Mon, Jun 21, 2021 at 5:35 AM Stuart Henderson wrote:
>>
> SNIP
>>
>> The location matches this block:
>>
>> >> location "/rainloop/*" {
>> >> fastcgi param SCRIPT_FILENAME "/htdocs/rainloop/index.php"
>> >> fastcgi
Hi list,
We orderd some Dell machines PE R6515 with AMD EPYC 7302P 3GHz but
surprise the CPUs are not available. An alternative suggested by dell
would be the Epyc 7402p 24C/48T 2,8Ghz CPU. But I'm thinking of going
for the Milan CPU right away. Specifically, it would be the AMD Milan
7313P
> I don't know either.
> That is what I am asking.
I'm not going to spend more time investigating a bug fix in zlib made 15
years ago. If that's what your policy is, then we have provided plentiful
pointers for you to do so.
> Yes, you keep saying we should just throw the new code in, and you
Matt Dowle wrote:
> That's right. I don't understand.
> Could you explain it then, or point me to a document that explains what
> your development process is?
> Putting two and two together, it seems that it is 16 years plus a bunch of
> cherry picked bug fixes backported over a very many years.
> So feisty.
Seriously?
On Thu, Jun 24, 2021 at 8:33 PM Theo de Raadt wrote:
> Matt Dowle wrote:
>
> > That's right. I don't understand.
> > Could you explain it then, or point me to a document that explains what
> > your development process is?
> > Putting two and two together, it seems that
Hello Stuart,
Just wanted to preface my response with the fact that I use Emacs for my notes
hence you'll see source blocks later with "#+BEGIN_SRC".
Regarding your previous question:
Do you have:
*mail_plugins = $mail_plugins imap_sieve**
in the "protocol imap { ... }" block?
Answer:
Yes, I
Hi,
Occasionally I see in my query logs that iridium browser contacts an address
called "cache.iridiumbrowser.de".
Jun 25 06:16:31 eta delphinusdnsd[14254]: request on descriptor 24 interface
"cnmac1" from 192.168.177.8 (ttl=64, region=255, tta=1.794ms) for
"cache.iridiumbro
wser.de."
On Fri, Jun 25, 2021 at 06:25:10AM +0200, Peter J. Philipp wrote:
> Hi,
>
> Occasionally I see in my query logs that iridium browser contacts an address
> called "cache.iridiumbrowser.de".
>
> Jun 25 06:16:31 eta delphinusdnsd[14254]: request on descriptor 24 interface
> "cnmac1" from
On Fri, Jun 25, 2021 at 06:48:41AM +0200, Theo Buehler wrote:
[..]
> > I've had some instability issues with iridium in the past and I'm wondering
> > how I can turn this off. I guess they stripped all the google phone home
> > stuff from chromium, and now do their own phone home.
>
> Try
On Thu, Jun 24, 2021 at 11:09:05AM -0600, Matt Dowle wrote:
> Hi,
>
> Is it intentional or is there any good reason that OpenBSD 6.9 released May
> 2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
> version v1.2.11 (Jan 2017) is 4 years old.
>
> Background here:
On Thu, Jun 24, 2021 at 08:04:37PM -0600, Matt Dowle wrote:
>
> > It is NOT 16 years old. You keep saying that. There is a different
> development
> process involved here which has upsides and downsides and which I don't
> expect
> you will understand.
>
> That's right. I don't understand.
>
On Thu, Jun 24, 2021 at 10:41 PM Sebastien Marie wrote:
> On Thu, Jun 24, 2021 at 08:04:37PM -0600, Matt Dowle wrote:
> >
> > > It is NOT 16 years old. You keep saying that. There is a different
> > development
> > process involved here which has upsides and downsides and which I don't
> >
On 2021-06-24, Theo de Raadt wrote:
>> I think the easiest path here is to incorporate the new upstream into a
>> port, unless someone is familiar with zlib and can cherrypick out the
>> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
>
> That is completely impossible.
Theo,
> Instead, we got pages and pages that summarize to "must
update", and doesn't explain what the bug is or what the fix is.
> If only we had an explanation of what is actually wrong and needs fixing
We know it was this news item from 1.2.3.1 (released 16 August 2006)
Matt Dowle wrote:
> Theo,
>
> > Instead, we got pages and pages that summarize to "must
> update", and doesn't explain what the bug is or what the fix is.
>
> > If only we had an explanation of what is actually wrong and needs fixing
>
> We know it was this news item from 1.2.3.1 (released 16
On Sun, June 20, 2021 23:15, Nenhum_de_Nos wrote:
> On Sun, June 20, 2021 20:34, Nenhum_de_Nos wrote:
>> Hi,
>>
>> I updated my rpi 3B to 6.9 and after that I got this messages:
>>
>> axen0: watchdog timeout
>> axen0: usb error on tx: IN_PROGRESS
>> axen0: usb error on tx: TIMEOUT
>>
>> and the
Matt Dowle wrote:
> Hi,
>
> Is it intentional or is there any good reason that OpenBSD 6.9 released May
> 2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
> version v1.2.11 (Jan 2017) is 4 years old.
>
> Background here:
Matt Dowle writes:
> Hi,
>
> Is it intentional or is there any good reason that OpenBSD 6.9 released May
> 2021 uses a 16 year old version of zlib (v1.2.3; July 2005)? The latest
> version v1.2.11 (Jan 2017) is 4 years old.
>
> Background here:
Theo de Raadt writes:
>> I think the easiest path here is to incorporate the new upstream into a
>> port, unless someone is familiar with zlib and can cherrypick out the
>> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
>
> That is completely impossible. It must be in
> I think the easiest path here is to incorporate the new upstream into a
> port, unless someone is familiar with zlib and can cherrypick out the
> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
That is completely impossible. It must be in base. There are 3 copies
in
Dave Voutila wrote:
> Theo de Raadt writes:
>
> > Dave Voutila wrote:
> >
> >> Theo de Raadt writes:
> >>
> >> >> I think the easiest path here is to incorporate the new upstream into a
> >> >> port, unless someone is familiar with zlib and can cherrypick out the
> >> >> commit(s) that resolve
Dave Voutila wrote:
> Theo de Raadt writes:
>
> >> I think the easiest path here is to incorporate the new upstream into a
> >> port, unless someone is familiar with zlib and can cherrypick out the
> >> commit(s) that resolve the issue. (I didn't find zlib in ports already.)
> >
> > That is
Theo de Raadt writes:
> Dave Voutila wrote:
>
>> Theo de Raadt writes:
>>
>> >> I think the easiest path here is to incorporate the new upstream into a
>> >> port, unless someone is familiar with zlib and can cherrypick out the
>> >> commit(s) that resolve the issue. (I didn't find zlib in
On 2021-06-24, Dave Voutila wrote:
> I'm in 100% agreement it sucks and it's something I believe is already
> done for ports that require OpenSSL.
Only for ports which require OpenSSL and don't require a library
which pulls in LibreSSL. For example we are now stuck on updating
Postfix (thanks to
On 23.6.2021. 12:09, Claudio Jeker wrote:
> On Wed, Jun 23, 2021 at 11:40:25AM +0200, Hrvoje Popovski wrote:
>> Hi all,
>>
>> fist of all, thank you for rpki-client, it's so easy to use it and to
>> get the job done.
>> I'm playing with rpki-client and denying ovs invalid statement and I've
>>
Hi,
It's possible backup the system on altroot disk if the disks are create
encrypted?
Thanks
Luciano.
28 matches
Mail list logo
