Elle était une étudiante de plein d'ingénieurs en France. Elle a eu un maître d'école polytechnique et d'un PhD de télécomparie. Durant le PhD, elle a étudié différents attaques statistiques sur les chiffres symmétriques. Elle était l'une des 4 fondateurs de la team de la sécurité et de la cryptographie de Jean Plus. Elle a ensuite étudié aux États-Unis et a travaillé pour la recherche cryptographique. Elle a été le directeur de l'IECR. Maintenant, elle est la technologie sécurité de la fédérale d'Altrombos. Elle est responsable pour de nombreuses activités de recherche, incluant crypto et PASQuANTUM crypto, pour analyser la surface et les mesures de contente et la structure de sécurité pour nouveaux produits et services. Alors, elle a récemment pointé une personne pour les 5 risques. Le Comité de Sécurité Fondation de la Fondation et elle va présenter un travail dans ce comité. Donc, s'il vous plaît, joignez-moi à Eleanor. Merci beaucoup pour cette introduction. Je vous souhaite que le micro soit en train. Ok, bon, merci. All right, so indeed, my name is Helena Hanchou and I'm a Rambus Security Technologies Fellow. I'm also the RISC-5 Security Standing Committee Chair and it's my pleasure to chair that committee because it is security related and that's one of the topics that we like to work on at Rambus and that this community likes to work on as well. So let me try to give you a little bit of an overview of what RISC-5, the foundation does and how that relates to security and what the security committee is trying to do as well. Okay, does that work? Yes, perfect. So here's a little bit of the outline of my talk. Just a sec, so I know how much time I have. First I'll try to say a few words about the RISC-5 foundation itself when it was created and how it started working, what the current status is of the specs and stuff and then I will talk about the Security Standing Committee creation and its charger and the task groups that we currently have that work on security. I'll say a few words about some DARPA activities that some of us in the foundation have which is not directly related under the umbrella of the foundation but still related to the same topic. I'll talk about the speaker program we have mentioned some academic and industry initiatives around RISC-5 and then maybe some open problems and research directions that you might be interested in hearing about that you might get interested in working on and hopefully you would then join us and to bring the work to the foundation as well. All right, so first things first, RISC-5, pronounced RISC-5 is a free and open instructions at architecture enabling a new era of processor innovation through open standard collaboration. That's the official line of the RISC-5 Foundation. It was founded in 2015, so for about four years ago. In the meantime, it already has more than 300 members. This includes both organizations and individual members. As an individual, you can also join the foundation and have access to the specs and work on everything if you'd like to. It's open, it's a collaborative community of software and hardware innovators so both sides are being looked at. The base, ISEID, itself, was born in academia and in research. It was put together by Berkeley and then given into the foundation. It's a new level of free, extensible software and hardware freedom on architecture. We hope to be paving the way for the next 50 years of computing design and innovation and as I said, members of the foundation can have access to and participate in the development of the specs, of the extensions and all the related hardware and software developments and ecosystem. Recently, somebody told me, when you make slides like this which are full of words and you have to read all of that, nobody really understands anything, so you should highlight what you wanna say. Okay, so let's go. There we go. It's free, open, open, free. Lots of freedom and the website is here. Okay, so that's risk five. Let me give you a few words of intro on what the basis for the work is here. So the first thing that was worked on was the risk five instructions at manual. It has two volumes. The first one is volume one called the user level ISEID. It was mainly edited by Andrew Waterman and Krister Azanovich and the version, the most recent version that was, the first version that was brought into the foundation was version 2.1, 2.2, sorry, in May of 2017. It was drafted in May of 2017. It's a Creative Commons attribution international license so you can use it, open three. And it was originally derived from a version 2.1 which was written by Andrew Junsuk, David Patterson and Krister Azanovich. So what does it actually contain and do? Well, there is first of all a base instruction set architecture. So it has different sizes, register sizes. You can work on a 32 bit version. You can work with a 32 bit embedded version which has a slightly reduced version of the instruction set. 60 full bit and 128 bit. And then on top of that, we have so called extensions. So there's a number of different such extensions that are being worked on. One of them is called, they go by letters. So one of them is called the M extension which is for multiplication and division. Another one is called A for atomic instructions. Then you have a few different ones on floating point operations. So single precision, double precision, quadruple precision and decimal. You have a compressed instruction set extension.  One of them is important for us specifically for cryptography. One of them is called vector extensions. All right, so this is the first version that was contributed. And now what happened next, move forward, fast forward a little bit from that first version is that about two months ago, in June, on June 8, this first volume one user level ISO was ratified by the foundation. So it's now a stable ratified adopted specification that everybody can use and is officially promoted by the foundation. So the difference between the ratified one and the previous one, let me show you what it is. First of all, there's a little bit more work that went into it in the last two years. Most notably, it went from 145 to 236 pages. So a lot of more stuff. It does show the ratified parts and it has additional extensions. So this is a little bit small. You might not be able to read it completely but if you look at the spec on the website, you can see the ratified portions. Some of the extensions have already been ratified. The others are still being worked on. So they are called drafts. One of them, the one that we're interested in, the V extension you can see is still a draft. So that makes Rich over here very happy because every time he wants to build on it, he has to go back and look at what they changed last week. But it's progressing in parallel. We're working at the same time. And so we're trying to get these things towards ratification as we go. Then there's the second thing that has been ratified at the same time as the base level ISA, which is the volume number two, which is about privileged architecture. So the first one is the user level interface. But below that, you have levels of privileges that certain, where you have certain permissions and certain rights that get executed at those levels. And this is what the second volume talks about, which was ratified at the same time. It was edited by the same people, has the same license attached to it, all that's the same. And what it does show is the following. Sorry. It does define three different modes. In addition to the user mode, it defines the machine mode, which is the lowest level, which is very close to the hardware, which is usually implemented in hardware. The supervisor mode, which can be done in hardware as well, but you could start being able to go into software a bit more. That depends how your architecture looks like. The hypervisor mode, and then finally the user mode, which is in the previous volume. So far, we have two modes that have been ratified in June. This is the machine and the supervisor mode. And the third one, the hypervisor one is still in draft. So you can still contribute and make comments and provide feedback. And if you join the foundation, you can work on getting that towards ratified as well. All right, so three modes here, plus one user mode. This is what we have so far in the foundation, as the base for everybody to work on. All right, so I usually get the question, but okay, this is great. This is paperwork. Do you guys have anything for real? Yes, we do. So on the website, if you go on the RISC-5 Foundation's website, you will see a list of 65 cores that people have been working on. And I'm sure there's more out there, if not all of them are listed here, then please let us know if you're working on this as well. Give us more references so we can list them and give people pointers to your work. But here you will see 65 cores that are already available. Many different companies are working on them. There's cores by companies such as Andis and Sy-5 makes them available for you to use. And Microchip has some, there's plenty of different companies and there's also universities. Etihad Surich, for example, has a few of them that they built. MIT worked on them, Berkeley worked on them. So plenty of things to play around with. One little side note here. None of these have passed the RISC-5 Compliance Suite yet. And this is for a very simple reason because this Compliance Suite is still in development. So it's a little bit difficult to have already passed something that's not completely finished. We're working things in parallel as soon as the Compliance Suits and foreign aspects have been finished and ratified and everything, then we will start being able to have the cores pass those suites as well. All right, so a bunch of cores available. The other thing that is useful as well, useful to know, is that you have a number of tools and software associated to RISC-5 available that is listed on the RISC-5 website as well. So, for example, if you look for simulators or debugging tools, compilers, spootloaders, OS and OS kernels, compilers, you name it. All of that, you can go on the website, click on the link and see what other people are working on, what they've put on their own websites and you can, some of it is open and free, some of it is more commercial, but you will always find something that's useful to be able to work on. And very new to this environment, we also have a link now on that website for security software. There's not a whole lot yet there, but I've listed here in the little square the two things that have been posted there since the last month or so. So, one company called Hex-5 is working on an SDK there and I'll come back to that on what they do. And the Keystone project has posted their Keystone enclave there, so you can go and look at that as well. All right, okay, so this is globally what the foundation does, everything that you have access to that you can look up. Now let's get to the real topic which is RISC-5, how about security? What about security? So, let me go back in time a little bit and talk to you about January 2018. January 2018, Spectre and Meltdown, that was the oops moment. So, suddenly people working on processors realize there's something there that shouldn't be there. Namely, if you look at speculative execution, branch prediction and all these things, you suddenly realize that you're leaking information through, for example, cache timing side channels because you're trying to speculate about something that will happen in the future. You start looking at data that you're not supposed to be looking at because you haven't computed the previous result yet, yet you're already looking at something that you shouldn't be looking at.  And so, this was a big realization for the foundation saying, oh wait, we are working on open free processors and there's this thing going on whereby other processes are being greatly hacked and broken by these side channel attacks, a new form of side channel attacks. What shall we be doing about this? We need to do something about it. All right, so, this was exactly what led to the creation of the security standing committee, which I have the pleasure of sharing. So, this happened around July timeframe and by the time we got our publications together and knew what we wanted to work on, it was about July and that's when the security standing committee was announced. So, July 2nd, press release, Rescribe Foundation announced the security standing committee creation calling for participation. So, I had said back then, apparently, that security is one of the fundamental issues in our connected world, it's told too, and that we would like to address existing and emerging threats. And Joe Kinnery, which I will come back to as well, was talking about the event of a new compute platform that has formal methods at its foundation for processor correctness and security. So, it's all about proving and formally assuring security during hardware development. How do you make sure that you can formally say my design has these properties and prove it? Okay, so, this standing committee has been created about a year ago and has been working on different things since then. Let me show you what the mandate of that committee is when it got created. So, this is compared to other committees in the foundation. This is a permanent committee. The non-permanent ones are called task groups, and I'll give you two examples of what we're working on. But this one is a permanent one. So, the permanent one looks at things that are going on in the security world. What should we be working on? It can recommend, for example, to create task groups which then go and write specifications, specifications, drafts that then go towards ratification. It is meant as an ideal vehicle for the security community. So, this community here, it liaises with other committees inside the foundation but also outside the foundation. So, for example, we're starting discussions with global platform as one of them. We might be talking later on to TCG and to FIDO and other committees like that to see where we intersect and how we should be working together. We have a mandate to create an information repository, a new attack trends, countermeasures, and stuff that's going on in the world of security that is important to the foundation and that people should know about. We're identifying top 10 challenges and security for the risk-buy community and I guess very top, top up there is all about side channel attacks, the new version of it, I would say. We do propose task groups, as I mentioned. We are here to recruit security talent, so if you're interested, please join us, work with us. It's a lot of fun, it's challenging, not easy at all, but it's a lot of fun. And develop consensus around best practices for maybe even the smaller devices like IoT and embedded systems. Okay, so mentioning task groups, we already have created two task groups that deal specifically with security. One of them, the first one, is the cryptographic extensions task group. This one is chaired by Richard Newell from Microchip, sitting right here. So if you have any questions, please ask him. The vice-chair that has recently been nominated and approved is Derek Atkins from Secure RF. And these two great folks are trying to get us some crypto extensions on top of the vector extensions. So the charter that is proposed in this task group is to build extensions on top of vector extensions that would be useful for cryptographic algorithms. The intent is to have a base and an extended version of that. The base one would have low cost instructions for acceleration of the most traditional and common algorithms. And the more evolved one would have greater functionality. There would also be reserved encodings for other types of algorithms, all sorts of types of algorithms because there's a bunch out there so that we can get better security performance out of it. It includes both symmetric and asymmetric algorithms in its mandate as well as other primitives related primitives such as hash functions, message digests. And the committee will also at some point be looking at random numbers and secure key management. Now remember that the foundation works at the instruction set level. So these kinds of committees do not define how you actually do, for example, generate random numbers, but it defines how you build your random number generator into the system, how you have access to it through the instruction set. Is that right, Rich? Okay, so remember that you stay at that level and don't necessarily look at how it's being implemented at the hardware site. Okay, so a little bit of status update on where this task group is at. Right now it is working on AES instructions for three key sizes and that's done. The SHA-2 instructions are being looked at for both 256 and 512, which is almost done pretty close. For both of them, there is one solution that lets you do a one round approach and a full round approach for AES and the SHA-1 is a 16 and a full round approach. So the solutions are being worked on and are pretty much done. Now we're in the step of needing to convert that into official specs. So we know how we wanna do it. Now we have to draft the specs and then get the specs ratified at some point. The group has also been looking at prototyping public key algorithms on top of the base instruction set, so looking at how to do long integer arithmetic and there is an implementation proof of concept that was looked at, so just to make sure we can do it and it's available and it works. And some future directions here are the more lightweight approach maybe to this entire thing. Remember that this is based on vector extensions, which is quite a broad set of extensions. So one possibility would be to look at maybe just a subset of the vector extensions to make it lighter or to completely remove the vector extension dependability and just include some smaller instructions for that instead. So there's an approach that was proposed very recently by the University of Bristol called Xcrypto which proposes scalar instructions, rotates like smaller style instructions to have the software, the crypto software run faster and Bristol has recently joined the foundation is now part of the discussions to see how we could do all of that together. Sorry. And I'm hearing that Tilly Comparitek also expressed some interest in this kind of research. If you're working on things like that, if you wanna talk to us, talk to Rich, please do so, join the foundation and come work with us. All new ideas are really welcome. All right. The second one, second task group we have currently is one that is looking at how to build a trusted execution environment on top of the RISC-V architecture. This one is led by Joshi from NVIDIA and Nick Cosifidis from FORTH. And what they're trying to do is really define an architecture spec that will support trusted execution on top of RISC-V processors. So they are looking at providing implementation guidelines, recommendations and to develop kind of the components that you will need to have a TE available such as compilers, simulation models, hardware, software components. Because you built up, it's a bigger system than just the processor. What do you need for that? What is mandatory for that? What is necessary, sufficient and so on. So in terms of where they are at, currently what they're looking at is that the first thing is a PMP model that they defined, physical memory protection. It is based on the privileged spec on the latest version 1.12. They're also looking, same thing, how to securely divide up the memory and how to protect it securely at the outer limits. So that's called the IOPMP. It's a proposal stage version 0.1. And as a next step on the hardware side, they will be looking at control flow integrity extensions. What can be done there? On the software side, the work that's being done is a secure monitor architecture. There's a document being put together on secure boot architecture. So you recognize all the traditional notions that you have around trusted execution. We're trying to architect and formalize that. So the first secure boot architecture has signature verification as a basis and then some optional extensions for further on for key management, inserts, revocation, attestation and things like that. And the other part that's being worked on and looked at is the TE APIs. So an API to the other parts of the system. For example, between trusted applications and the US, between two trusted applications, how do they talk to each other? How do you attest a trusted application? How do you talk between a trusted application and a secure monitor, et cetera? So all of these APIs are being looked at and discussed and debated and hopefully drafted and standardized at some point. Oops, sorry, everybody awake now? Okay, so on a slightly different note and subject, there is another activity going on which is not directly under the umbrella of the risk by foundation, but very deeply related to it. This is driven by Joe Kinnery from Galois. He is also the vice chair of the security standing committee. And he's involved in a lot of different darker projects, one of them being the SIS project and I forgot what the acronym means, but S is probably security and then the other S and H are software and hardware. So they're looking at how can you build secure systems? How can you kind of model secure systems with security properties and how can you reason about them? How can you formalize that and then prove that your system is secure? One of the things they look at is a formal spec language for hardware design called Lando. And this one has four sub languages, a system spec language, an architectural language, product line engineering language and a security property language. So you can specify what your security properties should be, what they should look like and then you can reason about it and you can verify. That's the work that they're doing. So not all of this is public, not all of this will be public in the future, but as DARPA allows Galois to publish some of this, it will become available and they will contribute it into the RISC-V Foundation as well. They're also working on a domain model for specifying security properties. So for example, they've started by formalizing the NIST CWEs and among those mostly the ones relating to buffer and memory errors. So this is all going in the direction of formalizing vulnerabilities and checking that they're not there in your design. And again, as these things become publishable and DARPA allows to publish more of it, these will get contributed into the foundation and everybody will be able to look at it and use it. Along the same lines, they're working on a tool suite that's called Bespin for formal reasoning. And a sub-system of that tool suite has already been published and made available to the RISC-V formal group. This part is called GRIFT and it stands for something like Galois RISC-V formal tool or something like that, close. But it's a part of this larger system, tooling system called Bespin where you can use the tool to formally prove things. And finally, they work on many different things but the ones that are interesting for the RISC-V foundation are the ones around platform specs and security-enriched ISAs. So what they've done recently, I believe it was at DEF CON this month, they have started showing a secure voting machine platform spec, which has certain security guarantees in it. So it's meant to be open for public review. It's meant to be offered as a game to go against and to try to attack. It's a voting machine so everybody knows that the state of voting, secure voting machines is an interesting state these days. So this is an attempt at trying to make a secure one if you can go and try to hack it. If you find interesting results, please feed that back to them. We will incorporate that, they will do that and then incorporate into the platform specs as they go and build better systems. It's a bit of a hackers and builders game. They're also working on six other platform specs based on RISC-V SOCs. The six that they're looking at are Rocket, Boom, Piccolo, Fluid, Bassoon and Risky. If you've never heard about this, go on the website and look at them. These are the ones that are mostly being worked on by MIT, Berkeley, Etihad, Zurich, I believe, and then there's two, the two others, I don't remember which institution proposed them, but they're like very open, you can look at how that works. And later on, hopefully, we will see some of the platform specs being published as well as DARPA gives authorization to do that. Okay, so this is the kind of more formalization security proof approach in hardware design that this part of Galway is working on. Okay, so we also have a speaker program in the security standing committee. We have so far invited a number of people as we went. Remember, we have about one speaker per month average, I would say. We alternate between a business meeting and a speaker program in the committee meetings. So this means that every other time we have a guest and every other time we talk about, okay, so what's new in the world? What should we be looking at? Is there a new task group we should be creating? What should we be doing? Okay, so the speakers we've had so far, Gernot Heizer from data 61 on timing and tax and an augmented form of the instruction set. And I'll come back to that a little bit later. We had Dayali from Berkeley on the Keystone project. José Renaud Esperanto on timing, attack, mitigation ideas. You can see that most of the topics are around how do we get rid of these annoying side channel attacks. John Giger was talking about TEs and what these things look like. Nicole Fern from TortugaLogic has been presenting on security oriented verification tools. It's kind of a tool that allows you to check at the hardware level whether some of the security vulnerabilities that you would like to avoid are really not there. Daniel Genking has been talking to us about foreshadow. Stefan Mangat and his team have been talking to us about specific security ISA extensions. I'll say just a couple more words about that later. And Ben Marshall, I already mentioned him from the University of Bristol, has been talking to us about his ex crypto extensions to the ISA so that faster crypto can be built. If you would like to give a talk on risk five security topics, your name goes here, please come talk to us. We can set up a time for you to talk to the group. And then we can talk about the topic that you'd like to present. So we're trying to collect all the information about people, institutions, academics, organizations that are working on risk five and security so that there's kind of a little bit of a centralized information repository about all these initiatives. Okay. If you, other ongoing security initiatives that was independent from the RISC-I Foundation, again, there was a security contest but it is related to risk five. So I wanted to mention it. There was a hackathon at DAC last year where a group of people have organized kind of a hardware bug hunting. And because risk five specs and everything are open, they chose it as a platform that was easy to implement fake bugs into if you want and then give them to everybody to go off to try to see if they could find them. So they had a systematic bug construction approach for bug hunting and along the way, apparently, they also found a couple of native bugs in some of the risk five processors. So open and available to everybody does not necessarily equate security. It helps a lot. It's a good starting point, but there can still be issues and bugs can be found. So this is something that we should also keep in mind. And you can go online and check it out and ask them what kind of bugs they put in there for people to hunt after. Another ongoing security initiative is still in the same area. Security contest, this is all new. And again, if you're interested, please talk to Rich. It's being run by TALIS and Microchip. It was announced on July 15th. It's a sort of hackathon. They're looking for open source submissions on a Microchip FPGA where you propose a construction with security countermeasures. It's based on Zephyr where you're allowed to make a limited number of changes to the compiler. And the deadline for submissions is September 15th, so hurry up. And the idea is to try to come up with a security implementation and a security proposal that will protect at least against the five classical, very classical attacks which are listed here. So it's about corrupting function pointers, buffer overflows on the stack, corrupting function pointers, both on the heap and the stack, and things like that. So if you have a proposal, please submit it to the contest. It's supposed to run on the Microchip FPGA and TALIS, I believe, is someone that will be assessing security on it. All right, a few more initiatives. On the academic and national labs side of the world, we have mentioned already, but I'll mention them again. The University of Graz is working on extensions for security, mainly around trying to counteract side-champ attacks, control flow integrity, and trying to work on secure memory access. So they built extensions for that, and I believe all that work is pretty much public. So you could either talk to Stephan and his team which is sitting somewhere in the audience as well, or you can look up their papers that they've published already. The University of Bristol, which I mentioned, ex-crypto extensions, and Telecom Paris Tech also expressed interest. I don't know that they have published papers yet, or if they have, please send them to me, so I can listen here. But there's interest there as well. Another initiative that was presented at the workshop in Zurich this year, earlier this year in June, was from Seu Aletti. They're working on a secure processor with essentially everything authenticated and encrypted in there. So all of the resources are essentially secured, functionally secured. Buses, bus access, buses memory accesses, data path, instruction path. Everything is nicely authenticated and encrypted. The slides are online at the Zurich workshop. You can go online and see it there. They've, I believe, also published a paper on it. They will be giving a talk, hopefully to us later this year, but not quite ready yet. But okay, it is not super fast, obviously, if you encrypt and authenticate all of these lines, but it allows for a very secure implementation of a processor if you have applications for that. A couple more initiatives around secure enclaves, based on risk five. One of them is called Sanctum from MIT, and that is a basis for the Keystone Project from Berkeley as well. They're slightly related. There is another initiative called Open Titan from Google, with five base as well. There is, remember, at the beginning, I had a slide on security software stuff and Hex 5 was mentioned there. So what they do, what they propose is a multi-zone TEAPI, and that one's available for you to look at and review. So they propose a way of having multiple different secure applications run at the same time, or at least on the same platform such that they can't kind of attack each other. We do have a few initiatives as well, so if you wanna hear about our Crypto Manager root trust, you can have a look at the demo next door over coffee or lunch. And Joel Wittner, who might be still sitting here in the audience today, he says no, he says yes. Joel is sitting here. He gave an invited talk yesterday at FDTC. He could tell you all about how to run mutually distressing applications on a RISC-5 embedded platform such that they can't essentially attack each other. We also have an initiative going on. It's not a secure enclave, it's just a processor here, but initiative going on, which is DPA-resistant, DPA-resistant RISC-5 CPU, by Mike Hutter, Elke de Mulder, and Samata Gummala, and this has been published and talked about before at the RISC-5 Summit last year, as well as an invited talk at DAC this year, earlier this year, and next month, there's a Lawrence workshop where Mike Hutter is probably gonna say a little bit more about that as well. Some of them are in the audience as well, so you can talk to them about that, okay? All right, so these are kind of the initiatives that I wanted to talk about a little bit on what exists today. Everything the foundation does, all the task groups, the things that are either commercially or openly available that you can play with, software, ecosystem, and all of that. Now, let me, in the last few minutes of this talk, maybe talk a little bit more about what still needs to be done. Remember that a foundation is a standard like a standardisation organisation, and so it does advance at a certain speed. It doesn't go super fast, but it does steadily advance. So if you wanna contribute, please come and help us. And these are maybe some of the topics that we still need to work on. Okay, first one, big question is how to mitigate micro-architectural flaws. So what we found out over the past year and a half is that beyond the original side channel attacks we talked about 20 years ago, which was DPA and EMA and all of that, differential fault attacks. There is another complete set of side channel attacks. Some of them yet to be found that will, is gonna hit processor manufacturers and developers as we move forward because there's so many things still to be found. So the question is how do we really try to counteract these, because most of these happen at the micro-architectural level. The foundation is working at the instruction set level. How do we make sure that we can specify something, help people understand how to build better systems without necessarily completely specifying what works at the, what is done at the micro-arch level? So that's one of the big questions that we're trying to tackle. We've started discussing that we couldn't necessarily do it at the ISO level, but we could describe platform specs which go a bit further and would give you some indication and some hints of how to add special instructions that would help mitigate some of these things. So that's kind of the direction we're trying to go. So how do we do better than proprietary micro-arch? How do we publish more, explain more, yet leave the actual implementation free for the implementer and the organization to do whatever they want? So we specify one level and what comes below is open to anybody to do what they want. Big question. Some ideas on how to mitigate these have been proposed by people that have written papers about it and have published about it. So here I'm listing a few ideas and directions that have been proposed. Now we're trying to look at how do we build these ideas into a platform spec? How does that work? So Gernot, I mentioned him before, has looked at something called the augmented ISO. He proposes a way of adding cash flush instructions into a system as well as trying to partition the memory in ways that different processes cannot access each other's private information. So it's a little bit difficult to build, but that's one of the directions we're trying to go. José Renaud from Esperanto also had some timing attack mitigation ideas in there. He was going down a bit more the path of kind of adding tags with security classifications to your elements so that you could kind of give some security property to each of them and follow the properties through the flow. And recently at the secure enclaves workshop in Berkeley last month, c'est-à-dire, sorry, it was this month, Chris Fletcher from the University of Illinois proposed something called speculative taint tracking, so which is again some idea of tainting registers and defining corresponding update policies such as if one register is tainted and you mix it with one that's not, then both of them are tainted so you kind of have to follow the flow through your design, make sure that your specific information that you want to keep private, confidential or authenticated will have the same properties as you go through the process. So these are some examples of works that are being done and we're trying to figure out how to add this into our main specs. Another big question that we're trying to deal with and that comes up more and more is what about security certifications? So should the RISC-5 Foundation actually be involved in it? And if so, how? The question comes up because being at the instruction set level, we don't look necessarily at how the implementation is done. That's not the mandate of what we do. So how do you make sure that you can certify for security if you're not looking at how the implementation was done and how it leaks or not? That's a good question. So we've had, the first thing that we're doing is that we're creating formal specs and compliance test suites, but this is only, I would say, a functional spec compliance aspect of it. So it has a certain function and that function will be realized. Functionality will be realized. That doesn't tell you anything about how much it leaks or not. So how do you certify, given that the micro-arcs specs are kind of out of scope and that every flaw we've seen more recently is related to that side of things? Good question. So we started some discussions with different evaluation labs, security labs that are, or other organizations that are proposing different schemes and we are trying to see if there could be certain security levels that we could define that would maybe not necessarily look at the exact implementation, but at least from a functional perspective, prove that the security properties are done right at least. So the two that have been proposed so far are CESAP and PSA for more IoT-oriented devices. One of them, interestingly enough, is driven by ARM, but my understanding is that you can perfectly submit a risk-5-based design to this scheme as well. So discussions about how do we do this? How do we even approach this? Any good ideas? Please talk to me. So this brings up an interesting question as well, a question that I got at one of the recent workshops about, well, how do you position open-source versus security certification? Because if some of you, most of you, I'm familiar with common criteria and how that security game works, and there's something in there called the Jill Tables in which you get points if your design is actually not accessible and is hard to find. So essentially, your design is more secure in some sense if you don't make specs available and it is hard to discover what's in your product. So if we're talking open-source, this is going the exact opposite direction. You benefit from everybody being able to look at your design, making comments, you find bugs, and you can improve, but you lose points on the Jill Tables in the common criteria game. How does that fit together? That's a question I got recently, and I don't know that I have a good answer to that yet. So open-source was just some form of, I'm calling it obscurity, which is a little bit over the top, probably here, but it is a form of obscurity to say you get more points if your design is harder to find because nobody has seen it before and never will. Good question. All right, and then the other direction is assurance. So I've talked about that a little bit before. Formal verification, hardware, security, properties, and guarantees towards that. I've mentioned a few tools that Galois is working on, lando, or specs and tools, lando, bespin, and grift. There's other things going on in this world on security assurance in that form. I've listed a few things here, which are not just risk five related. They're broader than that, but please see some of these companies qui sont ici à chess this week as well. They have interesting things to propose. For example, riskure has a kind of software source code analysis tool that's called true code. Secure IC has something a little bit similar, but I believe at the hardware level called virtualizer. Fortify IQ has a tool called trace IQ, which is trying to see if some of your designs are resistant to power analysis or not. Enterturga Logic is a company that proposes a tool called Radix that can analyze your RTL and see if certain security vulnerabilities are present or absent and helps you design better at the RTL level. I'm sure there's plenty more stuff going on. This is kind of the things that I'm mostly aware of if you're working on something else that I haven't talked about, or that I haven't listed. Please speak up, and we'll be happy to to include information about what you do here. All right. Couple more minutes, one or two more ideas that you could be looking at or working on. What about risk five and post quantum crypto? We're going the first step. We're a little behind, so to speak, looking at algorithms that were done 10, 5, 10 years ago. We're doing that now. But what about the future? What about post quantum stuff that's coming up? And there were interesting presentations about it this morning. How do we address it as the risk five foundation level? Should we be looking at addressing it at the vector extension level? Does that even make sense? Should we specify completely new stuff like inner products that would make some of the constructions go faster? Is this necessary? Is this sufficient? Is it even going to be useful? Will it gain performance? Should we do it? Should we not? If you want to work on this and propose a group, please do. Should we be doing any specific extensions for lattices, codes, super single or isogenes? How do we do that with the current instructions and what else do we need? Another open research question. Okay, almost done here. So I think I've given you a little bit of an overview of everything the foundation does. The tools that are available, specs that are available, work that the task groups are doing right now, future work that we could be looking at and most importantly, the open problems is how to really deal with security when security is done at the implementation level. How do we do that? Any ideas are welcome. We have some ideas and we'll be coming up with interesting platform specs but everything relating to implementation level leakage, we need to think about how to address that. So open source, I would say in general is a great approach, even if you lose a couple of points on the Jill table. There's many new opportunities. There's a lot of stuff happening. There's a thriving RISC-5 ecosystem. Please do look at the open problems. Please continue working on everything and let us know of your results. There's many good ideas already, a lot of initiatives but still many things to be done. So this is really a call to action and again, I'd like to thank the organizers of chess for inviting me today to be able to give this talk to you. I hope you enjoyed it. If you have questions, we can either take them now or over lunch probably because I'm standing between you and lunch now. So thank you very much. I hope you enjoyed it. I certainly did and I hope to have good discussions going forward. Thank you. So yes, we do not have too much time for questions but if you have one or two. I have one. What's for lunch? What is for lunch? I don't know. So maybe there is no question we can go to lunch. Thank you. Thank you Elena. Sorry, we miss also two presentation for the first session of the afternoon. So if there is some speaker come to join us.


