The CUBE's live coverage is made possible by funding from Dell Technologies, creating technologies that drive human progress. Hi everybody, welcome back to the FEDA in Barcelona. My name is Dave Vellante, I'm here with my co-host, Dave Nicholson, Lisa Martin is in the house. John Furrier is pounding the news from our Palo Alto studio. We are super excited to be talking about cloud at the edge, what that means. Charles Sy is here, he's the Senior Director of Product Management at Dell Technologies and Peter Federolf is the Chief Technology Officer at ACG Business Analytics, a firm that goes deep into the TCO and the telco space among other things. Gents, welcome to the CUBE, thanks for coming on. Thank you. Yeah, good to be here. So I've been in search all week of the elusive next wave of monetization for the telcos. We know they make great money on connectivity. They're really good at that. But they're all talking about how they can't let this happen again, meaning we can't let the over the top vendors, yet again, basically steal our cookies. So we're going to not mess it up this time, we're going to win in the monetization. Charles, where are those monetization opportunities? Obviously at the edge, the telco cloud at the edge, what is that all about and where's the money? Well, Dave, I think from a Dell's perspective, what we want to be able to enable operators is a solution that enable them to rule out services much quicker, right? We know there's a lot of innovation around IoT, Mac, and so on and so forth, but if they continue to rely on traditional technology and way of operations, it's going to take them years to enable new services. So what Dell is doing is now creating the entire vertical stack from the hardware through CAS and automation that enable them not only to push out services very quickly, but operating them using cloud principle. So when you say the entire vertical stack, it's the integrated hardware components with like, for example, a red hat on top, or a wind river. That's correct. And then open API so the developers can create workloads. I presume data, data companies, we just had a data conversation because that was part of the original stack. That's correct. So through an open ecosystem, you can actually sort of recreate that value, correct? That's correct. So one thing Dell is doing is we are offering an infrastructure plot where we are taking over the overhead of certifying every release coming from the red hat or the wind river of the world, right? We want telcos to spend their resources on what is going to generate them revenue, not the overhead of creating this cloud stack. Dave, I remember we went through this in the enterprise and you had companies like IBM or the AS400 and the mainframe saying, it's easier to manage, which it was, but it was still assumed by the open systems trend. Yeah, yeah. And I think that's an important thing to probe on is this idea of what exactly does it mean to be cloud at the edge in the telecom space? Because it's a much used term when we talk about cloud and edge in sort of generalized IT, but what specifically does it mean? So when we talk about telco cloud, first of all, it's kind of different from what you're thinking about public cloud today and there's a couple of differences. If you look at a big hyperscale or public cloud today, they tend to be centralized in huge data centers. Okay, telco cloud, there are big data centers, but then there's also regional data centers, there are edge data centers, which are your typical access central offices that have turned data centers and then now even cell sites are becoming many data centers. So it's distributed. I mean, like you could have, like even in a country, like say Germany, you'd have 30,000 cell sites, each one of them being a data center. So it's a very different model. Now the other thing, I want to go back to the question of monetization, okay? So how do you do monetization? The only way to do that is to be able to offer new services like Charles said, how do you offer new services? You have to have an open ecosystem that's going to be very, very flexible. And if we look at where telcos are coming from today, they tend to be very inflexible because they're all kind of single vendor solutions. And even as we've moved to virtualization, if you look at packet core, for instance, a lot of them are these vertical stacks of say Anoki or Ericsson or Huawei, where you can't really put any other vendors or any other solutions into that. So basically the idea is this kind of horizontal architecture, right? Where now across not just my central data centers, but across my edge data centers, which would be traditionally my access COs, as well as my cell sites, I have an open environment. And we're kind of starting with packet core, obviously, and UPFs being distributed, but now open ran or virtual ran, where I can have CUs and DUs and I can see they could be at the cell site, they could be in edge data centers, but then moving forward, we're going to have like Mech, which are new kinds of services, could be remote cars, it could be gaming, it could be the metaverse, and these are going to be a multi-vendor environment. So one of the things you need to do is you need to have this cloud layer. And that's what Charles was talking about with the infrastructure blocks, is helping the service providers do that, but they still own their infrastructure. Yeah, so it's still not clear to me how the service providers win that game, but we can maybe come back to that because I want to dig into TCO a little bit, because I have a lot of friends at Dell, I don't have a lot of friends at HPE, I've always been critical when they take an x86 server, put a name on it that implies edge, and they throw it over the fence, and it's not going to work. Okay, we're now seeing, we were just at the Dell booth yesterday, you did the booth crawl, which was awesome. Purpose-built servers for this environment. That's right. So there's two factors here that I want to explore in TCO. One is how those next-gen servers compare to the previous gen, especially in terms of power consumption, but other factors, and then how these sort of open-ran, open ecosystem stacks compare to proprietary stacks. Peter, can you help us understand those? Yeah, sure, and Charles can come in on this as well, but I mean, there's a couple of areas. One is just moving the next generation. So, especially on the Intel side, moving from Ice Lake to Sapphire Rapids is a big deal, especially when it comes to the DU, and the DU, you know, with the radios, right, there's the radio unit, the RU, and then there's the DU, the distributed unit, and the CU. The DU is really like part of the radio, but it's virtualized. When we moved from Ice Lake to Sapphire Rapids, which is third generation Intel to fourth generation Intel, we're literally almost doubling the performance in the DU, and that's really important because it means like almost half the number of servers, and we're talking like 30, 40, 50,000 servers in some cases, so, you know, being able to divide that by two, that's really big, right, in terms of not only the cost, but all the TCO and the optics. Now, another area that's really important, when I was talking, moving from these vertical silos to the horizontal, the issue with the vertical silos is you can't place any other workloads into those silos, so it's kind of inefficient, right, whereas when we have a horizontal architecture, now you can place workloads wherever you want, which basically also means less servers, but also more flexibility, more service agility, and then, you know, I think Charles can comment more specifically on the X or 8000 some things Del's doing because it's really exciting relative to what's happening there. So, you know, when we start looking at putting compute at the edge, right, we recognize the first thing we have to do is understand the environment we are going into, so we spend with a lot of time with Calcos, going to the south side, going to the edge data center, looking at operation, how do the engineer today deal with maintenance replacement at those locations? Then based on understanding the operation constraints at those sites, we create innovation and take a traditional server remodel it to make sure that we minimize the disruption to the operations, right? Just because we are helping them going from appliances to open compute, we do not want to disrupt what is having a very efficient operation on the remote sites. So, we created a lot of new ideas and develop on general compute where we believe we can save a lot of headache and disruptions and still provide the same level of availability, resiliency and redundancy on an open compute platform. So, when we talk about open, we don't mean generic. Fair, fair, fair standard. Open is more from the software workload perspective, right? A Dell server can run any type of workload that customer intends. But it's engineered for this environment. And so, what are some of the environmental issues that are dealt with in the telecom space that are different than the average data center? The most basic one is in most of the traditional cell power, they are deployed within cabinets instead of racks. So, there are depth constraints that you just have no access to the rear of the chassis. So, that means on the server, everything you need to access need to be in the front. Nothing should be in the back. Then you need to consider how labor union come into play. There's a lot of constraint on who can go to a cell tower and touch power. Who can go there and touch compute. So, we minimize all that disruption through a modular design and make it very efficient. So, when we took a look at the XR8000, literally right here sitting on the desk, took it apart, don't panic, just pulled out some sleds and things. One of the interesting demonstrations was how it compared to the size of a shoe. Now, apparently you hired someone at Dell specifically because they wear a size 14 shoe. So, it was even more dramatic. But when you see it, and I would suggest that viewers go back and take a look at that segment specifically on the hardware, you could see exactly what you just referenced. This idea that everything is accessible from the front. So, I want to dig in a couple of things. So, I want to push back a little bit on what you were saying about the horizontal because there's the benefit, if you've got the horizontal infrastructure, you can run a lot more workloads. But I compare it to the enterprise. Because that was the argument, I've made that argument with converged infrastructure versus say an Oracle vertical stack. But it turned out that actually Oracle ran Oracle better. Is there an analog in Telco or is this new open architecture going to be able to not only service the wide range of emerging apps, but also be as resilient as the proprietary infrastructure? Yeah, and before I answer that, I also want to say that we've been writing a number of white papers. So, we have actually three white papers we've just done with Dell, looking at infrastructure blocks and looking at vertical versus horizontal and also looking at moving from the previous generation hardware to the next generation hardware. So, all those details, you can find the white papers and you can find them either on the Dell website or at the ACG Research website. ACGresearch.com. ACG Research, yeah. If you just search ACG Research, you'll find lots of white papers on TCO. So, you know, what I want to say relative to the vertical versus horizontal, yeah, obviously in the vertical side, some of those things will run well.  However, that being said, as we move to cloud native, you know, it's very high performance, okay, in terms of the stack, whether it be a Red Hat or a VMware or other cloud layers, that's really become much more mature. Now, it's all CNF-based, which is really containerized, very high performance. And so, I don't think really performance is an issue. However, my feeling is that if you want to offer new services and generate new revenue, you're not going to do it in vertical stacks, period. You're going to be able to do a packet court. You'll be able to do a ran over here. But now, what if I want to offer a gaining service? What if I want to do metaverse? What if I want to do it? You have to have an environment that's a multi-vendor environment that supports an ecosystem. Even in the ran, when we look at the RIC and the X-Apps and the R-Apps, these are multi-vendor environments that's going to create a lot of flexibility. And you can't do that if you're restricted to, I can only have one vendor running on this hardware. So, it's- Yeah, we're seeing these vendors work together and create RICs, and that's obviously a key point. But what I'm hearing is that there may be trade-offs, but the incremental value is going to overwhelm that. Second question I have, Peter, is TCO. I've been hearing a lot about 30%, where's that 30% come from? Is it up, is it from an OPEC standpoint? Is it labor? Is it power? Is it, you mentioned, cutting the number of servers in half? If I can unpack the granularity of that TCO, where's the benefit coming from? Yeah, the answer is yes. Okay, you want to find that in terms of where the big bang for the bucket is. I mean, so you really need to look at the white paper to see details, but definitely power, definitely labor, definitely reducing the number of servers, you know, reducing the CAPEX. The other thing is, is as you move to this really next generation horizontal TELCO cloud, there's the whole automation and orchestration. That is a key component as well. And it's enabled by what Dell is doing. It's enabled by the, because the thing is, you're not going to have end-to-end automation if you have all this legacy stuff there, or if you have these vertical stacks where you can't integrate. I mean, you can automate that part, and then you have separate automation here. You need to have integrated automation and orchestration across the whole thing. One other point I would add also, right? On the hardware perspective, right? With the customized hardware, what we allow operators to do is take out the existing appliance and push an edge-optimized server without reworking the entire infrastructure. There's a significant saving where you don't have to rethink about what is my power infrastructure, right? What is my security infrastructure? The server is designed to leverage the existing what is already there. How should TELCO's Charles plan for this transformation? Are there specific best practices that you would recommend in terms of the operational model? Great question. I think first thing is do an inventory of what you have. Understand what your constraints are, and then come to Dell. We would love to consult with you based on our experience on the best practices. We know how to minimize additional changes. We know how to help your support engineer understand how to shift from appliance-based operation to a cloud-based operation. Is that a service you offer? Is that a pre-sales, freebie? What is, maybe both? It's both, yeah. It's both. Yeah. Guys, just really quickly, Dave loves the TCO discussion. I'm always thinking in terms of, well, how do you measure TCO when you're comparing something where you can't do something to an environment where you're going to be able to do something new? And I know that that's always the challenge in any kind of emerging market or where things are changing. Well, I mean, we also look at, not only TCO, but we look at overall business case. So there's basically service agility and revenue. And then there's faster time to revenue as well. And actually, ACG, we actually have a platform called the BAE, or Business Analytics Engine, that's a very sophisticated simulation cloud-based platform where we can actually look at revenue month by month. And we look at what's the impact of accelerating revenue by three months? By four months? By six months? So you're looking, you're not just looking at TCO. We're looking at the overall business case benefits. Yeah, exactly right. There's the TCO, which is the hard dollars. CFO wants to see that. He or she needs to see that. But you can convince that individual that there's a business case around it, and then you're going to sign up for that number. And they're going to be held to it. That's the way the world works. At the end of the day, Tocos have to be offered new services, because look at all the money that's been spent on investment on 5G and everything else. 0.5 trillion over the next seven years. All right, guys, we've got to go. Sorry to cut you off, but we have wall to wall here. All right, thanks so much for coming on. Fantastic. Donate for Dave Nicholson. Lisa Martin's in the house. John Furrier in Palo Alto Studios, keep it right there MWC23 Live from the FIDA in Barcelona.


