[19:58] <sep332> is it difficult/impossible to update the software packages in the VM image?
[19:58] <sep332> I mean the one on the archive.org website, not after it's booted
[19:59] <aaaaaaaaa> worried about bash?
[19:59] <sep332> yeah
[19:59] <sep332> and maybe other stuff that has security updates
[20:00] <aaaaaaaaa> I think the version of Debian isn't supported anymore, they'd have to change to the LTS
[20:01] <aaaaaaaaa> or they could switch to another distro too, but I'm not sure what that would entail.
[20:01] <sep332> ah. i mean the attack surface is pretty low, but i still feel bad encouraging people to download vulnerable software
[20:01] <aaaaaaaaa> I know I've seen a couple of complaints about the warrior having out of date software.
[20:01] <aaaaaaaaa> such as git
[20:02] <sep332> my Ubuntu 13.10 is not even a year old and it's out of support already sigh.
[20:02] <sep332> i mean there's always LTS but come one
[20:02] <sep332> *on
[20:07] <aaaaaaaaa> Maybe the Ubuntu 14 LTS for the warrior?
[20:09] <phuzion> I might be able to spin a new warrior image this week if you guys want.
[20:10] <phuzion> Unless someone steps in and does it before me.
[20:15] <aaaaaaaaa> I think before one is actually made, all the major devs chip in with their suggestions too.  I know chfoo has had some things he said he wished the warrior had for installed packages.  Maybe others do too.
[20:20] <sep332> now look what you started phuzion :p
[20:21] <aaaaaaaaa> I don't know how big of a hassle it is to make a new one, which is why I recommended that course of action.
[20:22] <phuzion> aaaaaaaaa: It's not TERRIBLY bad, but it's not a "Ok, gimme 40 minutes and it'll be on IA" kind of project either.