Hey everyone, welcome to today's day trading recap for Tuesday, October 26th. Really nice green day today for me, $4,050, mostly thanks to Tesla. Let's go through these, I'll show you what happened. Two mighty 90s won in AMD for plus 255, won in Microsoft for plus 60.  So let's go to these, let's start with the mighty 90s, AMD. So AMD was pushing lower, had this nice little poppin' volume right into a key level, got long here, and cut that run there. The only thing I wish I would've done different here, right when I got out of my last piece, I was like, you know what, I should've probably held one and sure enough, this thing really ripped up just after that. But still a nice winner, plus 255. Microsoft was a small winner, plus 60. So Microsoft was right after AMD, it was pushing down, had some volume poppin', I waited until here, so I got in right here, or maybe it was even this one, yeah, it was actually this one. And I just, I caught this little bounce, it looked like it was having problems getting through that level.  Onto the runners, first one in Zoom. So this was a little bit later in the morning. Zoom came down, or did, Zoom had been strong. And then so when it pulled back here, I got long looking for another bounce, kind of bounced down into the top of its previous highs. So I was looking for a bounce, and it just kind of started a bounce, rolled over. Started a bounce, and then when it rolled over here, I just cut out and took a loss. Airbnb plus 551, so this is a nice trade. This one was, I'm classified it as a runner because that's how I managed it. I got in based on a little bit of a mighty 90 setup, had this push lower right into yesterday's high, had a little bit higher volume, and that's where I entered. Got long right here, caught this move up, held onto one contract, got out of everything, except for one right there near the top. Took some heat here. I was thinking about adding again, but I didn't, and bounced up. So when it got back up to the highs of the day, I just cut out of my last piece. Booked a nice profit plus 551. Apple minus 260. So in Apple, yeah, yeah, this was one of my first trades. Big volume runner on that second bar. So when it pulled back, I was looking for a continuation higher. This thing just kind of bled lower, lower, lower, and I was hoping we'd get a bounce there. When it broke here, I just ended up cutting out. So it took a loss on Apple.  This one had this, it looked really strong. It was hovering right at all time highs, which it hit yesterday. And so when it dipped down here and then fired back up like that on the same candle, I got long looking for a continuation higher and this thing just pushed down. So I ended up cutting out of it, taking a loss there. Twitter, Twitter, Twitter, Twitter. This was another one of my early morning trades. Had this initially started down and went into the red briefly and then just shot right up with massive volume. So when it pulled back a little bit, I got long looking for a continuation higher and that didn't happen. Just kind of bled lower, so I ended up cutting out. Taking a small loss there minus 160 on that trade. Uber, this is one of my later morning trades. We're sitting there and all of a sudden we had this big spike in volume. So when it pulled back to this pivot, that would catch a bounce, started to, in fact, I was pretty close to getting out of half of my contracts if it would have bounced a little bit higher. But then it just rolled over, so I ended up cutting out and taking a loss on that one. And then lastly, Tesla, this was just a massive, massive loss. Wind for me. And part of it was because of the size I used, no doubt. But I mean, this thing just really started flushing and got some really nice spikes in volume. I mean, we were right at 10 a.m., which is kind of our cutoff for the Mighty 90. But the way that it was flushing and the way the volume was acting, I just waited for it to get down to yesterday's high there. Caught a bounce here and literally that move right there got out of half. In fact, let me just bring this over. I can kind of give you, this gives you a better time. So this is where we post our trade. So got in at 10.05 with that first one, got out of half, still 10.05. So literally just a quick bounce, bought them for 31.5, sold half. So I bought four, sold half at 35, came back down, added at 10.08, bought two more for 26, closed half of those at 30, literally three minutes later, two minutes later closed another quarter, and then closed those at 10.12. Then I turned around at five minutes later at 10.17, bought some more at, bought four more at 26.90, closed two of those at 30, closed one at 30.25, and then closed them all out at 10.24. So between 10.05 and 10.24, I was literally just playing these bounces here. Boom, boom, boom, boom, and out. So kind of a crazy trade. Obviously, the size had a lot to do with that, but the price action too, I mean that's what really was giving me the confidence of getting in with some size at a key level with this pop-in volume, with that quick flush. So didn't really give me much of a move. I mean, if I would have booked a lot more or had this thing actually bounced and continued back higher, but nonetheless, booked some quick profits in Tesla to put me at 4,050 total profit on the day. So good stuff. We did talk about in the community this morning. So we, a couple of weeks ago, we released our new strategy, the navigation trend trading that we're primarily using for longer duration swing trades, several days to a couple of weeks, but you can also use it for day trading. So once a week, I haven't decided when, but once a week, we are going to trade exclusively the NTT setups in our day trading as well. So probably sometime next week, maybe even this week, but regardless, I will post in the community, kind of giving you a heads up when that's gonna happen. Look forward to seeing everybody in the live stream, the rest of this week. See you then.