OK. So good afternoon, everybody. Lovely to see you all here today. First of all, I would like to share their way, 25 contributors, you can see. I'm also here. Sorry for my bad voice. I found there an exciting thing. Do you know, a block team can be made without writing a single line of CSS code? Yeah. 2023, block team has no CSS code at all. Even no PHP code, all right? Isn't it awesome or cool? I think both. So if you want to make a functional and beautiful block team, you have to be a master in Tim Dixon, right? So I'm curious to know who is the experience with this team development or customization in this room. Could you say hi to me? Excellent. Also known faces, by the way. So Anton will help with you to go through that part of the Tim Dixon so that you can understand the Tim Dixon even better. And after completing this session, you will be able to start your next block team development more efficiently. And if you have any classic team, you can also convert your classic team into hybrid team by adding Tim Dixon. So what is Tim Dixon? Tim Dixon is a configuration Dixon file. It's for controlling Tim styles and block settings. This file is located in the root director of your team. It works with both classic team as well as the block team. But it doesn't work with the classic editor. So just remember, the minimum UK version of WordPress is 5.8. Otherwise, you have to activate the gluten block plugin. So before going into jumping to Tim Dixon, you know, Dixon is come from JavaScript. It's a lightweight data format for storing and transporting data, the data separated by values of objects and name value pairs. And here, data separated by values, currently we solve the objects. Or no, square bracket, all these errors list. Excuse me. Now, we are seeing what exactly looks like a Tim Dixon file. Here, a little bit of stuff is schema, is version, settings, styles, custom templates. There are almost seven sections, mainly seven sections. I rearrange those seven sections into three groups. Group number one is the schema and version. And the group number two has the most important and essential two-part settings and styles. And the last one has the custom templates, template parts, and patterns. But today, we are mainly talking about styles and settings. All right? So what setting does in Tim Dixon? Settings actually does two things. Controlling block editor and individual blocks. And the second is create CSS preset with fellow. All right? Here you can see the stuff inside the settings. There are almost nine settings categories. Later, we're going to see more example on this. So don't worry. So what does styles in Tim Dixon? It's very easy, styles for applying styles to the website and individual blocks. Also, there are seven styles categories. So this part is more important because it's very important to understand the difference between settings and styles. Because you might get confused who are you going to write on this. You can see the similar categories in settings, blocks, border, color, spacing, and same things go here also. So it's very important to understand the difference. So in general, we control options related elements and general CSS preset in settings. On the other hand, we control design related elements. OK, right? In settings, we define color pillars in settings. On the other hand, we use those different colors in styles. I think you guys understand this. OK. So let's dive into some more examples. How it works in practical. OK, color. Now we are going to set the color pillars in the color of these settings section. Each color has three key value pairs, name, slug, and color. The color value can be any various CSS color value, such as color, name, RGB, or hexa. Yeah, it's string. It's the output word response, this and that, and create CSS preset for each color, for each color, and add them to the body selector. When you add these on the theme, you can see these from the, I think, console. So next. Also, you can see your edit color to the site editor color options, all right? Now, how we can apply those defined color. Here, we have set color inside the settings as background and text color. If the output word press force this and that as well, and add them to the body selector and another selector. OK. You might notice on the last slide, all right? The color at the top level of the settings, sorry, on the styles, it will affect only the, sorry, it will affect the full site, OK? And in the color inside the block, only if it this name block type, I think it's very cool. And the same thing goes for the settings as well. Just remember this one. OK. Now, we are going to talking about very important thing. By default, Gutenberg disabled most few, a few options like border color, spacing, typography, this stuff. But we can enable those options by adding true-to-appearance tools. Otherwise, your editing will not affect your site. You have to first of all set true-to-appearance tools inside settings. So this is very important. So now we are talking about spacing. How to control spacing like margin-pairing options without writing a single line of CSS code. So by default, WordPress provides these seven spacing presets. You can also see this spacing is preset as margin-pairing in the site editor, control options. We can also use those default spacing preset as spacing size like margin-pairing value in the style section. But if you want to create or make your custom preset, then you have to set, first of all, you have to set 0 to spacing scale inside these spacing of settings. These 0 will omit all the default spacing presets. Then now you can set these kind of stuff. This is your custom presets. Each custom preset has three quilos pairs, size, slug, and name. This should be chronological. And then as the output, what is another of those presets and add them to the body selector? All right. Also, you can see this you added custom spacing effected in the site editor. OK, now we are going to talk about typography. You might want to add your custom font family to your theme. Yeah, you can add your custom font family inside the font families under the settings typography. Each font family has four quilos pairs. There you can see font family, name, and slug. And if you want to add your downloaded local font, you can set it in font phase. I think you can guess. This font phase is similar to CSS import font phase, right? OK. It will create this preset as well. And also, you can see these, your integrated fonts available to the site editor, font choice options. OK, now you also add your custom font sizes. There are also only two quilos pairs, size and slug. It will create this preset. You also see this stuff available in the site editor also. So now, how to apply those different typography to your site? Very easy. We have added those generatices in the styles section of typography, font family, font size. As the output word response is just some data and adds the stuff here. OK. Now, we are going to explore more exciting thing, schema inversion. Which schema version do we need to choose? No confusion. We have to choose the correct version number two. If anyone used version number one, then what would recommend you to go to two? All right. So this is very important. What actually does is just an schema. This schema will help you to write in theme design more efficiently by providing features like autocomplete, quick suggestion tool tip, and the mainly validating data. So let's show how a schema help you write in theme design. When we add this schema, you can see the orange version. Also, you can see the auto suggestion. Isn't it cool? Yeah, of course, you have to choose a very good idea. I think free one, Visual Studio Code, would help you to get this one. So after that, I have now I can say, you don't have to remember all the things, right? Because the schema will help you to how to write in theme design. Isn't it cool? Yeah, I think it's cool. So guys, I'm going to near to end before then a quick tip for you. You change this in theme design might take so long to update in browser. I think it's maybe a catching issue. It will resolve if you set true to WB debug or skip debug. I think it will resolve your issue. So that's all for today, guys. I hope you enjoyed my session very well. And you are ready to start your next blog team. So let's make it happen. Thank you. Thank you. Thank you.


