From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from balrog.mythic-beasts.com ([46.235.227.24]) by ewsd; Sat Oct 31 19:55:05 -0400 2020 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=quintile.net; s=mythic-beasts-k1; h=To:Date:Subject:From; bh=ESNL2Jo/luTT5MCyNZCFWVC9XOiYX1DTyJlcK2k2BYg=; b=Wp5IAXcf2QOHKHWD8mVh6bNplV RdUGqqQCSsw1i06Vf33rnuV+gxlsHDY9nKogbm7vT38Ntc/7WtmmP4mb+pELUj1cfV1i2ANbYSFmL TimyStqKfDJLMcOJZNzD/oBFtJ034k9VZOAQtf/sgyrRSBVxi+MW+NBIR6niFqvdEr+O9yS2vpPa8 fw5fvEbwsk9bIWX6CHFFOQEexXX12f7scBvyoE601LE7ZohtQgOAmct96PJYZzYzi3W9RAQ78vzEW n0yTaACldUWwAtAf3plA/dNY2QkSGZksLoNyWKS0WpaR4aTwyyjfupurrWm4tmHR+MtHH5Rm/uf/A o2aLMj9w==; Received: from 132.198.187.81.in-addr.arpa ([81.187.198.132]:57070 helo=[192.168.1.179]) by balrog.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from ) id 1kZ0hz-0003BI-9b for 9front@9front.org; Sat, 31 Oct 2020 23:54:59 +0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Steve Simon Mime-Version: 1.0 (1.0) Subject: Re: [9front] Upas/fs and imap4d bug Message-Id: Date: Sat, 31 Oct 2020 23:54:54 +0000 To: 9front@9front.org X-Mailer: iPhone Mail (18A8395) X-BlackCat-Spam-Score: 14 X-Spam-Status: No, score=1.4 List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: hypervisor proxy firewall-aware optimizer =EF=BB=BF i wonder if the GET / is a hacker thinking your imap4 server might b= e an http server - more likely a script probing around. i see a lot of this sort of thing. -Steve > On 23 Oct 2020, at 8:10 am, sirjofri+ml-9front@sirjofri.de wrote: >=20 > =EF=BB=BFHello all, >=20 > Weeks ago I already got imap4d errors. I then rolled back to the older ver= sion (before upas changes to new date lib) and it worked fine again. >=20 > Now I updated my system and the bug still occurs. Here is an excerpt from m= y /sys/log/imap4d: >=20 > oat Oct 17 20:04:05 185.100.87.246!57794 tls reports failed: i/o on hungup= channel > oat Oct 17 20:06:10 185.100.87.246!50254 tls reports failed: devtls expect= ed 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 c= hannel > oat Oct 19 18:35:05 193.37.255.114!36020 tls reports failed: devtls expect= ed 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 c= ipher suite > oat Oct 19 18:35:05 193.37.255.114!36342 tls reports failed: no matching c= ipher suite > oat Oct 19 19:41:50 192.241.234.16!37832 tls reports failed: i/o on hungup= channel > oat Oct 19 23:32:33 193.142.146.50!64503 tls reports failed: devtls expect= ed ver=3D303, saw (len=3D12074) type=3D3 ver=3D0 '' > oat Oct 20 01:08:14 87.251.75.21!58124 tls reports failed: devtls 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 hungup= channel > oat Oct 21 05:27:59 183.134.104.149!54207 tls reports failed: i/o on hungu= p channel > oat Oct 21 05:38:31 89.248.169.12!39934 tls reports failed: i/o on hungup c= hannel > upas/fs: user: sirjofri; note: sys: trap: fault write addr=3D0x0 pc=3D0x21= 9050 > 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 hungu= p 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 expect= ed 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 expect= ed ver=3D303, saw (len=3D8239) type=3D47 ver=3D4554 'GET /=EF=BF=BD=EF=BF=BD= =EF=BF=BD=EF=BF=BD' >=20 > It seems to be some upasfs bug combined with missing cipher and/or bad cha= racters/unicode stuff. >=20 > I could try give more data on this issue. >=20 > sirjofri