Today, we're going to talk a little bit about what's been happening this past summer and why. We had, in many locations, we had early populations, some a little later. One of the things we did see in most of them was high survivorship from early on the season, early on the season on. I don't have anybody notice, but it was kind of hot and dry this year. Anybody really take note of that? Yeah, okay. Early in the season, one of the things that keeps our insect populations in check are something we call animal pathogenic fungi. It's a fancy name that means fungus that kills insects. And you'd be surprised how much mortality we actually get from that. We don't have grasshoppers up to our hips every year, despite what you saw this year. It doesn't happen every year. I know the numbers we saw this year can make you forget that. I had a student, we used to have an honest to goodness locust in North America, Rocky Mountain Locust. It's gone extinct now. I tell this story in my anemology class, I had one of my former students call up today and said, Anne, remember when you told us about the Rocky Mountain Locust? I said, yeah. He said, remember you said they were extinct? I said, yeah. He said, are you sure? I said, yeah. These fungal pathogens, these insect killing fungus get established early in the season. So these young insects that are just coming out of the egg, the small larvae and the small nymphs are very susceptible to this.   And so insects have this stage life, they go have eggs and then larvae or nymphs and then either a pupae or go directly to an adult. So these different stages have different levels of mortality in them. And that one that happens early is fairly important to what's going to happen to the population dynamics, can really limit the populations later on. To remove that mortality, and all of a sudden you have big populations. So this year we had heavy populations of aphids and small grains. Again, aphids got started early, they kept going. Why? No fungal disease. Same thing with Colorado potato beetle, same thing with our grasshoppers. So that part of being dry and hot impacts that early season mortality. But it's not the only part of the story. Another part of the story is the warmer it is, insects are cold-blooded. They don't control their own temperature like we do. So our physiological processes, our digestion and reproduction, all of our physiological processes are basically controlled under a very narrow limit. You basically generate your own heat, so you can do that. If you start getting a fever and it gets too high, you start feeling bad. Some of your physiological processes aren't going so well. In insects, they have a lot more tolerance of different temperatures. They have to, because they don't generate their own heat. They warm themselves by ambient temperature, right? So whatever temperature it is out here, that's what temperature they're experiencing. So their physiological processes can speed up a lot more and tolerate higher temps as the temperature changes. And that's what happens. You have them, all of a sudden, moving faster. When it gets really, really warm, they start moving faster. Not only that, they start to digest faster, which means they're going to feed more. They also reproduce a lot more. The reproductive drives go up, the reproductive potential goes up. But more importantly, if you've got an insect like aphids, for example, that have multiple generations in a year, all of a sudden their developmental time, which is closely linked to temperature, goes down and it decreases. And that means you're turning out more generations per year. And on top of that, you don't have that early season mortality. So now you've got more rapidly generating populations, not getting dead early on, being alive to reproduce, and you get expanding populations. And that's what's kind of happening this past summer. The business about having generations get shorter was really noted with Colorado potato beetle this year. When we started seeing them go through their larval stages really, really quickly. We started having things go through a second to third instar in a matter of days rather than in a week. So things were really rapid this year. Those developmental times really decreased. And again, that's linked to temperature. What this means for Colorado potato beetle is typically up here, what we've come to say when we see our summer adults, right? The overwinter's adults, the springtime, they start wandering into the potato fields from wherever they spent the winter. It's kind of like most of us coming back from Arizona. So we wander in, get our jobs going again. So they get into the fields, they start reproducing, they have eggs. Then you see the larvae, right? The larvae feed for a little while, a couple of weeks maybe, or shorter this summer. And then they'll drop to the ground, they burrow in, and they pupate. And then out comes summer adults. And that usually happens for us in July, right? And we usually refer to those summer adults as, that's the second generation adult. Actually, it's not. They're the ones that are going to overwinter and be around next spring. So we actually only have one true generation in this area of Minnesota and in Minnesota in general. It's very rare for us to see a second flush of summer adults. We've already seen that down in Central Mint. You've got plots in Becker that are experiencing, what was it? What was it? Thousands? Thousands. So Josie is saying she's got thousands of beetles in her plots. These are second, this is our second flush of adults. We've already seen our summer adults, what, end of June, early July. So yeah, we've seen two complete generations in Minnesota. That is extremely rare. I haven't seen it, and I've been working here for 24 years. So I talked to some of the guys who have been here longer. And one of them said, yeah, I saw that I think maybe 40 years ago. So yeah, it's a rare event. But it's all because these things are being driven through by temperature. For those of you who are doing seed potatoes, I can tell you that the PVY vectors are starting to slow down a little bit. We've seen three weeks of decrease. Now I was a little concerned because we were ahead of where we were last year, just up to about three weeks ago. And then all of a sudden, we started seeing our populations decrease. And that's very unusual for us. Our populations don't usually decrease until third, fourth week of August. You know, so right now. And we started seeing that decrease the end of July. So I think what we're also looking at here is not only does heat kind of speed up insect populations, but also it has an effect on plant growth. So this year, we saw small grains come mature very, very early, which means we saw the small grain aphids, which make up a large part of the stuff that's flying into potatoes later season. We saw those come off that grain early because the grain senesced early and they were flying early. And then all of a sudden those things stopped. We saw fewer and fewer aphids in our in our flight traps. So the good news is I think we're over the hill for for aphids as well. But that's kind of in a snapshot. What's going on when you see these these populations? They seem to be eating more rapidly this summer. I was I was hearing a lot of reports of that. I was hearing reports of there seem to be going through their larval stages really, really quickly, getting in adults coming out early. I had a report early today. I was talking to Justin. He thinks they may be seeing second generation up here, you had said possibly. So and it is possible that we could get them up here, whether or not if you're seeing third and fourth instar larvae right now in the field, whether those pupate and come out as adults. I hope not. But it is possible if it gets warm again. Now, the reason all this is important is those summer generation adults that came out first, they're still surviving unless they're been sprayed out of a field. But if they're not treated, they're still surviving. And they're going to be going off to overwintering locations like that fence row of that, you know, those tree lines. That's kind of where the overwinter. So they're probably getting ready to leave those fields anyway. If we have a second generation of adults, that just means we've got more overwintering, which means that if the winter conditions, depending on the winter conditions, we could have more adults moving into the fields next spring. That's why that kind of second generation of summer flush adults is important. Why should we be a little careful next year? What do I have for good news? OK. You know, you're going to hear a lot less on pathology today. So I figured, you know, it didn't look that bad. And and Gary will talk about Lake Blight situation. But I figure if they've got good news, I got to give bad because that's what pest management is. It's either doom or gloom. You're going to get one of the other. So. Oh, well, in the Colorado Potato Beetle test, we did a lot of chem trials this year. And what I can tell you is, although I can't discuss what they are, I can tell you that there are some products that are going to be coming online, hopefully getting into registration. And finding registration for potatoes that look really good, have good efficacy against Colorado Potato Beetle. And that's a really good idea for us, a good thing for us, because it'll give us some extra tools in our rotational toolbox and gives us something else to go to once we're once we're finished. And that's actually a pretty common problem right now. I'm getting calls from guys in Central Minnesota who are saying, yeah, I've got these second flush of summer adults. And I've rotated through all my chemistry. What do I spray? So actually having a couple of extra products is a good thing.