The responsible LEN-based investment navigator was developed jointly by the LENPOL tool in IED to create an online platform bringing together a wide range of tools and guides on how to address specific LEN-related issues in the context of LEN-based investments. This material is usually scattered across different organizations' websites and library, so the idea there was to have it all in one space and make it easily accessible and searchable based on who it's made for specifically and what topic it covers. For a bit of history, a first version of the navigator was developed two years ago under the DFID-funded legend program to provide guidance specifically to private sector actors who are involved directly or indirectly in the making of LEN-based investments, so that included lenders and investors, companies, buyers, and we had guides on how they can approach consultation and ethic, compensation, conflict resolution, transparency, etc. And now ideas embarking on a new project called ALINE, which stands for Advancing LEN-based Investment Governance, and this program is taking a more encompassing governance approach to address issues linked to LEN and investments, and that involves working with a variety of actors who play an important role in shaping LEN relations, in particular governments and civil society actors, in addition to the private sector. So in line with this, we have revamped the navigator and have added over 100 new guides for these new audiences, covering issues relevant to the ways in which governments and civil society can intervene to safeguard LEN rights. So to provide a few examples, we now have guides on how NGOs and grassroots organizations can help communities better prepare for negotiations with investors, or guides on what avenues exist for governments to improve the law in relation to LEN and more investments. We've also added a couple of new features to the website. We now have a news and blogs tab that offers content on what's currently happening in the world of LEN and investments, and we also have a new tab that provides links to other platforms that offer complementary services to protect LEN rights in the context of investment that can be of interest to the different audiences I've mentioned. So we've really tried to make this new version of the navigator as useful and relevant as possible for anyone who's interested in learning more about LEN-related issues in relation to investment and who's looking for guidance to address these issues and better protect LEN rights.


Well, Eric, Kevin Kevins at P&A. Yeah, nice to meet you. In person. Yeah. How often are you in office? About three days a week. Yeah, same. Yeah, ever since Dan kind of came out with the directive on how often to be in here. But you're a lot taller than I was expecting. Long legs. Yeah, that makes sense. Makes sense. But... Well, anyway, it's gonna be in person. I gotta keep going. Yeah, I gotta meet


This is the degree of Bachelor of Arts and Bachelor of Education. I would like to learn more about Native Studies. I would like to learn more about Native Studies courses. I would like to learn more about Canada. I would like to learn more about Canada. I would like to learn more about Canada. I would like to learn more about Canada. I wanted to get into University, but I knew someone else had chosen me. I wanted to learn more about myself and my family knowledge of course. I would like to learn and learn more I'm not going to do that. I'm going to go to residential schools in New York. I don't want to go to native peoples in Canada. I don't want to go to a native community. I don't want to go to a local community, but I'm going to go and do it. I don't want to go to a local community, but I'm going to go to some schools in New York. I had a dream. I was born and raised in a human being. I was born and raised in a human being. I had a lot of courses, I was a student, I had a lot of education in the U.S. I was born and raised in a human being. I was born and raised in a human being. I did a lot of indigenous- HTML content, I wrote on a different pale because that's my only dream. I want to think about that. I wrote my own story on Indigenous video lessons I was born and raised in U.S. I was born and raised in a human being I was born and raised in a human being We bring our children here, and we teach them this in their culture. It's not a school in the countryside. We are in the countryside now. The indigenous education is very important in the schools, especially in the areas that are very few, and they have the quality of life. The education is very good. Ok now let's start. then we don't use this bed. we come in from the other directors and send them back we need to replace our oversize ones of the waktu that are for reconditions but if that is important, we don't use a bed for each of these. In my art, I will try and portray myself here and put words into my mouth, to make two cultures own one population in this special universe. On the outside, I will try to pointing to the people. While I am in a special culture, the people feel themselves. Once I find myself, authors, noot zi no hello tine ennau, ennau deek lina n'adani erit lisaan darit lisa ttini, kod du hunu heks i hejja, ennau deek lina d'ennau erit lisaan rit lisaa, bet adi de al n'aduse kwi hadon el chen. I dant u darit lisaan li, lahae ja i d'anuhin nia, edir curriculum deek lisaan li du hunu, ennau betzi ane, dant u radani d'ndan li, klo al sum n'idee n'id d'ndan al sum l'aikha.


