andi- changed the topic of #nixos-security to: Vulnerability Roundup Issues: https://github.com/NixOS/nixpkgs/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+Vulnerability+roundup + https://broken.sh | Currently supported releases: unstable (master), 20.09, 20.03 (until 27th of November)
supersandro2000 has quit [Disconnected by services]
supersandro2000 has joined #nixos-security
{^_^} has joined #nixos-security
star_cloud has quit [Ping timeout: 268 seconds]
justanotheruser has quit [Ping timeout: 268 seconds]
star_cloud has joined #nixos-security
rajivr has joined #nixos-security
star_cloud has quit [Ping timeout: 240 seconds]
star_cloud has joined #nixos-security
star_cloud has quit [Excess Flood]
star_cloud has joined #nixos-security
gchristensen has joined #nixos-security
glowpelt has quit [Max SendQ exceeded]
glowpelt has joined #nixos-security
justanotheruser has joined #nixos-security
cole-h has quit [Ping timeout: 264 seconds]
anselmolsm has quit [Remote host closed the connection]
anselmolsm has joined #nixos-security
anselmolsm has quit [Remote host closed the connection]
anselmolsm has joined #nixos-security
anselmolsm_ has joined #nixos-security
anselmolsm has quit [Ping timeout: 268 seconds]
anselmolsm_ has quit [Remote host closed the connection]
anselmolsm_ has joined #nixos-security
star_cloud has quit [Ping timeout: 260 seconds]
star_cloud has joined #nixos-security
red[evilred] has joined #nixos-security
<red[evilred]> huh
<red[evilred]> something just caused systemd to SEGV
<red[evilred]> that's new
<red[evilred]> nice - now I can't reboot:
<red[evilred]> Okay - so this is interesting...
<red[evilred]> someone connected on my high ssh port
<red[evilred]> and apparently caused systemd to crash
__red__ has quit [Ping timeout: 256 seconds]
red[evilred] has quit [Ping timeout: 264 seconds]
bridge[evilred] has quit [Ping timeout: 264 seconds]
bridge[evilred] has joined #nixos-security
__red__ has joined #nixos-security
<__red__> so - I don't know for sure if my matrix server passed this on or not
<__red__> but apparently - someone connected to my sshd server and caused systemd to SEGV
<tilpner> Yes, up until "and apparently caused systemd to crash"
<__red__> Okay -
<__red__> it was my matrix node, so I didn't know if it made it or if anyone replied
<__red__> thank you
<__red__> Gonna assume neutrino unless I see it again
anselmolsm has joined #nixos-security
anselmolsm_ has quit [Ping timeout: 240 seconds]
<__red__> but it's a first for me for sure
<tilpner> Yeah, it looks very odd. So no ECC then?
red[evilred] has joined #nixos-security
<red[evilred]> it's a digital ocean VM
<red[evilred]> so I would have hoped so
<red[evilred]> the timing is what worries me
<tilpner> red[evilred]: Apparently that's a user-mode pagefault, so a bitflip in a pointer might do it. But DO says they use ECC. Unless you have that coredump, maybe run online memcheck?
<red[evilred]> where would systemd put its core files? / ?
<tilpner> I'm not sure what the errors mean, the whole "dumping: No such process" thing is confusing me
<tilpner> ls -t /var/lib/systemd/coredumps
<red[evilred]> yup - got one
<tilpner> Or find / -name \*32640\*
<red[evilred]> core.systemd.0.832d7e879c8d4a5d9ca6a8e0221a8da4.32640.1608218689000000.lz4: LZ4 compressed data (v1.4+)
<red[evilred]> so, uncompress it
<tilpner> Now there's the only the hard part left, making sense of it \o/
<red[evilred]> gdb /path/to/systemd /path/to/coredump
<red[evilred]> and backtrace?
<red[evilred]> (it's been a while)
<red[evilred]> well, looks like I have my morning project :-)
<tilpner> Yeah, something like that
<red[evilred]> umm
<red[evilred]> I think that core file is a trap:
<red[evilred]> core.systemd.0.832d7e879c8d4a5d9ca6a8e0221a8da4.32640.1608218689000000.lz4
<red[evilred]> Dictionary size: 1026 MB (2^30 bytes)
<red[evilred]> Uncompressed size: 8762807027734 MB (9188469141913302864 bytes)
<red[evilred]> need a bigger disk
<red[evilred]> 8.7PB core file if my math is correct
<tilpner> Does coredumpctl debug do anything else?
<red[evilred]> oh - never heard of that
<red[evilred]> ah - that worked
<red[evilred]> yeah - don't know I can do anything with that
<tilpner> thread apply all bt
<tilpner> (in case it has multiple threads. I've never tried that with coredumps)
cole-h has joined #nixos-security
rajivr has quit [Quit: Connection closed for inactivity]
star_cloud has quit [Ping timeout: 268 seconds]
star_cloud has joined #nixos-security
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
cole-h has quit [Quit: Goodbye]
star_cloud has quit [Ping timeout: 240 seconds]
star_cloud has joined #nixos-security