From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from oat.nine.sirjofri.de ([5.45.105.127]) by ewsd; Fri Oct 23 03:10:11 -0400 2020
Received: from sirjofri.de ([94.222.62.23]) by oat; Fri Oct 23 09:09:59 +0200 2020
Date: Fri, 23 Oct 2020 07:09:59 +0000 (UTC)
From: sirjofri+ml-9front@sirjofri.de
To: 9front@9front.org
Message-ID: <3399f77d-1691-4c2e-a653-66152a023b8a@sirjofri.de>
Subject: Upas/fs and imap4d bug
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Correlation-ID: <3399f77d-1691-4c2e-a653-66152a023b8a@sirjofri.de>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: generic SVG over XML injection reduce/map-scale descriptor interface 

Hello all,

Weeks ago I already got imap4d errors. I then rolled back to the older=20
version (before upas changes to new date lib) and it worked fine again.

Now I updated my system and the bug still occurs. Here is an excerpt from=
=20
my /sys/log/imap4d:

oat Oct 17 20:04:05 185.100.87.246!57794 tls reports failed: i/o on=20
hungup channel
oat Oct 17 20:06:10 185.100.87.246!50254 tls reports failed: devtls=20
expected ver=3D303, saw (len=3D8239) type=3D47 ver=3D4554 'GET /=EF=BF=BD=
=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BDP=CF=9A'
oat Oct 18 10:31:15 107.6.171.130!35816 tls reports failed: i/o on hungup=
=20
channel
oat Oct 19 18:35:05 193.37.255.114!36020 tls reports failed: devtls=20
expected ver=3D303, saw (len=3D34) type=3D1 ver=3D2 '=EF=BF=BD%'
oat Oct 19 18:35:05 193.37.255.114!36324 tls reports failed: no matching=20
cipher suite
oat Oct 19 18:35:05 193.37.255.114!36342 tls reports failed: no matching=20
cipher suite
oat Oct 19 19:41:50 192.241.234.16!37832 tls reports failed: i/o on=20
hungup channel
oat Oct 19 23:32:33 193.142.146.50!64503 tls reports failed: devtls=20
expected ver=3D303, saw (len=3D12074) type=3D3 ver=3D0 ''
oat Oct 20 01:08:14 87.251.75.21!58124 tls reports failed: devtls=20
expected ver=3D303, saw (len=3D11046) type=3D3 ver=3D0 ''
oat Oct 20 09:29:58 164.68.112.178!57559 tls reports failed: i/o on=20
hungup channel
oat Oct 21 05:27:59 183.134.104.149!54207 tls reports failed: i/o on=20
hungup channel
oat Oct 21 05:38:31 89.248.169.12!39934 tls reports failed: i/o on hungup=
=20
channel
upas/fs: user: sirjofri; note: sys: trap: fault write addr=3D0x0=20
pc=3D0x219050
fs 4591335: suicide: sys: trap: fault write addr=3D0x0 pc=3D0x219050
oat Oct 21 14:01:12 192.241.237.171!54876 tls reports failed: i/o on=20
hungup channel
oat Oct 22 09:01:02 142.93.153.132!52684 tls reports failed: Hangup
oat Oct 22 09:01:02 142.93.153.132!53364 tls reports failed: devtls=20
expected ver=3D303, saw (len=3D8239) type=3D47 ver=3D4554 'GET /=EF=BF=BD=
=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=EF=BF=BD=DE=A3'
oat Oct 22 19:26:52 178.128.165.19!43250 tls reports failed: devtls=20
expected ver=3D303, saw (len=3D8239) type=3D47 ver=3D4554 'GET /=EF=BF=BD=
=EF=BF=BD=EF=BF=BD=EF=BF=BD'

It seems to be some upasfs bug combined with missing cipher and/or bad=20
characters/unicode stuff.

I could try give more data on this issue.

sirjofri