The Hood and Cobra Commander 788 here, it's time for another vintage GI Joe toy review and after last week, I wanted to look at something that was maybe a little bit better. So this week, we're going to look at the Desert Fox six wheel drive vehicle and the driver skid mark. Hey, let me stop you right there. We're not going to be making fun of skid marks name. Now maybe other reviewers would do that and everybody would get their giggles, but we're all adults here. We're not going to engage in the potty humor. We're going to be a bit more mature about this. I made brownies. Do you want one? No. Fun of skid marks name. We all know why people make fun of his name. We don't even need to go into that. Plus, we have a nice vehicle to look at, so we don't need to go to the gutter. We're only high brow on this channel. Hi, ice cream. Do you want it? It's chunky chocolate. No, thank you. I'm not hungry. I'm shooting a video. Oh, buddy. HCC788 presents the Desert Fox and skid mark. This is the Desert Fox, the six wheel drive vehicle from 1988 and the driver, the unfortunately named skid mark. This vehicle and figure set were first available in 1988 and were also available in 1989 and were discontinued for the year 1990. If there was a replacement for this vehicle in 1990, that would have to be the hammer. The vehicle based on the real world Humvee and this is a very nice, mostly realistic vehicle for that late in the line. The Desert Fox is, of course, a desert vehicle and it is appropriately colored with the primary color being this light tan sandy color. There were other desert vehicles released before the Desert Fox. I would say the first one was the vamp mark 2 from 1984. After that, the Mahler MBT from 1985 was in desert colors. In 1986, we got the Tomahawk helicopter in desert colors and this one had a camouflage paint scheme. Very nice. In 1987, the mobile command center was also colored for the desert. The Desert Fox came with one action figure skid mark and we don't need to comment on his name. We all know what it means. We're going to set skid mark aside for now so we can take a closer look at the Desert Fox. Let's look at the parts and the features of the Desert Fox starting in the front here. And in the front, we have this grill. We have a couple of pseudo headlights. There's no detail on them. They're really just cutouts in the top portion of the vehicle so you can see the gray underneath. We have a little bit of detail on here up at the top. We have the front wheels which are plastic and hollow and they have very minimal detail on them. Really just a little bit here. I think the exposed clip here is not very attractive. The wheels do turn. You can click them once to the right, middle and once to the left. They do stay in those positions and I guess that's fine. I don't really need turning front wheels on land vehicles but I guess that's a nice bonus. It does have a plastic axle not a metal dowel like the vamp so that will be more prone to breakage. We have a roll bar here in brown plastic with some headlamps and on the roll bar we have a pair of missiles. These orange missiles have a universal dumbbell slot that goes straight through the whole missile and you just put that on the roll bar like so. They fit on pretty securely. The blueprints call these Scorpion SS-12 anti-tank missiles and I don't love the orange color but it's okay for a desert vehicle. I guess these colors could be all in the same pallet. We have the cab which fits two action figures. We have the driver's seat there. Plenty of room to get the driver in and out of the vehicle. We have a gear shifter in the center there, a few odd buttons. We have very minimal dashboard detail. We have a non-functioning steering wheel. I'll demonstrate how to put the figure in the vehicle. There's plenty of room to slide him in the side door there and there is no back peg. There's no seat belt. There's nothing to really secure him in there but usually he's in there deep enough that he doesn't fall out too easily. Behind the cab we have this space and it's a remarkably large amount of space for such a moderately sized vehicle and right in the middle there we have the machine gun turret. The turrets call this a 20mm automatic loading anti-aircraft cannon and it can elevate on the turrets. There is some detail on the machine gun. It is not based on a real world weapon as far as I know. The turret itself is also in that orange color. Again, not the best color but tolerable for a desert vehicle. It has a texture pattern on it to make it look like it's made of metal. The turret can turn all the way around 360 degrees. The floor of this machine gun turret has a couple of foot pegs and you can use those foot pegs to place an action figure on there to operate the machine gun. Now, it's not super easy to get the figure on there. You can get both feet on there sometimes. There we go. So now you have a figure that can actually operate the machine gun. What's nice about this, the figure turns as the machine gun turret turns and that is really an excellent feature, maybe the best feature on this vehicle. This manned machine gun turret actually fixes a problem that the vamp had. The vamp had this really nice machine gun on it but who operates that machine gun? There's no space for an action figure back there. Sometimes the G.I. Joe comic book would show a person back there aiming the gun even though you couldn't really do that with the toy. We have the back wheels which are much the same as the front wheels. We have two on each side which is what makes it a six wheel drive. Here in the back we have this extra feature, this side facing seat with this computer panel. I'm not sure what all this computer gadgetry is for, maybe for targeting something. There's a foot peg way in the bottom there. I'm not sure how useful that would be but maybe you could fit an action figure's foot in there. It's at an odd placement there that you'd have to get the leg at kind of a strange angle. I'm not sure you could actually use that but this is still a really nice little bonus feature here. This is a nice way to carry an extra action figure on the vehicle without just having like foot pegs on the rear bumper which is what a lot of vehicles did. Here in the back we have this antenna in brown plastic and I really like this. This is the extra detail that makes the vehicle feel more realistic. Like all antennas and G.I. Joe vehicles this will probably be the most frequently missing part. Here in the bumper we have a fuel port that is just a sticker. Gone are the molded in fuel ports on earlier vehicles which you could use the gasoline hoses that you got with the USS flag and the Cobra Terror Drone to really pretend that you were refueling the vehicle. Finally in the very back we have a universal tow hook which you could use to tow something perhaps the mountain howitzer. Just hook it on there. I don't think there were any desert themed towed weapons at least not that I remember. Maybe somebody can correct me on that. There's an odd thing I noticed looking at Skidmark and the Desert Fox. He sits really deeply down in there and that's not necessarily a bad thing. Comparing that to a clutch in the vamp. Clutch he actually sits a little bit high for this bar.  So it's like the vamp is just a little bit too small and the roll cage is a little bit too low for him. But we have a different problem with Skidmark. He can't see over the dashboard. The dashboard board is too high. Now let's look at the figure that came with the Desert Fox. Skidmark. Now settle down. We're not going to make fun of Skidmark's name. That's a cheap shot. Skidmark did not come with any accessories so let's take a look at his articulation. He had the articulation that was standard by 1986. He could turn his head from left to right and look up and down. He could swing his arm up at the shoulder and swivel at the shoulder all the way around. He had a hinge at the elbow. He could bend at the elbow about 90 degrees. He had a swivel at the bicep. He could swivel his arm all the way around. The figure was held together with a rubber O-ring that looped around the inside. That allowed him to move at the torso a bit. He could move his legs apart about so far. He could bend his leg at the hip about 90 degrees and he could bend at the knee about 90 degrees. Let's look at the sculpted design and color of Skidmark. And the first thing you notice is the palette that we're dealing with has a very bright orange, a very bright green, and a darker green with just a few black spots for details. On the head we have a non-removable helmet in very bright orange and we have, looks like some sunglasses and a fair face sculpt there. And on the helmet we have some dents in it and, you know, I actually kind of like this. It gives the helmet some character. Of course I would prefer that helmet to be removable but if you're going to do a non-removable helmet you might as well do one that looks good and I think this one looks pretty good. On his chest we have a bright orange vest in the same bright orange color as the helmet. We have some detail front and back. We have some odd black details here. I'm not sure what those are supposed to be but we have what looks like a knife. We have a black pistol and a holster and we have what looks like a radio receiver with a cord sculpted on that runs around to his back and we'd have to assume that this is connected to the communication system in his vehicle and I think that's really nice. I think it would have been nicer if that cord had been painted in the same way as the receiver rather than left unpainted. This is a very well sculpted vest in a horrible color but I have one other problem with the vest other than the color. It has these sculpted on pouches under his arms on both sides and those pouches actually interfere with the arm movement a little bit. You can't put skid marks arms all the way down by his side because they bump right into those pouches so his arms stick out a little bit. On his arms we have dark green long sleeves and this is a very nice color. I like this color but it's a color that doesn't appear anywhere else on the action figure so it's kind of out of place. I prefer this color to the other colors on the action figure but it just doesn't go with anything else. He has sculpted onto his right wrist a couple daggers. Very interesting little detail there. Now since they are on his right wrist they would be convenient to pull out with his left hand and this may be an indication that skid mark is left hand. His waist piece is a pretty plain sculpt. He has a belt and he has a belt buckle with US stamped on it. Other than that there's really nothing special about it. His legs are in that light green color. This is not quite neon green but it's close. It's very bright. On his right leg he has a pocket. On his left leg he has what looks like a mini sawed off shotgun. It's in a holster like a pistol and it's on his left leg. So that also may be an indication that skid mark is left handed. On both his legs he has sculpted in stripes that run all the way down his leg. Then there at the bottom of his trousers we have what look like elastic bands kind of like sweat pants and then of course we have orange boots in that same bright orange color. Let's take a look at skid mark's file card. It has his faction as GI Joe and it has a portrait of skid mark here and this portrait makes it look like his helmet should be yellow and that may have been the color that they were originally going to have the helmet in yellow. I don't think I can get behind this. I think the yellow might have actually looked worse than the orange. His final name is skid mark and he is the GI Joe Desert Fox six wheel drive driver and his final name is serial columbani and his file name may have been inspired by Giuseppe Columbani who was an Italian soldier who wrote a treatise on martial arts. Larry Hama the writer of the GI Joe comic book who also wrote these file cards was a martial artist and he may have come across Columbani's writing. His primary military specialty is fast attack vehicle driver secondary military specialty is infantry. Birthplace is Los Angeles California and his grade is E4. This top paragraph says skid mark was the kid that was held up by your mother as a shining example of everything that you were not. He was annoyingly polite maddeningly well groomed and excruciatingly successful in his studies. There was a collective sigh of relief from his contemporaries when he received his first driver's license and subsequently shattered all known records for the accumulation of speeding violations. This quote down here at the bottom says he keeps his locker and bay area squared away and spotless. It makes everyone else look bad by comparison. This could have been a cause for resentment if he wasn't the fastest and most reliable recon driver around. The worst thing that his teammates can say about him is the best thing that a soldier can say about another soldier. He does his job. I wouldn't call that a ringing endorsement. So this is the kind of guy that enjoys demonstrating that he's better than you so you kind of enjoy seeing him taken down a peg. Skid mark and the Desert Fox's GI Joe media appearances were brief. First of all he was not animated for the GI Joe cartoon series. He was only animated for TV commercials. He did not show up in the TV show. In the GI Joe comic book series published by Marvel Comics he first appeared in issue number 72 and also in issue number 73. And that was kind of important because those events precipitated the Cobra Civil War which is still one of my favorite story arcs in the Marvel comic run. In the comic book his uniform and helmet were colored green which looks a lot better. I really like that color scheme it would have looked great on the action figure. Looking at the skid mark action figure overall this is a pretty good sculpt that is ruined by a horrible color scheme. And I can't overlook the color that was a design choice and the designers have to be graded on that. The color takes what would otherwise be probably a middle tier figure and puts it right into the bottom tier. Looking at the Desert Fox overall this is a really nice vehicle. I can't quite put it in the top tier. I'm gonna call it a middle tier vehicle. It just has a few flaws but if you were to fix just one of these flaws it would probably be a top tier vehicle. It's really close. I don't like the exposed clips on the wheels. Some hubcaps covering those up would have looked a lot better. And the driver sits a little too low in the cab. He can't see over the dashboard. He's gonna have to sit on a phone book to drive the thing. But other than that the Desert Fox has a lot going for it. I love the gun turret. I really like the back seat. I like the color scheme. Most of the color scheme. The orange is not my favorite but I can live with it. I think the Desert Fox is an adequate successor to the Vamp Mark II. Also this is a very economically designed and constructed vehicle. It really doesn't have very many parts but it still has a fair number of features. I have some personal history with this vehicle. The Desert Fox was the second to last vehicle that I got as a kid. I was still getting some GI Joe in 1988 but it was some time within 1988 that I finally cut myself off from GI Joe. But I do remember getting the Desert Fox and I think I was pretty happy to get it. That was my review of the 1988 Desert Fox and Skidmark and congratulations guys. I'm getting through the whole video without making fun of Skidmark even once. Don't forget to like this video on YouTube. Subscribe on YouTube. Comment and share this video. That's what keeps this channel going. Like me on Facebook. Follow me on Twitter. Support me on Patreon. And check back next week for another vintage GI Joe toy review. Thanks for watching and until next time remember only GI Joe is GI Joe. Hey baby I'm done shooting the video. How about those brownies?