Hi guys, my name is Jen and I create crafts in today's video.   So let's get started. All right, crafters. So starting in design space.  I either purchased them from design bundles or I purchased them from Etsy. Those are my two go-to to find them so you can find them anywhere you can go and Google and find them that way. But that's my two go-tos is Etsy and design bundles. So I thought these would be really fun to do. To be honest with you, I've some hide one behind it. I have kind of a few of them behind there. I have never done one like this before this whole image here. So you are going to learn with me how to do this. This is really interesting how it's so full and vibrant like this. So you're going to learn with me how to do these. I didn't see these other ones hiding behind it. So you can see there's kind of a theme going on here. I sell my Kuzies and all of my other crafts at two consignment stores and then I'm also really looking forward to selling my stuff at craft flea markets stuff again this spring and summer. Stay along with me. I will show you everything how to set up how I did give you the full details on everything. So you want to hit that subscribe button if you're not subscribed already because I do make a lot of money on several things that I make. One of them is my Kuzies in the summertime and the other one is my key chains. But my number one thing that I sell is my egg cartons. If you haven't seen that stay tuned. I will leave a link in the description down below showing you how to create those and what they look like. So the only thing with these that I have to do is resize them and there's really nothing else that I have to do except for make sure that they're changed to print then cut and then resize them. So the Kuzies that I have, I just purchased all of them on Amazon. I purchased a hundred pack of multiple variety of colors and then I also have just regular white ones that I'm going to be putting this on. I can't tell you what size to use the way that I do it for me is I put my Kuzie on a mat and I look that way to see how big it is. That's just the way I do it. It makes it really simple and easy to do. So the way I figured mine were so my white ones are a little bit bigger than the colorful ones. So these ones I think I'm going to keep just the way that they look and then this guy I'm going to make a little bit bigger. So for mine it's going to be there it is a 3.2. That's what size fits for me. So I'm just going to change all these to be the 3.2. So it's it's anything under three and a half by three and a half. So whatever works for you is might be different than mine. So the way that I do it is I'm going to leave it locked up here, but I'm going to change this to be 3.2 and then it's automatically going to change the height for me if you saw it there. So I'll do this one really quick and show you I am not unlocking it. I'm just changing it to 3.2 is what I wanted it and it's automatically going to change the height for me. If I unlocked it and change it to be 3.2 by 3.2. I will show you it will not look right. So this is what it looks like right now. If I unlock this and I put it to be 3.2 watch this. It's not as bad, but it is skewed a little bit. So I don't like the way that looks so I always keep it locked up there and then let it figure out for me the height that it's supposed to be. So I just push the back button so it went back to where I wanted it anything under you know the three and a half by three and a half. So I'm just cutting it right here. Then this one I want to make sure no way too big. So again, I'm just going to change it 3.2 and then let it automatically change the height for me and then this last one down here. Let's figure this one out the 3.2 and then if you want to change the color on these you can change the color. Some of them are kind of harder to get to like this one. It looks like it says original artwork here. So what you can do is actually go up to operation up here and change it to basic and that will let you get to the color. So let's say I wanted to do this one yellow.  So again, same thing. It's printing cut. You can't change color here because it says that you just want to go to basic and you can change it to whatever color you want. So let's say I want this one brown just like that. So I'm going to just hit the back button a few times because I want to keep these black the way that they are and then I change this one already to a different color. So again, all you got to do is resize and make sure it says print then cut and then you can go to make it. So for this one, I'm going to leave it a little bit bigger than the 3.2 because I wanted to overlap on my koozie. Nope, got to take that part out. So I'm going to change this one to be the 3.2 and then let it automatically change the width and the height for me right here. So I've never done anything this full before that takes up the whole space of it. So we're going to see together what this looks like. So I always like to go in here and check that it says you can see up here right here that each one of them say print then cut up see miss that one. So I'm going to go in here for it to then cut you can see it changes it looks a little bit different to but I always like to double check and click on every single one to make sure that that's what they say next after you change the color and you change the sizing you just want to go to whoops sorry want to go to make it and then you send it to your printer. So you're using a sublimation printer that you set up with the subbing ink and you want to use the subbing paper. The only other thing that I do on here is just move this down a little bit and move this to the side a little bit just so I can get my scissors in here. You're not going to need your cricket machine with this you will see register lines on here when it prints out you just want to make sure you cut those away. So that's the only thing I do on here actually one more thing I click the mirror button. So with anything like htv heat transfer vinyl or like this you always want to mirror your image. So I'm going to do the same thing with this one just push it down a little bit. And push the mirror button and the last one unfortunately with design space I don't know why they do it but they don't let you like put them out like if I wanted to put all I suppose that one would fit but it's a little close here like having a little bit of extra paper. I think and I need to work with it so if you guys are kind of knowledgeable if you guys are knowledgeable about this let me know but I think you can do this in Canva and you can print out the whole 8 by 12 piece of paper that you have. I'm not sure I'm just getting started with this. So this is how I do it. I just saved this paper right here. I'm going to take a scissors and cut this paper so I have the rest of this and then I'll use it for another project somehow. So again I could probably put another one of these right here but I'm just going to leave it the way it is for the purposes of the video. I'm going to go to continue and I'm just going to send it to my printer. It's as easy as that. So it says send to printer. I'm going to choose the printer I use. So I have this one. I have the equitink 2803 and I absolutely love it. So you can see the excuse me. You can see that the mirrors on and I always take off the bleed here and then I'm just going to go ahead and push print and it's going to send it to the printer for me. I'm going to do the same thing on these as well. So I'm going to skip and do this one. So I have that one. I'm going to send it to printer. See it here again click my printer that I'm using turn the ad bleed off print it. So it's printing for me now. I'm going to get set up at my heat press. I'm going to talk a little bit about my heat press and then show you what they look like and how to create these koozies. These are awesome. I cannot wait to show you the finished product. All right. So I'm at my heat press and I have all my stuff ready. So here's my new heat press that I'm going to be talking about really quickly. This is the HTV runt heat press over here is my old one. I love this heat press. I'm not getting rid of it, but this one has a couple of neat features that I really love about it.  So once you close this drawer, it will automatically go down. If you have an issue, you just push a little R on here and you make it go back up really easy to use. No pressure that you have to worry about it automatically does the pressure for you and it has an awesome little timer button on here. You can push the time button plus and minus. You can push the temperature button here and do the plus and minus really awesome. So when the R turns green, it means it's ready. So I have my heat press set at 400 degrees for 35 seconds. I have my images here. So I'm going to show you these really quick. So this is the images that I cut or printed out on my printer and you can see that it has a register marker on the edge. That is because of cricket. I was not putting this in through cricket to cut it out. I'm just going to take a scissors and cut them out. I've already cut one of them out here. So I cut this. You want to make sure you cut the register lines away from there. So I'm going to be using this one first and you can always see from the back way which way it goes. So you don't put it upside down. I've done it many times where I thought I had it right side up and I actually did it upside down. So you always want to make sure that you're putting it on properly.  So I wasn't able to finish this project on video on time. So I actually have these white ones and in the meantime of me doing this video, the first part of it and pressing it now, I had the time to order some new koozies. So not only do I have the white koozies, but I have colored ones and you can see here, this is why I said it's important that koozies are different sizes. So you can see on the edge here, there's a little bit bigger of the white one is a lot bigger than the colored ones. You always want to make sure that if you're watching somebody's video and they say, oh, your koozie is three by three or six by six, whatever it could be, you need to measure your own so that you make sure that you have the right size. Very, very important.  You can see that it says it there. So what I like to do is kind of work backwards. I guess. So this is where it comes in handy where you make your image a little bit larger that you can see all around it and I'm just going to take some heat tape that I have here. This is really not necessary to do this, but I just want to show you guys you can put heat tape on here to make it stay in place. Normally with bigger ones like the koozies, I don't worry about taping this. I just I just put it down in one spot so you can use heat tape and put it around the side so it stays in the spot and then when you're done, you want to make sure you flip your image so your image is right side up. So it's facing up towards the heat. So I'm going to just take another one really quick. So I have a blue koozie and I'm just going to find one here and cut this one out to really quick. Again, like I said, you want to get rid of the the lines on the side because those will go on anything because any color will go on here as if you can see this. If you can see all this, I kind of made the mistake of doing that. So I have it all over here, but it's not going to ruin anything with this. So here's the next one again. I like to flip it over because you can see what it says and then you want to just take it and this one's a little bit smaller. So I'm going to take my time trying to find the center of this. I can see the image on the back and I can kind of gauge where the edges are here and I want to make sure it's going to fit on the top and the bottom. So very important that you want to make this really straight. And then now is when the heat tape comes in really handy because now I can just put it on the side because it's not that big of an image. So just like this. So then the image is not going to move. So just like that, two of them are done. Next thing you want to do is just take a piece of parchment paper or a Teflon paper and lay it on the top to protect it. I'm going to pull this out all the way. I have the two on here and then again, like I said, all I got to do is watch this. That's it. It's automatically sorry about that. It's automatically telling me that it's working the pressure. I don't have to worry about it with this one. I'd always have to gauge and do the pressure on that push down really hard. This one. I don't have to do anything. Just watch it count down and that is it. This thing is really awesome. I love this thing. So other things that you're going to need are some gloves because this is going to be hot when you are done with this. So the heat tape comes in really handy. I'll leave a description down below. This heat container is really awesome. It comes in handy. Once it's done, it will automatically lift up.  So not at all am I saying, hey, go leave your heat press. You always want to stay by it when you have it on, but just in case that's a nice feature that they have. So I'm going to take that off. Not going to worry about the gloves. You should have gloves on for this, but I'm just going to show you. So I'm going to take this off and there it is just like that. It is a little bit off on the side here, but I figure once you put a beer can in or a soda can, you're not really going to tell. So there's the first one. They're the colored one. And then here is the full color one that I was really kind of worried about because I'd never used a full color before. So we're going to see what this looks like together. I'm going to take this tape off and again, this is hot. So you should wear gloves, but I'm not going to put them on for now. Ready? Ready for the reveal? I've never done this before. All right. Dad, that is really cool. I love it. So it went down far enough on here. So if you have something in here, you're not going to see the edge on there just like that. And you can actually go around and do the back too. But I like that. That is a full image there. That looks really awesome. So I'm going to continue to keep doing these. I have all these left here, but you're just going to want to do the same thing. Cut around your image here and then use your heat tape and put it on there. So this is done. You can kind of tell that this is done. There's really no color on it left. So you want to put that to the side and not make sure you don't use it again. You'll see on some of them that it does have color left. That's just where your heat did not touch your fabric. So that's why you might have left that left. So I'm going to go ahead and finish some more of these up and then I'll show you what they look like when they're finished and I'll put something inside of it. So kind of shows you off shows off what it looks like. But overall, I'm very happy with this. Leave a like down below. If you like this video, hit the subscribe button. If you guys are not subscribers of mine already. I'm going to be doing a lot more crafting coming up and you do not do not want to miss because I do craft shows. I sell it consignment stores and I do really well and I'm willing to give you guys all my tips and tricks. I actually have an ebook for sale as well. I will leave that down in the description below. All the funds go towards this channel for me to keep doing awesome videos for you guys. So help me and let me know you appreciate me and love these videos. So stay tuned to see what this looks like. But please do hit that subscribe button and that like button down below. So I hope this video really helped you out. This is what they look like and to do this with this part in here. I just cut out this with a piece of cardstock and then you just stick it in here and basically it helps you hang it here and it also keeps it nice and flat like this as you can see. So if you want to hang it and you put it in a store or something to sell it, you could do it like that. Just a piece of cardstock really not that hard to do. And then I also have a stack here. So I wanted to show you guys I do sell these at craft stores. So I have it here. I just have a little tag on the edge here. I put my number on it. I put the description of it and then I sell it. So these are very good sellers for me. So I hope this video really helped you out. I do have an ebook for sale as well. So if you're interested in learning some more about crafting and where to sell it how to sell and all that. I have all that available there. So I will leave that in the description down below. So if you're interested in it, please let me know happy crafting everyone.


