Hi
The log for the meeting.
/Magnus
[22:06:11] <Zorry> 1.0 project leads
[22:06:18] <klondike> steev: you don't have prometheanfire's number?
[22:06:23] <steev> sadly no
[22:06:26] <klondike> :(
[22:06:28] <Zorry> time to chose the lead
[22:06:30] <steev> i forgot to get his digits
[22:06:38] <klondike> Okey back to topic them
[22:06:50] <Arach> klondike, I need a voice.
[22:07:00] <klondike> Arach you don't :P
[22:07:18] <klondike> But maybe atoth does
[22:07:29] <SwifT> Zorry: you still candidate?
[22:07:37] <Zorry> SwifT: yep
[22:07:43] <SwifT> Zorry has my vote then
[22:07:48] <blueness> That's what i was going to ask, Zorry if you want to do it then i vote for you
[22:08:02] <klondike> Are there other candidates?
[22:08:15] <blueness> only if Zorry didn't want to do it :)
[22:08:41] <blueness> okay any need for a vote?
[22:08:48] <klondike> I'd step out just for the sake of democracy though I'll still vote for Zorry
[22:09:19] <Zorry> okay
[22:09:31] <Zorry> so me one year more
[22:09:40] <klondike> Yay, suffer ;)
[22:09:59] <klondike> We'll send the traditional Microsoft ninjas to your place
[22:10:28] <Zorry> klondike: :)
[22:10:33] <Arach> Micro soft ninjas. So kawaii. ^^
[22:10:55] <Zorry> okay toolchain lead me or some one else?
[22:11:22] <blueness> Zorry, fine
[22:11:24] <SwifT> the toolchain told me he still wants to be lead by you
[22:11:32] <Zorry> k
[22:11:43] <Zorry> kernel lead?
[22:12:03] <blueness> i'll continue if its okay with people
[22:12:04] <Zorry> blueness: okay for you
[22:12:09] <SwifT> blueness++
[22:12:10] <Zorry> +1
[22:12:45] <Zorry> selinux lead SwifT?
[22:12:48] <blueness> yep
[22:12:51] <SwifT> still candidate, yes
[22:12:58] <klondike> yep
[22:13:13] <Zorry> +1
[22:13:28] <Zorry> any more lead we need to discuss?
[22:13:41] <SwifT> there's RSBAC, grsec/pax and integrity
[22:13:50] <klondike> Can I get PR and Media? :P
[22:13:54] <SwifT> at least, that's what hardened.gentoo.org shows
[22:14:01] <Zorry> okay
[22:14:24] <Zorry> RSBAC and grsec/pax blueness?
[22:14:31] <SwifT> +1
[22:14:33] <klondike> +1
[22:14:37] <blueness> in my opinion: rsbac grsec/kernel pax = one project anyhow
[22:14:47] <Zorry> integrity SwifT?
[22:14:50] <blueness> yes
[22:14:53] <SwifT> hope so ;)
[22:15:09] <klondike> Uninformed abstention
[22:15:23] <Zorry> +1
[22:15:32] <Zorry> doc lead?
[22:15:41] <blueness> klondike!
[22:15:48] <SwifT> klondike++
[22:15:49] <klondike> Okey
[22:15:56] <Zorry> +1
[22:16:00] <klondike> I'll keep suffering docs
[22:16:07] <klondike> :P
[22:16:34] <Zorry> all thing done then congrat all then
[22:16:57] <SwifT> like saying congrats to an employee who has to do overtime because things broke
[22:17:06] <SwifT> =)
[22:17:11] <Zorry> next?
[22:17:13] <blueness> Zorry something for a good of the order, next meeting, maybe we should consolidate our "subprojects" for simplicity
[22:17:38] <blueness> because we've grown
[22:17:40] <Zorry> blueness: yep
[22:17:55] <blueness> but we can discuss it next time when i've thought about it
[22:17:58] <blueness> okay next
[22:18:29] <Zorry> 2.0 toolchain
[22:19:15] <Zorry> i still working with the upstream 4.8 patchset and is geting ready for commiting
[22:19:58] <Zorry> if all gos well i hope i can summit it to gcc-patch ml this weekend
[22:20:23] <blueness> nice
[22:20:53] <klondike> YAY!
[22:21:09] -*- klondike excuses himself for the latency since he is tweeting the meeting
[22:21:29] <Zorry> blueness: you have uclibc stuff
[22:21:39] <blueness> Zorry, yes, short update
[22:22:11] <blueness> 1) i have continued maintaining the same arches + abis as last report, but i have not had time to expand to more arches
[22:22:46] <blueness> 2) i'm writing documentation now and i will put it on line. this documentation is not so much a howto as just what is in those tarballs
[22:23:18] <blueness> i wasn't sure how to organize this with the rest of hardened, i was thinking at first a "subproject" but i'm not sure that makes sense
[22:23:59] <Zorry> did you talk to embedded about it?
[22:24:03] <blueness> i will just put up the documentation for now and link it both to hardened and embedded
[22:24:10] <blueness> Zorry, embedded is a bit scattered
[22:24:15] <Zorry> okay that fine
[22:24:40] <blueness> anyhow, i'm going to use the subproject xml because i like it better than the guide xml
[22:24:52] <blueness> and i'll announce it on the gentoo-dev-announce list for visibility
[22:25:01] <blueness> let's worry about what its status is some other time :)
[22:25:14] <blueness> that's all really
[22:25:24] -*- blueness is teaching again
[22:25:31] <Zorry> any one else?
[22:25:35] <Zorry> blueness: :)
[22:25:55] <klondike> blueness: project XML is a superset of GuideXML :/ I can't see why you like it more
[22:26:13] <klondike> blueness: who are you teaching your uni students or another new dev?
[22:26:20] <blueness> klondike, uni students
[22:26:28] <Zorry> next then?
[22:26:34] <SwifT> yup
[22:26:41] <blueness> and we can talk later but i had toruble with the guide xml ... yes nex
[22:26:42] <blueness> next
[22:26:45] <Zorry> 3.0 Kernel
[22:26:52] <blueness> k
[22:27:09] <blueness> nothing much to report but there is one issue that everyone should know about
[22:27:28] <steev> what about the 3.0 kernel?
[22:27:38] <blueness> the interger overflow plugin has caused some people issue, like with net-misc/tor
[22:28:01] <blueness> but pipacs says they're cleaning out those bugs
[22:28:07] <pipacs> it's not so much the userland process that matters
[22:28:21] <Arach> blueness, please, start masking outdated kernels, even those marked stable, as soon as they are no longer supported by grsec upstream.
[22:28:24] <pipacs> but what kernel subsystem the false positive occured
[22:28:44] <pipacs> most of these FPs were in networking code, that's why networking apps triggered them
[22:29:25] <blueness> yep i noticed that
[22:29:52] <blueness> i think Chainsaw hit it in the network code too
[22:30:07] <pipacs> it can happen in torrent, browsers, etc ;)
[22:30:15] <blueness> right
[22:30:21] <pipacs> but the culprit is always a FP in some networking code
[22:30:29] <pipacs> i think we fixed the ones we saw already
[22:30:31] <Arach> blueness, did you notice that people face that FPs because they use outdated h-s?
[22:30:36] <pipacs> but testing will tell for sure
[22:31:02] <blueness> pipacs, i'll keep adding the latest and asking people to test that first, passing bugs your way
[22:31:35] <pipacs> yes, please, unfortunately you'll have to be speedy with this until we can be confident that we found most of the FPs
[22:32:07] <blueness> i think i'm pretty quick, its usually a day or so after spender pushes out the new patches
[22:32:25] <blueness> Arach, i cycle through these pretty quickly
[22:32:46] <pipacs> that's good enough i think
[22:32:49] <blueness> only if i hit a kernel which seems pretty cstable do i stabilize it
[22:32:51] <pipacs> 0-day as it were ;P
[22:32:59] <blueness> pipacs, yea ~0 day
[22:33:25] <blueness> but our users should for now consider that plugin in flux
[22:33:36] <blueness> okay i think we've covered that issue
[22:34:12] <blueness> i have nothing more for kernel
[22:34:17] <Arach> blueness, there are h-s-3.4.x that are still "stable", and also 3.2.{11,20,23}. That's just misleading.
[22:34:33] <blueness> Arach, why?
[22:34:43] <blueness> 3.2.11 should go
[22:35:08] <Arach> blueness, because those h-s may and do contain bugs that are already fixed in the latest grsec.
[22:35:39] <blueness> Arach, and the ones just added also have bugs, the difference is that the older ones have bugs we know and the newer ones have bugs we don't
[22:35:42] <Arach> blueness, should I also remind they contain vulnerabilities?
[22:35:54] <blueness> so do the newer ones, that are yet unknown
[22:36:05] <blueness> and the vulns may be in features not even enabled
[22:36:18] <Arach> Unknown is the key word here.
[22:36:34] <blueness> yeah which would you rahter, bugs you can't work around or bugs you can?
[22:37:05] <blueness> Arach, i know this argument, and it is good to expose it to others here, but this is not the time to engage it in depth
[22:37:21] <Arach> blueness, that "can vs can't" doesn't make a difference as long as you don't list the known bugs and their workarounds.
[22:37:57] <blueness> echo "sys-kernel/hardened-sources ~amd64" >> /etc/portage/packages.accept_keywords
[22:38:15] <blueness> Arach, i'm not dismissing you but like i saide, we need to move on to get to other agenda items
[22:38:42] <Arach> k
[22:38:53] <Zorry> next?
[22:38:56] <blueness> yes
[22:39:05] <Zorry> 4.0 Selinux
[22:39:27] <SwifT> okay, I almost finished a huge workload I had on getting swig-2 to work with setools
[22:39:53] <SwifT> for some reason, most of my work is fixing stuff that shouldn't need to be broken in the first place, first python3, now swig :p
[22:40:22] <SwifT> anyway, the fix presented is also sent upstream and the few tests I had against the swig-generated code seem to work well, so I'll push it to hardened-dev soon (tomorrow most likely)
[22:40:49] <SwifT> I also added some blurbs to selinux' docs about adding your own roles to the system
[22:41:13] <SwifT> that's needed since the recent policies now support "named init scripts" as well (which we didn't support previously)
[22:41:42] <SwifT> named init scripts require specific administrative rights. I'm always assigning them to the sysadm_r role too (for compatibility sake) but users can now also create specific roles for specific services
[22:42:21] <SwifT> however, that also means that users that already have selinux on their system will need to add the system_r role to the sysadmin users as well
[22:42:38] <SwifT> i've documented that in the handbook as well as at the end (in the changes chapter)
[22:43:21] <klondike> xD
[22:43:26] <SwifT> I hope to push out rev 4 of the policies tomorrow to the hardened-dev overlay
[22:43:43] <klondike> :D
[22:43:47] <SwifT> that's about it for selinux
[22:44:30] <Zorry> any one else?
[22:44:44] <blueness> jsut a quick question
[22:45:08] <blueness> what is that status of python3 + all the selinux stuff is that moving forward?
[22:45:13] <blueness> i mean in terms of compat?
[22:45:28] <SwifT> everything we have, except the selinux-code in portage, should be python2 & python3 compatible
[22:45:32] <blueness> i remember hitting a lot of python2 vs python3 issues with twitch153's stuff
[22:46:05] <SwifT> yes, twitch153 started with a refpolicy release that didn't have p3 support in it, but since them they accepted our patches for it
[22:46:14] <blueness> k
[22:46:20] <blueness> that's what i was referring to
[22:46:25] <SwifT> also userspace has seen the patches, but I'm afraid their next stable release won't be fully p3-compatible yet, so i'll need to forwardport patches there as well
[22:46:49] <SwifT> for portage, I still have to start looking at the problems
[22:47:04] <SwifT> seems like a type issue with byte/string, which is a pita to deal with
[22:47:11] <blueness> yeah
[22:47:26] <blueness> easy conceptually but those issues are like everywhere
[22:47:40] <SwifT> portage calls the swig'ified interfaces that were broken with swig-2 so I had to deal with that first
[22:47:49] <blueness> k
[22:47:51] <SwifT> ended up with a patch almost 300k... manually handled :/
[22:48:01] <blueness> fun
[22:48:08] <blueness> oh i mean ... not fun
[22:48:13] <SwifT> yes, i seriously hope it's a good patch and upstream applies it
[22:48:15] <blueness> :)
[22:48:17] <Bunta> Hi guys, is it normal to get this multiples times when compiling hardened-sources :
[22:48:20] <Bunta> /usr/src/linux-3.4.5-hardened/arch/x86/include/asm/uaccess_64.h:183:24: attention : call to ‘copy_to_user_overflow’ declared with attribute warning: copy_to_user() buffer size is not provably correct
[22:48:26] <blueness> Bunta, not now
[22:48:30] <blueness> we've got a meeting going
[22:48:38] <pipacs> bunta, privmsg me
[22:48:52] <blueness> hahaha i was jsut going to say we've got the master right here!
[22:48:53] <SwifT> any other selinux questions?
[22:49:10] <klondike> Hum
[22:49:23] <SwifT> ok, next topic then
[22:49:39] <Zorry> 5.0 Gesec/PaX
[22:49:45] <blueness> k
[22:49:55] <blueness> big stuff here -> https://bugs.gentoo.org/show_bug.cgi?id=427888
[22:50:14] <blueness> i've started the move towards integrating xattr pax markings fully into gentoo
[22:50:18] <blueness> so i opened the tracker
[22:50:26] <blueness> the issues are:
[22:50:35] <blueness> 1) getting rid of chpax
[22:50:59] <blueness> 2) finally fixing up portage and tar in particular to store xattr
[22:51:10] <Bunta> blueness: woops sorry just arrived and didnt see...
[22:51:27] <blueness> 3) getting the userland utilities all ready ... that's pretty much done
[22:51:52] <blueness> 4) getting pax-util.eclass ready ... that will be done once all the userland stuff is stable, which should be soon
[22:52:06] <blueness> 5) here's the contraversial one we should discuss
[22:52:20] <blueness> vapier wants to drop PT_PAX support from the toolchain
[22:52:36] <blueness> that means pax markings will only be xattr in gentoo in the long run
[22:52:49] <blueness> this makes me nervous because of backward compat
[22:53:06] <blueness> we can document a proper migration, its easy
[22:53:23] <blueness> but what do people thing about dropping PT_PAX phdr from all gentoo elfs?!
[22:53:30] [mquin] [Global Notice] Services are back now but may be a little slow while everthing settles down. Thank you for your patience, and for flying freenode!
[22:54:03] <blueness> Zorry, comment ^^^
[22:54:04] <SwifT> what does "dropping support from toolchain mean"? is it a separate patchset we (gentoo) is maintaining?
[22:54:32] <blueness> SwifT, okay, currently when our toolchian builds an elf binary we add an extra program header to the elf
[22:54:49] <Zorry> blueness: i think it be trubel in the begining but in the long run is okay
[22:54:49] <blueness> program headers don't contain code or data, they just say something about how the binary should run
[22:55:11] <blueness> so GNU_STACK says what permissions to add to stack, eg will the stack be exe
[22:55:21] <klondike> I have to strongly opose on that one
[22:55:23] <Zorry> blueness: soner or later some thing will brake the elf
[22:55:25] <blueness> PT_PAX isn't in any other distro that i know of currently
[22:55:28] <SwifT> blueness: yes, but the "our toolchain" is something we (hardened) maintain, isn't it?
[22:55:35] <blueness> PT_PAX is where we keep our pax flags
[22:55:51] <klondike> There are still filesystems not supporting xattrs which need PT_PAX markings
[22:55:57] <pipacs> pt_pax flags should be kept if possible
[22:56:04] <shadowdaemon> ^
[22:56:05] <blueness> Zorry, yeah i figured that myself, it maybe be bad, especially for python which now needs paxctl -m
[22:56:14] <pipacs> i think his main objection is the maintenance burden on the binutils tets
[22:56:16] <pipacs> tests even
[22:56:17] <Flameeyes> blueness: sorry if I intrude — what about the hurdle with tmpfs not supporting pax marking?
[22:56:18] <blueness> SwifT, any gentoo toolchain
[22:56:30] <blueness> Flameeyes, tmpfs supports xattrs
[22:56:32] <blueness> as of 3.0
[22:56:35] <Flameeyes> yes
[22:56:37] <blueness> we'll have to drop < 3.0
[22:56:38] <Flameeyes> but only a subset
[22:56:46] <Flameeyes> even 3.4 does not let you use pt pax marking on tmpfs
[22:56:58] <blueness> Flameeyes, user xattr yes
[22:57:02] <Flameeyes> (I know because I tried)
[22:57:11] <SwifT> oh, it's in user xattr?
[22:57:17] <pipacs> yes
[22:57:23] <blueness> SwifT, yes its under the user space of xattrs
[22:57:25] <Flameeyes> user xattrs no, it supports security labels (selinux, xattr-based caps), not pt pax afaict
[22:57:25] -*- SwifT needs to read up on the pax xattr
[22:57:59] <blueness> Flameeyes, that's not what i remember but i'll test right after the meeting because that 's a definite blocker
[22:58:07] <SwifT> too bad, I just had the security.* governed through IMA :p
[22:58:42] <Flameeyes> > Currently this enables support for the trusted.* and security.* namespaces.
[22:58:43] <blueness> we didn't go with security.* because we want the average user to set their own flags on their own binaries the way paxctl does
[22:58:47] <SwifT> we'll definitely need to support PT_PAX for a while unless xattr support can be guaranteed everywhere
[22:59:02] <SwifT> ya, understood
[22:59:11] <blueness> Flameeyes, then i have my work cut out for me! looks like a kernel patch i'll have to write for the hardened kernels
[22:59:33] <Flameeyes> blueness: fine, would be nice to have it on non-hardened as well, but okay
[22:59:39] <blueness> Flameeyes, thanks i'll test and add that as a blocker to the tracker
[23:00:00] <blueness> Flameeyes, you mean the patch for tmpfs? i can convince mpagano or push it upstream
[23:00:10] <Flameeyes> yeah that's what I meant, good :)
[23:00:11] <blueness> i understand that stuff well enough i think
[23:00:28] <blueness> heh i started by trying to create an entirely new xattr namespace
[23:01:00] <blueness> this is long term, so we're not going to do anything that will break people systems, DON'T PANIC!
[23:01:02] <blueness> :)
[23:01:14] <klondike> NOOOOOOOOOO my system is a broke
[23:01:16] <klondike> :P
[23:01:23] -*- blueness has been waiting to quote "the hitchhicker's guide" all day
[23:01:58] <blueness> okay guys, please look over the tracker, add anything or open any new bugs we need to
[23:02:21] <blueness> any questions/flamings?
[23:02:46] <SwifT> nope
[23:02:59] <klondike> Nope
[23:03:03] <blueness> i have nothing more for grsec/pax then
[23:03:10] <Zorry> next?
[23:03:13] <Arach> blueness, does squashfs supports user xattrs?
[23:03:16] <blueness> yes
[23:03:38] <Zorry> 6.0 Profiles
[23:03:39] <pipacs> pax forcibly enables xattr support on filesystems btw
[23:03:47] <blueness> but Flameeyes has made me all paranoid now, so i'm going to go back and make sure it does *user* namespace
[23:03:51] <SwifT> nothing from my side on profiles
[23:04:28] <Mepho> hi guys, any idea when will this patch relating tar and acl,xattr, caps and stuff make it into the tree?
[23:04:29] <Zorry> nothing from my side to
[23:04:48] <blueness> nothing new for me, but i just wanted to add, given what i said above about uclibc, that i'm housing the hardened-uclibc profiles under hardened rather than hardened underd uclibc
[23:05:04] <blueness> Mepho, its hitting the tree now
[23:05:14] <Mepho> thanks
[23:05:34] <Zorry> next
[23:05:38] <Zorry> 7.0 System Integrity
[23:06:05] <SwifT> I finished the concepts and introduction of the system integrity stuff and put it online on the site
[23:06:20] <SwifT> that guides users a bit into what the project will try to accomplish and what the focus is on
[23:06:32] <prometheanfire> yo
[23:06:36] <prometheanfire> sorry, was donating blood
[23:06:53] <SwifT> i'm working on the ebuilds for the ima/evm related tools, hopefully a first draft of them will reach the overlay next week
[23:07:01] <prometheanfire> blueness: anything important I miss?
[23:07:07] <klondike> ELATE :P prometheanfire see the twitter for a fast summary ;)
[23:07:08] <blueness> no
[23:07:22] <SwifT> I'm also extending the selinuxnode virtual guest with ima/evm so that people can play with that as well
[23:07:59] <SwifT> my first goal is to provide detection (and prevention) of tampering of images offline (i.e. when the image is hosted by a third party, make sure that the image content isn't changed by the third party)
[23:08:28] <SwifT> not sure I'll be making this by the next meeting (since I'm also going on a holiday within the next month) but at least that's the goal ;)
[23:08:54] <SwifT> that's it - stupid swig-2 took too much time to do more :(
[23:09:34] <klondike> SwifT: marry me :P
[23:09:55] <SwifT> klondike: you can't financially support me :p
[23:09:56] <klondike> I tried to look into that a year ago and had to run
[23:11:08] <SwifT> it's mainly a documentation issue really, half of the code is already available in the kernel, a small part needed for it is a fairly simple-to-apply fix, but trying to explain kernel keyrings and such... brrrr
[23:12:17] <blueness> sorry guys, i've got to run, a minor emergency, bees!
[23:12:24] <Zorry> blueness: k
[23:12:32] <SwifT> NOPE
[23:12:34] <klondike> blueness: kill'em with fire!
[23:13:29] <Zorry> SwifT: done?
[23:13:44] <Dwokfur> enable CHROOT_DENY_BEES
[23:13:49] <SwifT> Zorry: yup
[23:14:02] <Zorry> 8.0 Doc
[23:14:43] <klondike> Nothing on my side sadly, real life keeps things funny :(
[23:15:05] <SwifT> nothing beyond what I already mentioned for selinux & integrity
[23:15:57] <Zorry> https://bugs.gentoo.org/show_bug.cgi?id=341951
[23:16:15] <klondike> Ohh yeah
[23:16:16] <Zorry> is it okay if we move that page to the doc overlay
[23:16:22] <klondike> I was speaking with jns
[23:16:29] <klondike> On that one
[23:16:43] <klondike> He may want to contribute on the IDS topic
[23:16:56] <klondike> Though not sure if it is going to be prelude or other thing
[23:17:08] <Zorry> k
[23:17:14] <klondike> I'll put a big outdated warning on the doc
[23:17:29] <SwifT> there's a disclaimer attribute for that ;)
[23:17:41] <Zorry> klondike: was thinkig of moveing it to the doc ovelay
[23:17:59] <klondike> Zorry: that can work too though the warning should be there anyway
[23:18:00] <SwifT> I don't mind taking a stab at it as well, I can shephard (sp?) it under the integrity stuff
[23:18:27] <Zorry> klondike: yep
[23:18:43] <Zorry> SwifT: do it
[23:20:10] <Zorry> any one else?
[23:20:16] <klondike> prometheanfire: ?
[23:20:30] <prometheanfire> nope
[23:21:26] <Zorry> 9.0 Media
[23:22:13] <klondike> Ohh cool that's me
[23:22:24] <klondike> Let's see
[23:22:41] <klondike> I gave a talk in bilbao in a really big event called Euskal Encounter
[23:22:55] <klondike> Lot's of assistants fortunately :D
[23:23:04] <klondike> *Lots
[23:23:49] <klondike> Also I'm trying to close a few talks on the Balcans area, though that is yet in the air, we'll see
[23:24:11] <klondike> And well the meeting is being twitted blah blah blah
[23:24:25] <prometheanfire> dunno when we want to talk about this, but fosdem?
[23:25:05] <klondike> Can send a propossal
[23:25:31] <SwifT> right, I'm going to know about my work-time beginning of september to make sure I can go, I plan to give a talk on SELinux & policy development
[23:25:34] <prometheanfire> dates have been announced for it
[23:26:05] <SwifT> yes, they're now looking for the major talks and developer rooms. Once the devrooms are known, we can schime in for our talks
[23:26:32] <klondike> Hum
[23:26:52] <klondike> Should I try to push a Hardened talk as major? :P
[23:27:01] <Zorry> nope
[23:27:56] <klondike> Okjey, okey xD
[23:28:07] <SwifT> we'll be the underdog :p
[23:29:10] <klondike> I'll also try to make FOSDEM
[23:29:26] <klondike> Ehum and speaking of conferences, anybody wants to make FSCONS?
[23:29:34] <Zorry> any going to the mini gentoo stuff?
[23:29:40] <SwifT> the Czech one?
[23:29:46] <klondike> I can try to push for talks
[23:29:48] <Zorry> SwifT: yes
[23:29:57] <klondike> Zorry: is there a mini gentoo stuff? when where?
[23:30:13] <SwifT> probably not, I'm two weeks in hungary around that weekend, disaster testing new infrastructure
[23:30:14] <Zorry> klondike: when is fscons?
[23:30:35] <klondike> Zorry: november in Göteborg
[23:31:28] <klondike> 9 of november until 11 of november for more details
[23:31:40] <Zorry> klondike: http://www.gentoo.org/proj/en/miniconf/
[23:31:49] <Zorry> klondike: okay
[23:32:49] <Zorry> next?
[23:33:30] <Zorry> 10.0 Open floor
[23:33:35] <Zorry> any one?
[23:33:48] <klondike> I'd like to know what has scarabeus to say on the miniconf :P
[23:34:38] <klondike> Ohh yeah almost forgot
[23:34:39] <SwifT> I gotta go folks, battery's dead here
[23:34:46] <klondike> I'm giving a talk at fscons too xD
[23:34:48] <Zorry> SwifT: cu
[23:34:48] <SwifT> good job all!
[23:35:34] <Zorry> ty all for the meeting