Hello. Welcome to Jenks Library. My name is Carolyn Oakes and I'm the Instruction Librarian here. Today, I'm here to help you with your weekly assignment to locate a scholarly or peer-reviewed article related to your weekly topic. My goal is that you will be able to quickly and easily find sources that are on topic, free to access, and of course scholarly or peer-reviewed. These are sources that are written by experts in the field and then rigorously reviewed before being published in scholarly journals. In this video, I will show you how to search library databases by topic. Let's start at the library homepage of Gordon.edu slash library. There are a lot of resources linked here, but for today we'll be focusing on this search the library box, specifically the tabs for databases and journals. Start with a database search when searching for a specific topic. After selecting databases, I like to select View All Databases, unless I know that I want to search within a specific database like PubMed or Academic Search Ultimate. To narrow down this list of 135 databases, use the subject dropdown to narrow down to Communication Sciences and Disorders. Up top, two databases have been highlighted as best bets for CSD research, but there are other multidisciplinary databases that you can search within as well. Select Communication and Mass Media Complete, and it will open up to the Advanced Search. This search starts with more features than a Google search. One important tool here is the peer reviewed box, which narrows down the search results to only include scholarly and peer reviewed articles. When you search in a database, use specific terms. For example, if I'm looking for a scholarly article on phonological disorders, I might want to focus on a specific disorder in my research. This search has only yielded 10 results. To expand search results, add in like terms connected by the Boolean operator OR. This tells the search engine that I want either term in my results, while the Boolean operator AND says I want both terms in my results and will narrow my results. If you can't think of terms, start typing OR, and most databases will suggest like terms. When you select an article title, it will bring up several key resources. An abstract, a link to the full text, and a toolbar on the side, which gives you access to citations. Another important link in this toolbar is permalinking. If you want to save a link and not download the article, make sure that you're selecting the permalink, as the URL at up top will not direct you through Jenk's library.


All is Satan Muhammad's father. Okay. Thank you. Okay, so What language did Jesus speak? Aramaic How do you say God and Aramaic?    Sorry. I wasted your time


There's a lot of people who talk about national being a right-wing party. I don't see national as being a right-wing party. I don't think they've ever been a right-wing party. They're very much, you can say they're conservative party, but it doesn't mean right-wing. And they're conservative in that they very much support the status quo. So they don't do any radical changes. The last radical changes they did was the cancellation of bringing in the Employment Contracts Act and doing all of those changes that happened in the 90s, which was a continuation from what Labour did in the 80s. But they generally are stable managers of the economy. And so I don't see them as being right-wing. They're more a centrist. And if you look at under John Key, there's no way he was right-wing. He was very much left of centre. And that's one of the great achievements of Helen Clark that people never talk about, is that she managed to move the political dial from the right and from the centre to the left of centre. And National moved that dial with it. So they're not right-wing at all. And when people talk about how can National attract the right-wing voters that they've lost, well, they shouldn't be attracting those people. They should leave those people to the ACT Party to hoover up because MMP is about governments of coalitions. And under John Key, National destroyed their coalition partners and eventually that came unstuck on them when they lost the 2017 election to second place getter Labour. So I think that they should continue to straddle the centre, be the party of the status quo, and leave the radical agenda and the right-wing agenda to the ACT Party. And you don't have to get up to being 45% and dominating everybody. You could have two parties, one at, say, 35% and another one at, say, 15% and you've got a government. No, I don't believe that National asked centre-right. I believe that they're actually centre-left. What they need to be is more centre. Leave the right and the radical right to the ACT Party and grow the ACT Party because two parties of a reasonable size is better than one large party being a complete broad church. Otherwise you end up with the problem that we had in the National Party in the last two years where they've encouraged their, what I call the wet-wing, which are very liberal in their outlook on absolutely everything.  Well, these things don't matter to 95% of the population. National needs to concentrate on governing for 95% of the population, not the 5% of single-issue rowdies that raise their head whenever they feel aggrieved about something. Well, some of them haven't been enacted yet, but they're likely to be enacted before the next election. The first thing would be the Three Waters thing, which is basically the marification of our water assets and basically handing over 50% of those assets to the control of Maori, abrogating the control of councils and abrogating democracy at the same time. The other thing that I would repeal would be Labour's removal of the right for local councils to hold referenda on particular items. It was an appalling breach of democracy and trust, passing that in the dead of the night under urgency. And there's a couple of other reforms that need to be undone as well. The Resource Management Act reforms that Labour are bringing in are going to make things actually worse. And their health reforms are just going to waste half a billion dollars on shifting the deck chairs on the Titanic. So there's a lot of things I think that what Judith Collins needs to do is start a spreadsheet and a list of things that should be repealed and she should create an omnibus bill that can be brought in in the first 100 days of taking over and just remove all of these legisly blockages that the Labour Party has brought in. Well, Winston's got a choice. He's sitting at about 4% in the latest UMR poll. He hasn't campaigned on anything at all. I think that he'll be able to campaign and lead up to the election on the basis that, do you miss the handbrake now? And I think there's a large chunk of Labour voters that would probably see that having someone sensible and an elder statesman there to temper the edges of the more radical elements in society on the left and the right might be a good thing. If he went with Labour again, that would be the end of New Zealand first. No one would ever vote for them again on the basis that he always goes with Labour. But people forget that the first time when Winston Peters had a chance to go into coalition, he went into coalition with National. Now, what National did to Winston Peters during that coalition was appalling. And if you know the people who were involved and know the backstory and you'll realise that what was sold to us via the media and via Jenny Shipley was starkly different from what actually happened in reality. And that is the underlying reason why Winston Peters has basically sought U2 against various people in the National Party ever since that day. Now, all of those people, every single one of them who were involved during that time and all the people he's had fights with in the courts, people like David Carter, Nick Smith, etc., they're all gone now from National. And so it's a completely different party. It's led now by someone whose word is a bond. And Winston can work with that. And whenever he signs a deal, he sticks with the deal. And so I think there is a distinct possibility, which is greater than a 50-50 possibility that he'd go with National. Well, there's a large chunk of the population that are like that. And usually they're died-in-the-wall National Party people who have not bothered to educate themselves as to the background behind these things. They haven't bothered to talk to Winston or some of the other players behind the scenes. They're not as deeply involved in politics. They just trot out the party lines. And frankly, it's rather lame for them to do that and to just blindly say, no, don't trust Winston. Well, that's fine. They can not trust Winston. But there will always be around five or six or seven percent of people. They actually will trust him. And one thing about Winston Peters is he's very, very consistent. And consistency is a rare thing in politics these days. And it's something that can be banked on. And I think he will make a play on that. Well, you never know under MMP, because every politician can be made a liar in about five seconds flat during negotiations. But that's the most logical thing that would happen. You'd have the right being supported by ACT. You would have the center being supported by National. And then you would have what I call New Zealand First and Nationalist Party. And they can do some things that are quite Muldoon-ist in outlook. But on the other side, they can be quite dry and conservative, especially on social issues. So I think those three would provide quite a stable government.


