buzzmarshall has quit [Quit: Konversation terminated!]
otisolsen70 has joined #beagle
<zmatt>
/cl
rob_w has joined #beagle
dmh has joined #beagle
dmh has quit [Quit: rip]
dmh has joined #beagle
dmh has quit [Quit: rip]
ikarso has joined #beagle
dmh has joined #beagle
dmh has quit [Quit: rip]
dmh has joined #beagle
<jfsimon1981>
Hi g.morning
indigaz7 has joined #beagle
indigaz has quit [Ping timeout: 240 seconds]
indigaz7 is now known as indigaz
Guest24 has joined #beagle
Guest24 has quit [Client Quit]
florian has joined #beagle
starblue1 has quit [Ping timeout: 256 seconds]
starblue1 has joined #beagle
<set_>
jfsimon1981: Hello!
<set_>
It me, set_.
<set_>
I chatted w/ you a while back. Anyway...I am up early and making this bot work w/ updated ideas. BBGW!
<set_>
I am gettin' rusty.
<set_>
on the server online: Internal Server Error. I might need to read up.
<set_>
I am having tech. diff. Boo!
<set_>
Brb!
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
Steve_ has quit [Ping timeout: 240 seconds]
SJFriedl has joined #beagle
SJFriedl has quit [Ping timeout: 240 seconds]
SJFriedl has joined #beagle
SJFriedl has quit [Read error: Connection reset by peer]
SJFriedl has joined #beagle
Shadyman has quit [Remote host closed the connection]
SJFriedl has quit [Ping timeout: 240 seconds]
SJFriedl has joined #beagle
lucascastro has joined #beagle
zjason has quit [Ping timeout: 240 seconds]
lucascastro has quit [Ping timeout: 240 seconds]
hays has quit []
rob_w has quit [Quit: Leaving]
hays has joined #beagle
akaWolf has quit [Ping timeout: 256 seconds]
hays has quit []
hays has joined #beagle
akaWolf has joined #beagle
jkridner has quit [Changing host]
jkridner has joined #beagle
buzzmarshall has joined #beagle
lucascastro has joined #beagle
florian has quit [Quit: Ex-Chat]
<zmatt>
ah nice, local privilege escalation exploit found in policykit... be sure to install your updates on desktop linux systems. (policykit is not typically installed on headless systems, and in particular is not installed on the IoT images)
<zmatt>
"polkit also supports non-Linux operating systems such as Solaris and *BSD, but we have not investigated their exploitability. However, we note that OpenBSD is not exploitable, because its kernel refuses to execve() a program if argc is 0."
<zmatt>
wait, linux _does_ allow argc to be zero? o.O
<zmatt>
why the fuck
m-atoms has joined #beagle
Guest028 has joined #beagle
Guest028 has quit [Client Quit]
vagrantc has joined #beagle
otisolsen70 has quit [Ping timeout: 240 seconds]
m-atoms has quit [Ping timeout: 240 seconds]
m-atoms has joined #beagle
behanw has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
akaWolf has quit [Ping timeout: 256 seconds]
<hnv>
"This vulnerability has been hiding in plain sight for 12+ years"... it gives me goosebumps
paulbarker has quit [Ping timeout: 240 seconds]
vigneshr has quit [Read error: Connection reset by peer]
mgsb has quit [Read error: Connection reset by peer]
vigneshr has joined #beagle
mturquette has quit [Read error: Connection reset by peer]
mturquette has joined #beagle
paulbarker has joined #beagle
mgsb has joined #beagle
pbrobinson has quit [Ping timeout: 240 seconds]
ikarso has joined #beagle
pbrobinson has joined #beagle
akaWolf has joined #beagle
<zmatt>
it's easy for a vulnerability to hide in plain sight when it's due to behaviour that's not widely known
<zmatt>
I wonder how many people were/are aware that argc can be zero in main(), it was news to me
<zmatt>
hopefully this incident will get this weirdness fixed in the kernel
<set_>
Does anyone know any of the side effects of this instance/vulnerability?
<zmatt>
set_: "side effects" ?
<set_>
Right, like...
<zmatt>
in practice it's not a hugely important vulnerability
<set_>
What would happen to a system if this "backdoor" was entered?
<set_>
Oh.
<zmatt>
people who have local access (as normal user) on a system with a vulnerable version of policykit can use it to gain root privileges
<set_>
I am asking b/c I compiled a kernel and then installed it to cross-compile a system to the BBB. But on my main system, the dev. desktop, grub2 took over and created a single instance of OS. Then, my 'puter died out.
<zmatt>
on desktop systems this is generally not that relevant since someone would still first need to have local access
<set_>
Oh...okay. So, my issue is unrelated. Okay. Wozzers about the root privileges.
<set_>
Right.
<zmatt>
and on servers and clouds there's no reason for policykit to be installed at all
<set_>
People would need password access. Oh. That makes sense. No wonder it went undetailed for so long.
<zmatt>
that has absolutely nothing to do with how long it remained undetected
<set_>
Oh. It was not detected. Okay, I thought they just put it "on the back burner."
<zmatt>
???
<set_>
Like, "I will get to this later," type of idea.
<zmatt>
no, you don't put a critical vulnerability that is trivial to fix (once you realize the vulnerability exists) "on the back burner"
<zmatt>
well, not critical... still major
<zmatt>
it may be critical for some systems I guess, but I suspect they'll be pretty rare
<set_>
Okay. Yes sir, that makes sense b/c people w/out sudo access or root privileges should not have it unless granted.
<hnv>
a successful `apt-get changelog policykit-1 | grep CVE-2021-4034` is a good sign right?
<zmatt>
should be yes
<zmatt>
or just check the installed package version
<zmatt>
(the fix is in 0.105-31.1, 0.105-25+deb10u1, and 0.105-18+deb9u2)
<zmatt>
heh, apparently polkit had another local privilege escalation vuln last year (CVE-2021-3560)