[01:27] * elky raises an eyebrow at "Dildosan" [02:33] sounds bad [02:34] didn't say anything though === daytime is now known as iceswordYehai [17:20] !badlock [17:22] . !badlock is lol [17:23] heh [17:23] i'll keep an eye out for the USN and link it here, I assume #ubuntu will ask about it [17:24] Yeah, I'm keeping an eye on -hardened too [17:26] when are we opening -release-party [17:27] I'd vote for 14th [17:27] ( one week before release day) [17:47] !badlock is The samba fixes for the badlock vulnerability are currently being tested. For more info see http://badlock.org/ [17:47] I'll remember that, Pici [17:47] https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa/+packages [18:07] actually, -release-party is already open. [18:08] they started the party and you were not invited? :( [19:45] !badlock [19:45] The samba fixes for the badlock vulnerability are currently being tested. For more info see http://badlock.org [19:46] !badlock =~ s,$, and https://lists.ubuntu.com/archives/ubuntu-server/2016-April/007266.html, [19:46] I'll remember that dax [19:46] !badlock [19:46] The samba fixes for the badlock vulnerability are currently being tested. For more info see http://badlock.org and https://lists.ubuntu.com/archives/ubuntu-server/2016-April/007266.html [19:52] heh [19:52] dax: I actually put that on earlier but decided to take it off because I thought it might be confusing for users [19:53] !badlock =~ s#and.*#and https://ubottu.com/y/badlock/# [19:53] I'll remember that Pici [19:59] i don't think that needed shortening really :\ [19:59] I had shorted it earlier, just was putting that back on. [20:05] Unit193: did I miss something, or did that bot get approved somewherE? [20:06] Pici: Kubuntu council approved, not us. [20:06] Unit193: oh. [20:06] Amusingly, it's not exempt from Drone` either. [20:06] Unit193: did the ircc get an email about it? [20:07] It was there before I was, so based on the fact you don't know, then no. [20:07] 'cause if you weren't there I probably would have banned it. [20:07] May I suggest that it login to some account and be given an ubuntu/bot cloak? [20:08] * Pici is feeling a bit weird not being able to action that [20:08] (no pun intended by /ACTION-ing that) [20:09] Amusingly, that nick seems owned by someone else. [20:09] silly [20:13] Unit193: who owns the telegram channel? [20:14] Not precisely sure, one of the Kubuntu council members I'm sure though. [20:14] which telegram chan? [20:15] valorie: just wondering about telegram in #kubuntu right now [20:15] valorie: The actual rooms on Telegram, the other side of the bridge. [20:15] oh, jings, I totally forgot that I should ask about the bot [20:15] called groups on Telegram [20:17] https://github.com/FruitieX/teleirc <--- bot [20:17] hosted and run by Ovidiu-Florin Bogdan [20:17] yes, on the KC [20:18] so, should I email the IRCC? [20:18] if you want that bot you can run that bot. but i would make that official with an own freenode account and a cloak. [20:18] and how can it get an account? [20:18] I guess I'll leave that up to Ovidiu [20:19] and yes, I think one of us owns the group as well, although I'll make sure [20:20] * valorie goes to write a few emails about it [20:20] someone joins with it's nick, registers the account, then gives the bot config the password. if the bot can't identify then that's less than ideal because imposters will have a field day of it [20:20] Based on the config, it does have some form of SASL. [20:21] Also would likely want to put it on the bot wikipage. [20:27] this page? https://wiki.ubuntu.com/IRC/Bots [20:29] ok, sent [20:29] Yeppers! [20:29] once we've got it a freenode account and cloak, I'll write to the ircc [20:30] and get a cloak [20:30] and add it to the page [21:32] https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-2118.html [21:32] this is the main badlock cve iirc [21:42] huh, I thought that was old, and long fixed [21:43] * valorie was wrong [21:43] it was told there was an issue called badlock, but the patches were just published today [21:45] it's taken a month i think [23:00] ahoneybun: Heya, what's up doc? [23:00] woooo, someone reads my emails! \o/ [23:00] wb ahoneybun [23:01] wb? [23:05] * ahoneybun wishes he knew why konversation show all this red text every so oftern [23:06] wb=welcome back [23:07] red text is where someone has mentioned your nick [23:07] valorie: Stop it, you're telling him all sorts of untrue stuff! It's blue when someone says your nick... :( [23:08] lol [23:08] Unit193: nuh uh. it's yellow. [23:08] it's blue when someone uses the /me [23:08] nope, magenta [23:08] valorie: That's green. [23:09] hmmm, you would think we used a plethora of irc clients in here [23:09] Unit193: actually you're right about THAT. :) [23:09] who woulda thunk [23:09] ahoneybun: Also, pls2id to services? [23:09] I think all that is configurable in konvi, but I rarely mess with the defaults [23:10] I set up id to services in konvi and/or the bnc [23:13] * valorie goes off to war on dandelions [23:18] its something from ZNC [23:18] it only happens when I have more then 1 machine connected