On 8/19/24 7:26 PM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
That's indeed quite odd if connecting with openssl s_client works.
I really think you should try out asking exim devs.
reported as https://bugs.exim.org/show_bug.cgi?id=3108
I will
On Mon, 19 Aug 2024 22:31:54 +0200,
Stuart Henderson wrote:
>
> Wait and try again, or try a different mirror. Something is causing
> shearing in some cases i.e. a mixture of files from two different
> snapshots.
>
probably the speed of downloading parts of snapshot is the root cause
> > Nothin
> On 19 Aug 2024, at 23:34, Kirill A. Korinsky wrote:
>
> On Mon, 19 Aug 2024 21:13:57 +0200,
> "Peter N. M. Hansteen" wrote:
>>
>> I did a bit of that and it looks if I read this correctly that the pain point
>> is in the DKIM handling, collection of bts at
>> https://nxdomain.no/~peter/exi
On Mon, 19 Aug 2024 21:13:57 +0200,
"Peter N. M. Hansteen" wrote:
>
> I did a bit of that and it looks if I read this correctly that the pain point
> is in the DKIM handling, collection of bts at
> https://nxdomain.no/~peter/exim-gdb-traces.txt
>
I wonder if this issue can be introduced by
htt
Wait and try again, or try a different mirror. Something is causing
shearing in some cases i.e. a mixture of files from two different snapshots.
(Ran into the same one myself earlier and discovered that autoinstall
doesn't reboot in this situation, instead drops back to
install/upgrade/auto in
On Mon, Aug 19, 2024 at 03:13:40PM +0100, Stuart Henderson wrote:
> On 2024/08/19 15:26, Theo Buehler wrote:
> > On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> > >
> > >
> > > On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> > > >
> > > > So quite odd, the whole thi
Grettings, fellow gentlemen and ladies.
Hereby I want to announce the following issue that I got while running
`torsocks sysupgrade -n` on 1 machine.
Dmesg should be attached below.
I'll summarize the sysupgrade output because the X11 doesn't work right
now so I can't easily copy everything now be
On Mon, Aug 19, 2024 at 03:26:27PM +0200, Theo Buehler wrote:
> On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> >
> >
> > On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> > >
> > > So quite odd, the whole thing.
> > >
> >
> > That's indeed quite odd if connecting w
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> That's indeed quite odd if connecting with openssl s_client works.
> I really think you should try out asking exim devs.
reported as https://bugs.exim.org/show_bug.cgi?id=3108
I will go after stack traces, would you be able to dig o
On Mon, Aug 19, 2024 at 12:51 PM Anon Loli wrote:
> Great! Can't wait to have my desktop usable again! ;)
> Surely one can go without X11, yes indeed.
>
> But surely one has to enjoy the luxury of watching videos, too!
> I could imagine ditching X11 and well all display servers if I could like
>
Great! Can't wait to have my desktop usable again! ;)
Surely one can go without X11, yes indeed.
But surely one has to enjoy the luxury of watching videos, too!
I could imagine ditching X11 and well all display servers if I could like have
everything SAFELY directly streamed to the GPU or somethin
On 8/19/24 4:13 PM, Stuart Henderson wrote:
(If it _does_ stay, perhaps it should switch to using gnutls).
I am not sure this is a good idea. In the past I had quite a lot of
issues when built with gnutls. This was under linux and lots of time
ago, but this might still bring some issues th
On Sat, Aug 17, 2024 at 01:22:17PM +0200, Walter Alejandro Iglesias wrote:
> Today after upgrading to latest snapshot xenodm hanged for a while.
> During the hang I couldn't ssh from another machine. I had to reboot as
> single user, comment out xenodm flag in /etc/rc.conf.local and reboot.
> Usin
On 2024/08/19 15:26, Theo Buehler wrote:
> On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
> >
> >
> > On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> > >
> > > So quite odd, the whole thing.
> > >
> >
> > That's indeed quite odd if connecting with openssl s_client
Dannis 't Hart writes:
> Hello,
> It seems I'm not the only one having some trouble with Xorg/xenocara in
> recent snapshots. Perhaps there is a common cause.
>
> On my laptop (Thinkpad T490S) I use mostly snapshots, troubles are seldom.
> The snapshot from August 13th worked fine, updating to
Hello,
It seems I'm not the only one having some trouble with Xorg/xenocara in recent
snapshots. Perhaps there is a common cause.
On my laptop (Thinkpad T490S) I use mostly snapshots, troubles are seldom. The
snapshot from August 13th worked fine, updating to the snapshot of August 17th
seemed
On 8/19/24 3:26 PM, Theo Buehler wrote:
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
So quite odd, the whole thing.
That's indeed quite odd if connecting with openssl s_client works.
I really think you should t
On Mon, Aug 19, 2024 at 02:57:28PM +0200, Renaud Allard wrote:
>
>
> On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
> >
> > So quite odd, the whole thing.
> >
>
> That's indeed quite odd if connecting with openssl s_client works.
> I really think you should try out asking exim devs
On 8/19/24 12:04 PM, Peter Nicolai Mathias Hansteen wrote:
So quite odd, the whole thing.
That's indeed quite odd if connecting with openssl s_client works.
I really think you should try out asking exim devs.
smime.p7s
Description: S/MIME Cryptographic Signature
> On 19 Aug 2024, at 11:53, Renaud Allard wrote:
>
> Is 134.209.237.226 the IP you tested your "s_client" from? Because I can't
> see any "error handling TLS incoming connection" from that IP. Besides, the
> SSL connection worked in your former mail.
>
No, the digitalocean address is someth
On 8/19/24 11:45 AM, Peter N. M. Hansteen wrote:
And the log has the same errors as before -
2024-08-19 11:41:30 1sfytD-8rO-2Mur Completed
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (fault address:
0xc126c7df)
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (maybe
And the log has the same errors as before -
2024-08-19 11:41:30 1sfytD-8rO-2Mur Completed
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (fault address:
0xc126c7df)
2024-08-19 11:42:17 1sfyu1-Eqn-0YUe SIGSEGV (maybe attempt to write to
immutable memory)
2024-08-19 1
On Mon, Aug 19, 2024 at 11:33:14AM +0200, Renaud Allard wrote:
> > so I reinstalled the locally built older one for now
>
> It would have surprised me if it was rfc1413 requests, but that was
> something to test.
>
> Does it also do the same error if you just connect with "openssl s_client
> -sta
On Mon, Aug 19, 2024 at 11:33:14AM +0200, Renaud Allard wrote:
> > so I reinstalled the locally built older one for now
>
> It would have surprised me if it was rfc1413 requests, but that was
> something to test.
>
> Does it also do the same error if you just connect with "openssl s_client
> -sta
On 8/19/24 11:16 AM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 11:11:40AM +0200, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 10:54:00AM +0200, Renaud Allard wrote:
Your configuration looks indeed very simple without anything unusual.
I added your tls_require_ciphers as this
On Mon, Aug 19, 2024 at 11:11:40AM +0200, Peter N. M. Hansteen wrote:
> On Mon, Aug 19, 2024 at 10:54:00AM +0200, Renaud Allard wrote:
> > Your configuration looks indeed very simple without anything unusual.
> > I added your tls_require_ciphers as this is the only thing that is really
> > differen
On Mon, Aug 19, 2024 at 10:54:00AM +0200, Renaud Allard wrote:
> Your configuration looks indeed very simple without anything unusual.
> I added your tls_require_ciphers as this is the only thing that is really
> different from my test server at connection time, but I still couldn't
> reproduce the
On 8/19/24 10:12 AM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 10:05:01AM +0200, Renaud Allard wrote:
There are no secrets in my config, so I can give you a copy if that helps
at all.
Well, if you have no secrets inside that configuration, it might help if I
can see/try it.
sure
On 8/19/24 10:02 AM, Peter N. M. Hansteen wrote:
On Mon, Aug 19, 2024 at 09:17:03AM +0200, Renaud Allard wrote:
I still cannot reproduce this on latest snapshot from today and package from
repo.
OpenBSD current.arnor.org 7.6 GENERIC.MP#265 amd64
I have noticed that the same kind of error has
On Mon, Aug 19, 2024 at 09:17:03AM +0200, Renaud Allard wrote:
> I still cannot reproduce this on latest snapshot from today and package from
> repo.
> OpenBSD current.arnor.org 7.6 GENERIC.MP#265 amd64
>
> I have noticed that the same kind of error has already been seen in other
> versions of exi
On 8/19/24 8:46 AM, Renaud Allard wrote:
On 8/18/24 4:58 PM, Peter N. M. Hansteen wrote:
On Sun, Aug 18, 2024 at 01:57:11PM +0100, Stuart Henderson wrote:
Is this exim 4.97.1 or 4.98? If it's 4.98 can you try building 4.97.1
('cvs up -D 2024/07/29' in mail/exim) to see whether it was the up
31 matches
Mail list logo