This study examined the frequency of markers of transfusion transmitted infections among blood donors in a blood bank at a tertiary care hospital. A total of 29,732 donors were screened for hepatitis B, hepatitis C, HIV, 1 and 2, syphilis and malaria. Out of these, 2,587 donors were found to be positive for one or more of these infections. The overall prevalence of infectious diseases was 8.6%. The highest prevalence was seen in anti-HCV, 3%, followed by HBSAG, 2.9%, syphilis, 2%, HIV, 0.5%, and malaria, 0.02%. This study highlights the importance of screening blood donors for transfusion transmitted infections and suggests the further research should be done to determine the risk factors associated with these infections. This article was authored by Hirakadir, Nadia Nasir, Shaheen Kauser, and others.


Okay. We're wonderful. Hello. Thank you for your patience. My name is Whitney Leigh. I'm a developer advocate at VMware. So nice to see your smiling faces. So I have a pretty cool job. I get to travel around the world and talk about interesting tech. And I'm here talking today because I developed a presentation about Knative Serving. And so I've delivered it many times throughout the past year. And I wanted to share with you some of the questions and concerns I've heard about Knative. All right. So that's me. When I give the presentation, I don't use slides. So I'll draw out how Knative Serving works and then I'll flip back and forth to a live demo. So I'll show it in the terminal also. So a finished drawing looks something like this. During the presentation, I'll be zooming in on different parts and drawing it. And it's a really fun presentation. And it's really fun for me because I get to see people get excited about the technology. Sometimes I'm presenting to developers and they're overwhelmed by Kubernetes generally. And so I'm giving them K-Native where they're like, oh, I don't have to know all the Kubernetes abstractions. This is great. So I see them get excited. And then I also see them like, okay, I want to adopt this. What should I do next? Or what is a potential obstacle maybe for getting this in my organization? So I get a lot of questions and I've been saving them all up just for this moment. So I want to talk about the audience for my talks. Who am I giving these presentations to? So as I just mentioned, I do give the presentation sometimes to developers. For example, at JBC in Barcelona, I've been at DevOps UK in London and various stops around my companies like spring one tour, Seattle and New York. But then I've also given this talk or talked about K-Native or serverless to an ops audience too. So you'll see some of that reflected here. And so that would be at VMware Explorer. I did that. And also Victor and Mauricio who are up here, the three of us did ask me anything about serverless panel on Victor's show, his DevOps toolkit show. So also this is my show in lightning. It's a streaming show. So Carlos came on and talked to me about K-Native serving. And some of the questions came from that show too. That was a fun time. So I've grouped the questions into larger trends instead of firing off a bunch of them at you. So let's go over the trends quickly. I've gotten questions around observability and debugging questions about the networking layer, questions about integrations with other tools, and similarly how K-Native fits in with the CI CD, GitOps and or platform building story. And then also I've gotten questions around scaling workloads. So without further ado, let's actually hear about some of the questions that I've received. So in terms of observability, how is K-Native? I'm going to kind of list the questions. I'm not going to tell you how I answer the questions. Basically, I am very comfortable saying I don't know when I don't know, and I will send them to the K-Native Slack workspace, but for now I'm just going to list these questions. So is there a GUI to help me see the differences between revisions at a glance? And I overheard I don't like K-Native because it's impossible to debug. So that's a preconception that's out there. What are your thoughts about using K-Native tracing and telemetry capabilities versus code level instrumentation? And finally, for this one, how do I debug K-Native when things go wrong? So then I also received questions about the networking layer. So definitely the first two times I presented, I got comments and questions about K-Native being heavy and requiring the full-fledged service mesh. So I now address this as part of my presentation where I talk about the different networking layer options, but you should know I like to tell the community it's still very much the way K-Native is perceived out there that it's heavy. And then another question I got is why doesn't everyone use this? It doesn't sound like a networking question, but when I got this question, Mauricio actually came on to my enlightening show. He talked about K-Native eventing, and when he came on he said that it is his firm belief that K-Native should be installed into every Kubernetes cluster. So when I got this question, I like quoted Mauricio in that moment, but then I had another audience member who said he was like, I know why you don't use K-Native. And I was like, oh no, okay, here we go. And so that guy said K-Native makes your resources become tightly coupled with a specific networking choice, and that networking choice might limit choices you can make later in terms of what tools play well with K-Native. So I talked to that guy after, and he was specifically talking about Flagr. He tried to make Flagr and K-Native work together, and he couldn't do it because of the networking choice that K-Native forced him to make. So that actually segues perfectly. And so my next set of questions, which is questions about integrations with other tools. So for this one set of reciting the questions, I thought I'd simply name all the tools that people are asking about in terms of the context of working with K-Native. So first of all, GCP Autopilot clusters. I'm a relatively new learner myself, so I'm not going to assume you know any of these text technologies. I'm going to say what they all are. So pardon me if I'm repeating something you already know, or something that's obvious to people because I don't have a sense of what's obvious because nothing's obvious to me. But Autopilot gives you a cluster for exactly the size of the workload that's running. So Autopilot would have to create a node to run a workload. So then therefore Autopilot, with your scaling from zero, you have to create a whole node. And so I got a question around whether that works well with K-Native. Also, whether K-DA works well with K-Native, K-DA stands for Kubernetes-based event-driven autoscaler. So can you use this autoscaler with K-Native? Argo CD, does that work with K-Native? It's an Argo CD is declarative GitOps continuous delivery and deployment tool for Kubernetes applications. Tecton Pipelines, it's a cloud native solution for building continuous integration pipelines. And Crossplane, which we talked about today, it's a way to extend Kubernetes to manage resources that are external to Kubernetes. So we know that that works with K-Native because we just saw Mauricio and Victor show us. And then as I mentioned before, Flagr, and I've gotten questions about Flagr multiple times. So not just from the one difficult, not difficult, wonderful person who participated in that conversation. So Flagr, if you don't know, does progressive continuous releases, and it uses metrics as a way to calibrate the way the application is rolled out. So this, for the next group of questions are about how does K-Native fit in with the CSED, GitOps, and platform building story. So basically all the tools I was talking about before, integration questions with Crossplane, Tecton Pipeline, Argo CD, et cetera. I want to point out here that this category definitely has ever overlap with tooling integration. So a question about whether K-Native integrates with Crossplane is a question about platform building in my book. A question about whether it integrates with Tecton Pipelines is a question about CSED. And then we have some more straightforward ones like how does K-Native work with an infrastructure as code approach? If you're using GitOps, would you have a SCEMO there, too? And does it work with GitLab, CICD? And then the final section of questions are about scaling workloads. So how do you make sure your cluster has enough resources available should many applications scale from zero at once? How can we measure when it's worth using K-Native for the scale to zero benefits? So K-Native itself has resources constantly running, so how do I know it's going to be a net win to use K-Native for serverless? How can you do serverless with spot nodes? And without the cluster autoscaler on the Kubernetes cluster, can you realize the true serverless feature of K-Native? So to recap the five trends, we have questions around observability and debugging, questions about the networking layer, questions about how K-Native integrates with other tools in the CNCF landscape, questions about how K-Native fits in with a GitOps, CICD platform building story, and questions about scaling workloads. At the end of my talk, I give action items, so now I have questions for you. First I'll get some statements. So I point people who are interested in K-Native to the knative.dev quick start tutorial, the one that Paul was just talking about, that he upset up. And I also point them to the K-Native Slack workspace for if they have any questions or adoption concerns. But I wanted to ask you, and I don't expect you to answer now publicly, but maybe find me later. If there's any other K-Native resources that you think it would be valuable for me to point people to when they're learning about K-Native serving for the first time. And that's the end of my talk. You can find me on Twitter at Wiggity Whitney. If you want to see one of the talks that I give and pick it apart and give me feedback, there's a link right there. But that's all I have. Thank you so much, y'all.


I'm a retired water engineer and it's my joy to work with so many talented volunteers who look after these wonderful steam engines. These are Hawthorne Davie steam engines and they are the last two working steam engines of their type in the whole world. They're two-stage steam engines and they would drive these shafts backwards and forwards rocking those huge cast iron wheels behind me round like that and they would be connected to rods that would lift enormous plunger pumps that would lift the sewage from 40 feet down from the end of the sewage collection systems and drive it down six 700 millimeter diameter mains to the what was then new sewage treatment works at Milton. Now the reason for this sewage pumping station is that at the end of the 1800s you could not swim in that river and survive because it was so filthy and so full of sewage. So many people in Cambridge were dying of cholera and this was the case in all of the major industrial cities throughout the world. So these new stations were the beginnings of us cleaning up our environment.