Stack-register Checking https://undeadly.org/cgi?action=article;sid=20180310000858
Mike Larkin talking about the current status of #vmm https://www.openbsd.org/papers/asiabsdcon2018-vmm-slides.pdf
And double-p (Philipp Buehler) talking about his WIP project for #OpenBSD + #vagrant + #autoinstall. https://github.com/double-p/vagrant-openbsd-provider/blob/master/bhyveCon-WIP.pdf
Mike Larkin at bhyvecon 2018: OpenBSD vmm(4) update https://undeadly.org/cgi?action=article;sid=20180309064801
The birdsite has now turned the unavoidable ads content to almost 100% Japanese, just a few hours after I flew in for AsiaBSDCon. I kinda hope it stays that way after I go back.
The list of accepted talks for @BSDCan 2018 has been announced: https://lists.bsdcan.org/pipermail/bsdcan-announce/2018-March/000168.html full schedule to follow soon.
#OpenBSD has moved 6.3-beta, get ready to make some time for testing! 😎 https://marc.info/?l=openbsd-cvs&m=151982981310046&w=2
"So this is your third attempt. I was going to waste your time by just ignoring this one like the previous ones, but for your own sake, please go play with something else.
I frankly do not see any reasonable reading of my material that would lead a sane person to think that I'd want to have anything to do with promoting Microsoft SharePoint or Microsoft Exchange.
That said, actually reading my stuff might turn out to do you some good. Try it some time."
If you follow me you know my blog.
Meltdown fix committed by guenther@ https://www.undeadly.org/cgi?action=article;sid=20180221201856 #openbsd
Meltdown fix committed by guenther@ https://undeadly.org/cgi?action=article;sid=20180221201856
and of course this from the same bot:
Feb 21 06:18:08 skapet sshd: Failed password for invalid user /* from 18.104.22.168 port 44716 ssh2
Feb 21 04:58:52 skapet sshd: Failed password for invalid user } from 22.214.171.124 port 40174 ssh2
I'm almost at a loss for words:
Feb 20 13:30:15 skapet sshd: Failed password for invalid user n/a from 126.96.36.199 port 34902 ssh2
Kids, this is what happens when you have your bots feed each other garbage.
We are forced to conclude that correctly configuring a mail service is beyond some corporations, see "A Life Lesson in Mishandling SMTP Sender Verification", updated tonight (TL;DR: not fixed yet) https://bsdly.blogspot.com/2018/02/a-life-lesson-in-mishandling-smtp.html
Remember the thing about outlook.com abuse team not actually being available to non-customers? My writeup "A Life Lesson in Mishandling SMTP Sender Verification" has the description and data: https://bsdly.blogspot.com/2018/02/a-life-lesson-in-mishandling-smtp.html