Almost a full day of it now,

Nov 15 21:38:19 skapet sshd[13857]: Failed password for invalid user azSXdc from 103.240.79.67 port 37658 ssh2

Somebot got their usernames and passwords lists confused. Fun to be had for log junkies via bsdly.net/~peter/newpart.txt (also bsdly.net/~peter/2020-11-16_bu - usernames (passwords really) only).

Enjoy!

Almost a full day of it now,

Nov 15 21:38:19 skapet sshd[13857]: Failed password for invalid user azSXdc from 103.240.79.67 port 37658 ssh2

Somebot got their usernames and passwords lists confused. Fun to be had for log junkies via bsdly.net/~peter/newpart.txt (also bsdly.net/~peter/2020-11-16_bu - usernames (passwords really) only).

Enjoy!

What I did on my late fall break, 2020 edition:

This morning I remote participated in Sofia, Bulgaria’s OpenFest (openfest.org/2020/en/full-sche). The talk was live and the videos from the event will be available after the conference concludes (soon after, I hope).

But if you like you can take in my recorded dry run here: bsdly.net/~peter/openbsd_6.8_a (826MB, approximately 43 minutes IIRC), with slides to follow along at home.nuug.no/~peter/openbsd_an

NUUG 2020-11-10 18:30 CET Flying rockets with Free Software, Bdale Garbeehttps://www.nuug.no/aktiviteter/20201110-free-software-rockets/ Online meeting *DATE CORRECTED*

NUUG 2020-11-20 18:30 CET: Flying rockets with Free Software, Bdale Garbee nuug.no/aktiviteter/20201110-f - Online meeting

A question for users:

What (custom) value, if any, do you assign to

SPF_FAIL SPF: sender does not match SPF record (fail)
TO_EQ_FM_DOM_SPF_FAIL To domain == From domain and external SPF failed

in your config? Comments on why welcome too.

I've been reading the install instructions for several security products and I keep seeing required steps like

"1.Use SSH to log in to the system as a root user.
2.Modify the SELINUX value in the /etc/sysconfig/selinux file to SELINUX=disabled, and restart the host.
3.Use SSH to log back in to the system as the root user."

How many fireable offenses do you see in that procedure?

The Norwegian Unix User Group (NUUG), continues its series of online events, next up on 2020-10-13: 0G: Escaping the Surveillance Blackhole with Free Mobile Computing

nuug.no/aktiviteter/20201013-m

I've come across a network where not unlike the one in bsdly.blogspot.com/2018/02/a-l do they check for SPF et al in the wrong place, but they also appear to block DNS over TCP (which means null answers on SPF, DKIM et al so the mail gets delivered). Is there any quasi-rational reason behind this, such as a 'ping of death' style tale from the crypt? If there is, I look forward to some campfire time.

Show older
Mastodon

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!