So, this is Josephina, she will give her introduction later on and I'm Kai, I'm CTO of Sikinet and CEO of Sikistec and we want to give you a brief view of what we did with confidential computing to harden the OpenStack control plane. And my part will be to give you a short intro on what confidential computing is. And Josephina will give you the details how we did it and this may be the more interesting thing. So I have not much time, what is confidential computing about? It's about security. Okay. I'm done. Do you give me some time, Josephina, to explain more? Okay. Thank you. A little bit more concrete. It's about CIA. What's that? Sounds interesting at least. But CIA is a common abbreviation in the security area for security goals that we want to reach with mechanisms that we implement. It's confidentiality, integrity and authenticity. And this is especially interesting in the context of cloud computing when you have these goals of providers and different stakeholders on the stack of the software stack. So it provides mechanisms and means to secure data, to provide integrity of data and authenticity of data. And so it's a mechanism to provide trustworthiness. And you might have heard about confidential computing in the context of workload protection. This is a common use case where it's used to protect workload against providers. But we wanted to look at how we can use that for the control plane. To be a little bit more concrete, what does it mean to protect data on these three dimensions? And especially also code, not only data. This is a nice distinction, a new paradigm, let's say this way, because that's something we didn't have in the past. We had in the past data-addressed protection. And we still have it, of course. So we can protect data when it's stored on disk, on storage wherever. There are means of encryption and integrity protection so that data is stored securely. We can also protect data on flight so when it's transmitted over the Internet in different ways. So we have VPN technologies since 30 years. We have new versions of VPNs like Vioguard. So the same thing in different ways to encrypt data when it's sent and decrypt data when it's received. So not very easy to make it right. But technically it's known how to make it. But the new thing with confidential computing is to protect data and use. This sounds like magic. How to protect data, how to encrypt data or use encrypt data when it's used when we compute on this data. So we have two general solutions to make that happen. Mathematical solution for that is fully homomorphic encryption, which is a very interesting mathematical principle, sophisticated stuff. It's currently of quite limited use because it's really hard to compute or hard to use for general purposes. So we have some specific use cases. We can somehow search in databases. There are a lot of interesting use cases coming up with homomorphic encryption, but it's not ready for prime time yet, I think. So it's especially not suitable for program code. You can calculate the data, but you cannot protect program code with homomorphic encryption. Therefore, hardware supported means are developed in the past, and especially now in the context of cloud computing, which are, well, differently suited for the OpenStack control plane, especially, but so the technology behind is almost the same in different implementations. It started very early with the trusted platform module, the TPM stuff that was developed also some 15, 20 years ago. And you have technologies, mechanisms, software stacks that support trusted computing. It's called trusted computing architecture these days. So it's specially used to protect the software stack against tampering with. So it's integrity protection mechanism. But it was very hard to manage. So it doesn't have a quite good distribution or usage in the broad yet. And it's, from what I see it, TPMs and TCG, TCA mechanisms are not used that much anymore because it's now involved in the secure enclave paradigm. So step in between, there was a mechanism in the ARM processors, especially called trust zone that was implemented as a kind of CPU in the graded second part, secure part of processing. So also, it was already used for processing data in a secure way, but it was also very limited in its use. So the new implementations of secure enclaves are there in Intel and AMD processors. Intel calls it SGX ARM, AMD calls it SF, SEV. And for ARM, it's coming soon from what I heard. So it's not officially there. And there is a consortium that is dealing with a standardized software stack and APIs for that. It's the confidential computing consortium. And there are a lot of information how it works, how it works on different processors and so on. I brought a slide from Intel here that shows a little bit how it works to make it more visible or tangible, what it's really about. So you can protect data in an application or in a process context with SGX or with this as a secure enclave in a way that data is encrypted when it's transferred over the bus and the memory in the RAM, but it's only decrypted in the CPU. So the CPU itself provides the security boundary to protect the data and the program code. And there is especially a mechanism that goes beyond what we have until now. It's attestation. We can implement mechanisms to verify, to validate that the code that runs in this enclave is exactly a piece of code that we have compiled before. So it's made by HashSums, so the infrastructure behind verifies the HashSums and only if this code is calculated to this HashSum, then the CPU is executing it. So that's a very nice behavior or mechanism to provide integrity, code integrity. And even more, the code and the data when it goes outside the CPU is encrypted. So other processes on the system can look into memory, can dump the memory and look what secrets are or what data is in the memory and mostly program code deals with secrets. And that's where we come to the idea that we could use confidential computing also to protect the open-stack control plane, because there's a lot of stuff inside the control plane. You know it much better than me, especially when it goes about key management and key storage, like Barbican, like Keystone, then it's not so good to have these secrets in the main memory and the RAM of this machine, because then it's attackable. If someone gets root, if someone gets physical access, then it can read out the memory and there is even more attacks like cold boot attacks when you can read out the memory when the machine is switched off even and get the secrets that are stored in the RAM. So we think it's very good to have a mechanism to protect data of the control plane in these sort of endplanes. And it's even more protection against the major attack vector in the cloud scenario, the VM break out when someone is able to get access to the compute node when he breaks out from the VM. And so he has root or even ring zero access and writes and he can do everything on the machine and he can read out the memory and whatever he wants to do. And so these end-clave mechanism is very interesting to protect the control plane even if the VM or the operating system on the compute node is not that secure that we wanted to be at this. So that was the motivation behind and I think it can really help to harden the control plane against this major attack vector on a cloud stack. And finally it's about CIA, confidentiality, integrity and authenticity of program code and data on the control plane. What we did is we started to containerize OpenStack services. This is nothing really new, maybe you already did that or rather did do that but we then started to use SGX to protect the system. This was a joint effort with Intel and Scontain, Intel as you probably know. Scontain is a small company in Tristan area that has a lot of experience with SGX and libraries around that. What we experienced is we failed often on the current technical limitations of this end-clave paradigm and Josephine will give some insights in this pain that we had at some point but I think it's worth to go this way and because this technology emerges we will have more resources in this end-claves. We will have encrypted virtual machine environments in the next generations of the process so this technology will be there in the future and we would like you to build these OpenStack services more end-clave friendly so that we can use this hardening mechanism to make it more secure to run an OpenStack control plane. That was my intro and now Josephine will give you some more insights what we really did. Hi, my name is Josephine Zeifert. I'm a developer at ZeclStack. Some of you might know me as being one of also contributed to OpenStack and normally I'm more directly into the OpenStack code and now I will give you some overview about our case study with Babicam which is on the control plane. So we started with a very, very simple Babicam setup. We had our controller node with our Babicam container, a config file and we have also our life cycle management which we wanted to include and we wanted to use the image updates or the life cycle management for any outdated images and we still had some pain with putting Babicam in an SGX container that was only one part or main pain with putting Babicam in an SGX container or any other OpenStack servers like we also did it with Keystone and we are currently working on Nova and putting that into an SGX container is the forking of the processes which leads to a lot of processes which should maybe be executed on an enclave but that's way too much. So after we got that worked out for Babicam we had two other open questions here. The first was, yeah, what do we do with a config file? I mean, where does the data in the config file come from and how can we protect it but make it usable for rebuilds, etc. And we especially used simple crypto as a use case here because the hardest thing when simple crypto is there's the key encryption key, the master key encryption key directly in the config and that is a wonderful attack vector. And so if we can protect that keg, then we can protect other credentials like database credentials in the config file. So this is the first question I want to talk about and the second is, yeah, we still have a life cycle management and maybe we want to update the Babicam image because there's a security issue. How do we prevent the rollout of outdated or unpatched images and, yeah, scan this and therefore we used scone from scontain. I just give you a short overview about the architecture. Scone consists of local attestation services and configuration and attestation service, which is more central. On every note which executes a secure enclave, there has to be an LAS and the CAS can be central or there can be more than one CAS and stored on central nodes. The local attestation service is just for measuring and testing the local enclaves, as you can see on the left side, it provides a secure hash of the initial enclave state. So just make sure this is everything okay with the enclave on this. The CAS is a little bit more complex. There we can store policies for each service which is executed like Babicam and we can provide configuration like environment, viables, even injected files and keys and that is something we can use for the config files and it also can attest each service instance. So first we took our original Babicam image without being SGX ready and we also used scone to build an SGX-based Babicam image and we did so with also providing a scone file which described the target image, what it should be, what it should go on to the enclave and also to describe confidential properties of Babicam and those confidential properties ended up in the policy which was built for the Babicam service in the CAS and that policy also includes an initial checksum of the image for the image attestation. Now, as we can give parameters rightly into the policy, we go back to our config file and separate the config values between open config values, those which can be stored on every node and can be accessed by everyone, can be adjustable by LCM and it's like the EIP of the container, it's not confidential. And then we have secure variables and therefore we have placeholder variables. Here you can see we replaced the keg with placeholder variable and this is immutable for our lifecycle management and for operators. Then there are two ways to get the keg into the policy there. It is either provided with the scone file, so in a creation or what better way is you can give scone the comment to generate a key. So the key generated is in the CAS and as you can see the CAS and LAS also have a little lock on it, so they are also executed in an SGX environment. So if we generate a key into the CAS as it's stored in an enclave there, no one can access it and when we bring it to a container, when we start it, when we initialize it, the generated key is transferred directly into the enclave of the container. And here we can say the first step when we have a container initialization is of course to build the container, we use our new image and the policy which is stored in the CAS where we get the generated key from and also the hash of the image for the attestation. The config file from the controller node is also read in that part and everything is placed together to have SGX container. Before activating it, the second step is to measure and locally attest the container that is done by the LAS and there are even more secure key management than just providing the keg for the config file. But you can also generate keys for example an encrypted file system. These keys are also transferred at the initializing of the container and the Barbican container or any other container maybe more case for NOVA can have access to an encrypted file system using that key. And every key which is coming from the CAS is reloaded at time for restarts and rebuilds and never saved anywhere else than in the enclave of the SGX controller on the controller node. For the attestation part, we can go into this little example. We had a Barbican image also in version one, which went very well, but then there was a security issue. We needed to fix that image and there was a critical security update and now there's image v2. And because we did that with SCONE again, there's an automatic update for the images in the policy. As you can see, the hash is not of the image v1 but of the image v2. What now happens if we want to start a new container with the old image, then it takes everything, begins to build it, but the second step, the measurement fails because it creates a difference between these hashes and other measurements and therefore it is not executed completely. So it stopped. And then we use the image v2. We have the same building process first using the policy and the image and then the measurement because we have the correct image hash says, yeah, you can go to summarize all of this. The main thing we have now is the policy in the CAS system which is in another sgx enclave. So there we can have key for a potential file system or any config variable which is used in the Babacan container or any other container. So we have that one issue addressed where we want to address the values of the config comes from and how can we use the same value for any rebuilds or any other rollout because redundancy you can use as you see the same policy for a redundant Babacan installation. And it is verified through the hash so you can always run the correct version and there are also some other, yeah, little gimmicks to scone because it even checks your local hardware and looks for the right code for sgx for example and if there is a security breach it does not execute any container but it waits for an update so you have to update first the version of your sgx before you can execute another secure container on it. And that was a lot of, yeah, theory. So now for the demo time. At first I want to show you, you know, our key encryption key protection and therefore we don't even stay on the control or not but we go directly into our sgx based container and grab for that config in that container so anything you can do as an operator. And here we can see we grabbed for the simple crypto plug-in and we see the keg is just the variable. The original keg is stored in an enclave not accessible even from this container out. Now I can show you that it's still working so that we provided a keg. We are going out of that container again and just executing an open stack command, getting a secret and decrypting it and it works. I can get payload and I have protected my key. So that's the first part of this. Now I can show you actually, it's not easy to show you where this key is generated in the CAS because you need special operational keys to access this. I'm not allowed to do it but I can show you the scone file in which you can create it and which you can give the key and this is something which looks like this. There we can see the keg and you can either specify the key as a value or tell the CAS to generate the key at that point. And so we protected that one value from the config. Now I've showed you the config and the next part is the attestation. At first, we still have our sgx based container and we just make a backup image of it, of the running container. This is a new image. Backup done and now we stop the container. We inspect the container and grab the scone config ID because we need this ID when we start the container again, which is done now. There you can see the ID and we specify not the old ID but the backup image, so it's a different image and now we look into the locks. What did happen? As you can see, suspected replay attack and a few lines above you can even read that attestation failed. So even if it's because it's just a backup image but it doesn't let me start it so I cannot even start that image because the measurement is different, the hash is different, I cannot just inject another image from a love cycle. That is the second important thing. Okay. That was everything from my side. Thank you very much. Do you have any questions? Please. You should go to Mike because there is a stream. Question for Josephine. I think you mentioned at one point that forks were problematic with the SGX. So bearing in mind developing enclave friendly applications, what's the problem with forks and are there limits on forks and what can we do to work around that? The problem was when I informed correctly that because there were so many forks later on from the standardised, from the start point which you wanted to put in the enclave that it was problematic, it was too much for that enclave and we had to use or we had to adjust a few things to parallelise this. That was a big thing which did cost us time. There is currently a memory limit in this enclave and if you swap out then it becomes too much too slow. The hardware vendors are constantly increasing this but it's still with a new generation with Ice Lake, it's still limited in some sense. It's not unlimited as you work outside the enclave. It does need some care how many forks you do, how many cash you use or whatever. But that's something I think we should summarise in some sort of do's and don'ts and put it on a website or wherever to help to develop enclave friendly services. Can you go also to the mic? Have you looked at any other services, especially those that use root wrap or any privileged escalation to run at root level to set up neutron, set up networking things and what the limits of your approach are to just protect the software but also make sure it only does things that it's supposed to do. We are currently actually going into Nova and trying to put Nova into such containers and yeah, this is currently something we are working on. So as far we had Babacan and Keystone they are done. That's working on this one. They are the most lightweight ones so you wanted to test the two questions here and that was it. So what is the strategy of secretary type on addressing latest spectrum issues for example branch history injection which was discovered quite recently. So are there some features in the software development like you used the chopper points or do you just rely on the restrictive speculation litigation to develop? I can comment on this.  Period. And you won't get rid of it completely in a shared environment. So I think we are working now on more sophisticated attacks. When we look back at spectrum meltdown this was really a disaster but now it's getting better. But it's also getting slower you know. So you always have this trade-off and I think it's not a like white solution you can separate workloads if you want to get rid of side channels on different machines. This is usually done with the automation mechanisms in OpenStack but well it's overhead of course. We also use these mitigations of Intel and we work by the way we work quite closely together with a company that discovered meltdown and that has very close or very detailed knowledge about virtualization and side channel attack protection so we also look at how we could improve the hypervisor to protect better against side channel attacks. But that's a long story. So the contain toolset is not for free so please address them that they open source it. We would like that but it's their business model by the way but it's only a way to easily use SGX. You can do it step by step. There is a ton of documentation how to use SGX and do it yourself. There are also open source in the field to use SGX but that's the enablement of SGX different ways to use it. The way we combined it together is more a kind of configuration so that's not well an implementation work but a configuration and deployment work that we did together with our lifecycle management and we integrated I think with Yauk already so that new lifecycle management based on Kubernetes is able to deal with that sort because it's containerized this way and that way. So it comes together at some point but if you want to test yourself just connect to us and ask how we can help you. Okay I think that's the time is up.  Thank you very much.


