IRC log for #gllug on 20150302

01:55.22*** join/#gllug Leeds (~richardc@n112118156174.netvigator.com)
02:36.41*** join/#gllug dgeary2 (~portlandi@90.194.241.231)
05:49.32*** join/#gllug ChoHag (~mking@195.200.245.105)
08:33.40*** join/#gllug jpds (jpds@ubuntu/member/jpds)
09:10.23morsingLinode doing host Xen reboots without properly informing people, in case anyone here use Linode
09:13.57Leedswhen you say without properly informing... I got an email from them about it this morning
09:49.32*** join/#gllug ess_tee_u (~NULL@unaffiliated/ess-tee-u/x-83456671)
09:54.41morsingLeeds: So did I - I happened to log in to my control pages yesterday, which I almost never do, to see a support ticket about the reboot, but at that point no emails.
09:54.54morsingI've got the email now, thanks
09:58.25Leedsjust got an email from my non-technical boss, who has apparently been wandering around Linode's site, asking me to contact them - and cc: him - asking for details of their security architecture, in particular how they prevent hackers, malware and viruses from getting onto our server, in plain English he can understand
09:59.30Leedsto which the short answer is "no, Linode are not going to waste their time explaining virtual server security in plain English to a poxy customer with a single server"
10:04.31murbLeeds: ah I have  customer with a embedded product that sits on customers networks, the stupid questions we have to deal with from folk are amazing!
10:04.56murbone guy unplugged his box, and then refused to pay for the service, as he wanted to know what version of "bash" was on the device.
10:05.33Leedsheh
10:06.43murbLeeds: linode don't have some worthless security certificates you can point $boss at?
10:07.39murbLeeds: point him at https://www.linode.com/security ?
10:07.54LeedsI suspect he got the same notification that morsing was talking about, and it's set him off on a security ramble
10:08.15murbah the xen hypervisor updates?
10:08.20Leedsunfortunately, he's *started* by cut'n'pasting that page to me in email, and asking for detailed explanations
10:08.23murbthe we'll have to reboot stuff.
10:08.42Leedsright, that one
10:08.57murbLeeds: i'd outsource that in a support message ,then you can come back to him with they refused to answer, or whatever :)
10:09.03murboutsource the misery :)
10:09.28murbthey probably get this question many times and may in fact have a more detailed form reply.
10:09.43Leedshe pays me enough to waste my time on it - meeting with him tomorrow, so I'll try to waffle enough to deflect hmi
10:11.03*** join/#gllug chrisp_ (~wibble@host86-176-79-224.range86-176.btcentralplus.com)
10:12.58murbfair enough :)
10:55.18*** join/#gllug ChoHag (~mking@195.200.245.105)
12:54.59*** join/#gllug dick_turpin (~peter@host217-34-163-30.in-addr.btopenworld.com)
13:26.19murbLeeds: http://xenbits.xen.org/xsa/ # not a lot they can tell you for a few days :), but he can say look they have connections to get early access to vulnerability information.
15:09.29*** join/#gllug gregoriosw_vp (~gregorios@176.126.244.125)
15:53.53*** join/#gllug gregoriosw_vp (~gregorios@176.126.244.125)
17:06.06*** part/#gllug dick_turpin (~peter@host217-34-163-30.in-addr.btopenworld.com)
17:14.09gregjhttp://cl.ly/3L2b0f2n1X00/afghan_immigrants_joke.m4a
17:37.37*** join/#gllug infobot (ibot@rikers.org)
17:37.37*** topic/#gllug is Greater London LUG | Next Meet: Thursday Feb 26th 2015 at the Mulberry Bush pub from 6pm | http://www.gllug.org.uk
17:40.29*** join/#gllug infobot (ibot@rikers.org)
17:40.29*** topic/#gllug is Greater London LUG | Next Meet: Thursday Feb 26th 2015 at the Mulberry Bush pub from 6pm | http://www.gllug.org.uk
17:44.49*** join/#gllug samb1 (~samb1@turbomolecules.com)
19:13.59*** join/#gllug jpds (jpds@ubuntu/member/jpds)
19:25.29*** join/#gllug eye69 (~magnus@yoshi.upcore.net)
19:41.31*** join/#gllug eye69 (~magnus@yoshi.upcore.net)
19:52.53*** join/#gllug jpds (jpds@ubuntu/member/jpds)
23:41.57*** join/#gllug Leeds (~richardc@n112118156174.netvigator.com)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.