 The security is right. Okay, yeah. So I will move on to the smack update and we'll just do all the questions at the end. So the smack update, yay, smack. Stickers, anybody want some? I've got the red ones and the green ones. So what's new in smack this year? Most of what's gone on in smack has actually been done to it as opposed to for it. In particular, Paul mentioned this earlier, the mount and LSM infrastructures have been rather thoroughly revised. And as a result of this, there's been a lot of work, a lot of things have gone on inside smack in order to accommodate that. We added a rule KMM cache for the smack rule lists and got significant performance improvement by doing that. That was a very obvious change that one of the people at Samsung working on Tizen added. Also, there was this, in order to list out the labels that are known to the system, there was this kind of funky global label list associated, threaded through everything. And somebody recognized that there was an easier way to do it, that you didn't need that list after all and so we just took that out. Again, making it more performant and less memory consumptive, especially on small systems. And there were some bugs in the way IPv6 ICMP was handled that led to things, the bad neighbor syndrome that Paul was talking about earlier today. And just by actually taking care of that, a lot of cases where it was hanging before where you would get a timeout are immediately rejected. So kind of a big win there, especially for those people who are using IPv6. So there hasn't been a lot of change, but just to give you an idea of this, of how many time changes have gone in, we had 44 total changes. Most of them were in the stacking infrastructure. By far the next most was the mountain or the mountain's infrastructure changes. And actually there's some overlap in there because there are mount infrastructure changes for stacking as well as for the mountain infrastructure. Bunch of the cleanup that's been going on throughout the Linux kernel showed up here as well. So again, everybody who's here who had a hand in this, thank you very much. If there's nobody here, well, oh well. So what are we gonna do next? What's on the to-do list? By the way, the amount of work that I've been able to do personally on has been taken up by some other things that we talked about earlier. What are we gonna do next? Well, one of the things that came up in the process of actually doing the stacking was that the networking code really has got some cruft, it's got some bad ideas in it. And they're all mine. I will own up to that, those are all mine. But that was done before we had Calypso. Now that we have Calypso, the IPv6 code can be done a whole lot cleaner than it was initially. So probably the biggest task there is to replace the current IPv6 port-based controls with Calypso. And the other project that I thought was really interesting is we've got somebody who really wanted to do this. And so he's writing a translator for SC Linux policy to translate SC Linux policy into smack rules. That's going to be very interesting to see what the actual outcome of that is. I think we're gonna find that there are a lot of things where we have conceptual issues that are gonna make that something you can't really do automatically. But it will be an interesting thing to see how it comes out. And I hope to talk about that next year. And there's just one other thing I wanted to do as the last presenter here. I just want to call out James and we should give him a round of applause for putting this together and running the conference for us.