You know, with Kyle and Taekwondo and IR who will have to step up in their respective spots for you all? Yeah, so obviously both those guys, kind of what I said on Monday, I didn't expect them back in the short term, there's still some things that we've got to figure out. But that's the new IR rules and so many of everybody's read up on those. It's different than IR used to be, right? Where, you know, example in 07 when we had Randy Thomas towards tricep and carried him, basically carried 52 all year because he put him on IR as you remember D-Led. Yeah, all year. So the new rules, I think certainly help. There's just still some unknown, right? As they continue to get medical advice and, you know, both those guys will have procedures and you really won't know until after those procedures what the timeline truly is. So, you know, that won't be out there for the next four games. That's what that does right now when you put people on IR. You know, we've got five spots left to return, so the season plays out. As for your original question, again, what I talked about on Monday, I mean, it's our job as coaches to adapt and evolve. Every team's dealing with something. You know, we've got the right guys out there and guys that can play multiple roles for us that have done it. You know, with Pruitt, Hesse, Thurk, Felipe, we can also Morph and Keith Smith. I mean, there's a lot of things we can do to manufacture things in different personnel groups and obviously our wide outs and CP and Avery. So we've got a lot of options. Obviously, you'll never go one for one with a player, but try to find different solutions. The fact that they're both younger players and both seem to have potentially big roles for this franchise for a while. Does that play into it, too, in terms of usage versus not one in terms of maybe bringing them back and maybe where you guys stand at that point in the year? Only time. No, Mike. I think the only thing if you go with this, this is your compass. You do what's in the best of the players' health first and foremost, regardless of what year they're in the league. And the only thing I think that would come into play if you got a guy that's in the last year of his career, maybe he decides they all hold something off. I would never, if a guy was in the seventh year or second year, I would never advocate somebody doing something that wasn't in the best interest of their health. So that's the best way I can answer that. I understand what the angle you're going to have with that. That's not, you know, those are hypotheticals and great, great, you know, social media debates, but that's not. If you go with a compass, we'll always do what's in the best interest of the players' health first. That's where we'll go. Well, I guess I was meaning more, not necessarily pushing them back to the field, but the opposite direction of, you know, four weeks from now depending on where you guys are. If it's like, hey, you know what, maybe don't, where you hold and say, listen, you have a long career ahead of you type thing. I was looking at more in the opposite direction. So you're not conceding things? No, not conceding things, just like how that plays into it, maybe where you guys are at that point. I mean, I know what you're trying to ask. Look, go back to this. We'll always do what's in the best interest of the players' health first. It's pretty simple. Thank you. You just got to tie in. I believe Parker is actually second and snapped and routes were on, but my call for it was, was your next guy up on Sunday. What has he done that fits him in that spot? Well, a lot of different things. And it's not one for one. I mean, again, we can go out there and play tempers now. We can go all one. We can use CP where we want to use Avery. Like there's different ways to manufacture things. So it's never one for one, but, you know, certain things, they all have unique skill sets.  Parker at the point of attack in multiple schemes. He's got a good feel in space. Smart football player, multi-sport guy, played a lot of big games. You know, the one thing about him at FERC, they played in, you know, AFC championship games. They played in playoff games and they got some good experience. And we'll just see how it plays out as we continue to put the game plan in the rest of the week. You mentioned a couple of days ago your appreciation for interior linemen. I think this game will feature with Grady, Allen, and Deron Payne, the three defensive tackles who played the most snaps in the league so far. What does it say about guys play a lot of snaps? Have that endurance in there? So there's a lot about them. Josh, you know, you're talking about three of the better interior players in this league. And with different skill sets, but both of them are presented. But obviously Grady will have, obviously, the utmost respect for and has become the leader of this team. But when you talk about Payne and Allen, I mean, they're hard to block. They play the run really well. They're powerful. They got good counter moves as they assault the pocket in different ways they rush. You can see why both of those guys were first round, you know, heavy investments for Washington. And you got sweat playing out there. And they got a lot of bodies they throw at you guys that are playing well. See what it looks like if young comes back out there. So it's good for them. Probably the way he trains is unique. You know, sometimes it takes a little bit of luck, you know, things that you can't help that happen in there like what happened to TQ. So it's luck. But really at the end of the day, it's it's the way he goes about his business day after day, the way he prepares and trains. In terms of, I know I feel like a weekly question does that are on IR and you know, one of the coming back today that hasn't practiced yet. And as far as your left guard situation, you've started four different guys there in the last four weeks. We had to write it is she was still your guy there. Do you is Colby played well? So is that possibly Jalen there? That's the other ways the rest of week goes. But I thought she might play pretty well. Share personal conversations with us that you have with players, but could you tell us how? How it's reacting to the news of the century? I don't have any kind of dramatic story for you. Kyle, Kyle's a, no, it's like the conversation we have with every player. They remain private. All those guys, they put on the line for us. Whether you're Kyle Pitts, you know, or Jerry Bernhardt, all of our players, you know, we try to do what's best for them. And I'll always keep our private conversations private. Coach, what are some of the challenges that the commander's offense puts on your defense this week? Yeah, they got a big, heavy offensive line as well. You know, they've been running the football pretty well lately this last stretch. They've kind of turned the corner. A lot of talented wide outs, you know, the guys play multiple spots. The way they get the ball to Samuel, obviously Gibson. Robinson's been running the ball well for him. McLaurin's a terrific player. They had a, I mean, they, it's a really good roster. And Heineke's doing a nice job delivering the football, keeping plays alive. Tell they got a lot of confidence in them. But it's a veteran offensive line, playing multiple guys at center. But they, they're heavy handed and we know it's going to be a challenge because they will get downhill on you. Both of us backs will. And as you went back and looked at the Chicago game, you offensively, defensively and special teams, you played pretty well. Having all three phases, obviously you wouldn't want that this week. But how do you build upon that? Yeah, every, every week's, I mean, it's a new challenge, you know. You know, you sometimes, sometimes you'd hope you could build confidence, but the plan will be completely different. You know, we've got to defend something completely different than we did in Chicago. It's a different scheme in front that we'll be playing. Different special teams, schemes a little bit. So that's always the challenge. It's a fun part about the NFL is, you know, obviously getting to understand the opponent you're playing, understand the schemes and they're probably going to try to attack you, understand that you're going to have something new and what they possibly they're going to adapt to something at some point as well, especially if something's working for you. So that's the challenge we can a week out and it's just so different. You know, the way Washington is built, but they're playing really well. It's a big game for both teams and we're excited to be a part of it. Zacchaeus and Bird have both been very efficient. Is there a certain skill set in being a second or third guideline and the way you play when you don't get as many targets? You know, you have to approach things differently. It depends what your offense is, what your game plan is, how the game's going to be bad weather Sunday. So whether our plan is to want to throw it 45, 50 times, that was the plan. You may have to alter that because of the elements and the way the game's going. So I've never looked at it as RB1, wide receiver one, T1, whatever the hell, you know, people use out there. We've got an offense and the 11 guys we get out there, regardless of personnel and scheme, we expect to produce. So if the ball comes their way, opportunities obviously are running a lot. You're not going to get a lot of attempts, especially, you know, if you've got a lead and but those guys do a terrific job and they've stepped up in big ways all year. Birds made some huge plays for us last month or so and OZ has been solid since the day I got here. So we're happy both those guys on our team. Will Compton announced that he was going to sign with you guys and then... Yeah, I mean, look, I'll talk about people that are officially on our roster. I'm sure Will is a legion of fans will probably update. You get more from Will than you would from me. So I can, somebody's officially on the roster. I'll be happy to speak more about it. Yeah, Coach, you talked about the outside line better than Troy was mentioned to in his row. Just want to check in with you and see how he's coming. I just went over all their numbers and got over 800 snaps out of those guys. Yeah, all those guys, I mean, they're all, they play different roles for us. They've all had an impact. Very pleased with all those guys. Again, they're different depending on the week and the scheme, what's in the game plan, but all of them contributed not only in just on defense, D-Led, but they've made some big fork down in special teams place for us in the coverage game. So we'll just see how what the plan is this week. But all those guys, they continue to improve and that's a good sign. How's Troy doing instinctually because, you know, he's played so many different places. I don't know that the linebackers have an impact. Pretty good. You can see that obviously made some big down plays for us on Sunday, you know, not just defense, but in the return game at a big block with CP's record return. And he's obviously had the pump block early this year in LA. He's got close a couple other times. He's had an impact on a lot of spots for us. You mentioned this being a big game for both teams. I'm sure, you know, a lot of people didn't think through 11 games. People would be saying that about your team. What can you say?  How do you feel about where you are at this point? Well, I mean, we're in the mix. So obviously you want to be undefeated, right? That's the objective. That's not the reality, but that's your charge at one every week. When you get to this time of year, you get into the holiday season, you get into Thanksgiving. Making a push in December, you want to be in games that matter. So this is a big one for us. However, we got here. Again, we'll see what it looks like at the end of the year, but we're excited to be playing in a game that matters. Sunday on the road against a good opponent, really, really talented roster. See what the crowd looks like Sunday. Hopefully it's a good environment for fun games to be a part of. This might be a very... I always love when you phrase it that way. I know you do. I mean, Washington's field has always been known as kind of tricky, maybe. I mean, you coach there as well. Do you have to prep or talk to guys a little bit more because a lot of these guys now haven't necessarily played on their field? I mean, it's every week, Mike. It's a good question because you got to understand the environment you're going into. Weather a team like Carolina changes from grass to the turf. Weather is always a factor. If you play in certain places like last year when we played up in Buffalo, obviously the weather was an issue. Yeah, you try to educate about the environment you're going into. You can't simulate everything. We don't have a snow machine when you get ready to play Buffalo. Like I said, we all know that the weather can change, but if it's going to rain on top of that, yeah, certainly. You know, they put a new surface in recently. You got to make sure you got the right gear, right? Cleeds, right equipment. That's it. Come on, Josh. You got nothing. It's a short wake. We're compressed here. Yeah, that's good. All good. Thanks, Kevin.