From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] Upas/fs and imap4d bug
Date: Sat, 31 Oct 2020 23:54:54 +0000 [thread overview]
Message-ID: <BCD2A8E3-5E6A-4760-8318-B8B26C416ECE@quintile.net> (raw)
i wonder if the GET /<unicode> is a hacker thinking your imap4 server might be 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:
>
> Hello all,
>
> Weeks ago I already got imap4d errors. I then rolled back to the older 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 my /sys/log/imap4d:
>
> 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 expected ver=303, saw (len=8239) type=47 ver=4554 'GET /�����PϚ'
> oat Oct 18 10:31:15 107.6.171.130!35816 tls reports failed: i/o on hungup channel
> oat Oct 19 18:35:05 193.37.255.114!36020 tls reports failed: devtls expected ver=303, saw (len=34) type=1 ver=2 '�%'
> oat Oct 19 18:35:05 193.37.255.114!36324 tls reports failed: no matching cipher suite
> oat Oct 19 18:35:05 193.37.255.114!36342 tls reports failed: no matching cipher 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 expected ver=303, saw (len=12074) type=3 ver=0 ''
> oat Oct 20 01:08:14 87.251.75.21!58124 tls reports failed: devtls expected ver=303, saw (len=11046) type=3 ver=0 ''
> 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 hungup channel
> oat Oct 21 05:38:31 89.248.169.12!39934 tls reports failed: i/o on hungup channel
> upas/fs: user: sirjofri; note: sys: trap: fault write addr=0x0 pc=0x219050
> fs 4591335: suicide: sys: trap: fault write addr=0x0 pc=0x219050
> oat Oct 21 14:01:12 192.241.237.171!54876 tls reports failed: i/o on 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 expected ver=303, saw (len=8239) type=47 ver=4554 'GET /������ޣ'
> oat Oct 22 19:26:52 178.128.165.19!43250 tls reports failed: devtls expected ver=303, saw (len=8239) type=47 ver=4554 'GET /����'
>
> It seems to be some upasfs bug combined with missing cipher and/or bad characters/unicode stuff.
>
> I could try give more data on this issue.
>
> sirjofri
next reply other threads:[~2020-10-31 23:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 23:54 Steve Simon [this message]
2020-10-31 23:54 Steve Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BCD2A8E3-5E6A-4760-8318-B8B26C416ECE@quintile.net \
--to=steve@quintile.net \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).