Ladies and gentlemen, Dennis Day. Dennis Day is brought to you by Palm Olive Soap and Luster Cream Shampoo. Palm Olive Soap, your beauty hope. Luster Cream Shampoo for soft, glamorous, dream girl hair. The Dennis Day show with B. Benadera, Dink Trout, George Dooning in the orchestra, and yours truly, Vern Smith, is written by Frank Galen and stars our popular young singer in A Day in the Life of Dennis Day. Here's Dennis to sing, Hair of Gold, Eyes of Blue. I came down from Butte, Montana for a little change of scene and a pay where I met a pretty queen. Oh, hair of gold, eyes of blue, lips like cherry wine. The prettiest gal I ever knew and I'm gonna make her mine. And to leave on Monday, but she held me kinda tight so I held the ground and hung around and I left on Friday night. Oh, hair of gold, eyes of blue, lips like cherry wine. The prettiest gal I ever knew and I'm gonna make her mine. I was kind of blue and lonely, so I took my horse and packed and on Sunday morning was up and gone, heading south and riding back. Oh, hair of gold, eyes of blue, lips like cherry wine. The prettiest gal I ever knew and I'm gonna make her mine. Hair of gold, eyes of blue, lips like cherry wine. The prettiest gal I ever knew and I'm gonna... Ladies, what's your complexion problem? My skin's so dingy, mine's oily. My skin's dull, course-looking. For a lovelier complexion, you must stop improper cleansing. Instead, use palm-olive soap the way doctors advise. Leading skin specialists have now proved the palm-olive plan using nothing but palm-olive soap can bring fresher, brighter complexions. Yes, regardless of age, type of skin, or previous beauty care. Now, here's what these doctors advise. Wash your face with palm-olive soap. Massaging for one minute with palm-olive soap, lovely leather. This cleansing massage brings your skin palm-olive soap full, beautifying effect. Do this three times a day for 14 days. It's that simple. But remember, 36 doctors, leading skin specialists, advise this way for 1,285 women with all types of skin. Dry, oily, normal, young, older, and prove this plan using palm-olive alone, nothing else really works for two out of three. So, for a lovelier complexion, forget all other beauty care. Instead, do as these doctors advise. Use palm-olive for a fresher, brighter complexion. For loveliness all over, use big, frizzy bath sides palm-olive in your tub or shower. Our young hero, Dennis Day, is a lad who learned in his early boyhood to smile in the face of adversity. And judging from the life he's led, he's been smiling constantly ever since. But even he doesn't seem able to muster up a smile tonight. For you see, his girlfriend, Notre, has gone to visit her grandmother for a week, and our young hero is taking her absence mighty hard. We find him now pouring out his woes into the most sympathetic little ear in the Anderson household. Gee, I don't know what to do with myself. Seems like she's been gone two months instead of two days.  And we're going to have some fun tonight. I'm taking you to our club smoker. Oh, thanks a lot, Mr. Anderson, but I don't smoke. Do you might when you see Tassel's Latour, the red-headed ball of fire? Huh? She's a bubble dancer. A bubble dancer? Sure. You know, girl who dances with a bubble. Can't you get a dollar? Of course she can. But there's some men who'd rather watch her dance with a bubble. Gee, well, I guess it takes all kinds to make a world. Yeah. And not that Tassel's is going to do her bubble dance at our club dinner, of course. We just hired her to sing a few songs because she's the only professional entertainer we could get. But is she something to look at all? My quivering soul and body. Well, gosh, how does Mrs. Anderson feel about letting you go to a club smoking when there's a woman like that present? Oh, it makes no difference to cook this. She wouldn't let me go whether Tassel's was there or not. But I thought you just invited me. Well, sure. You see, you're part of my alibi. I am? Yes. I told Cook you that you and I were going over to John Campbell's tonight to see the pictures he took on his fishing trip. Yeah? And John handed his wife the same story that he was coming over here.  Ah, sure. You're absolutely safe as long as Pupsy doesn't get together with Mrs. Campbell. Yes, and that's hardly likely. I hate to lie to Pupsy, but, well, gee, a fella's got to enjoy himself once in a while. My home's the happiest in the whole world, but, you know what, I do get a little well, uh. Start crazy? Certainly not. You don't imagine I think that my home is a prison building. Well, that's thought has never happened. Yes, Gordon. I mean, yes, Pupsy. What's the Campbell's phone number? The Campbell's number? Why? What do you want that for, passion girl? Well, since you and Dennis are going over there tonight, I thought I'd ask Mrs. Campbell to come over here. Oh, no, no, that's, I mean, well, they haven't got a phone, Pupsy. They have the dinner. You know, the telephone company took it out, Mrs. Anderson. Took it out? What for? Unnecessary jiggling. Oh, it's the truth, Mrs. Anderson. I happened to call up Mr. Campbell about an hour after their phone was removed, and he told me all about it. He said that. Dennis. Yeah, I see the hole in it now.  Now, step aside. Operator, I want Mrs. J.H. Campbell on Wilkin Boulevard, please. Oh, I'm dead. What did you say? He said she's dead. Who's dead? Oh, Mrs. Campbell. They're holding the wait tonight for men only. Character on the streets this afternoon. Did she wait? Oh. See? Mrs. Anderson. Oh, she'll be back in an hour. No, don't bother. I'll call her then. Goodbye. So Mrs. Campbell is dead, is she? Oh, I made a mistake. I'll make them now and then. Well, you'll never top the one your mother and father made. Well, at least you got a little recreative, Mr. Anderson. Oh, but what good is it? In an hour, she'll talk to Mrs. Campbell and then. I remember once before she taught me in alive. She bowed me out for two days solid.  Yeah, of course. I was only able to hear her the second day. Jane, what are we going to do? Dennis, I have it. Well, enjoy it. You have much time left. I mean, I have an idea. Listen, if we could get some woman to call up Pooksy and say that she's Mrs. Campbell, all our troubles would be over. We'd have her tell Pooksy that she was busy. Yeah, then neither of them would ever know the truth. And I know just who we can get to do it to. That's Spencer around the corner who has such a crush on you, Miss Baker. But we asked her, Dennis. Gosh, I'm scared to go near that woman. Why? You can handle her? She always handles me and I'm ticklish. Nonsense.  Sure, and she looks like my father, but that doesn't stop her. Oh, well, I'll do it for you, Mr. Anderson.  What brings you here all of a sudden, and who cares? Honest, Baker.  Come into my warm, dark living room. Sit down, you're gorgeous in here. You're on the couch beside me. Well, OK, but you sit down first. No, you first.  Yes, I know. And let's see if I've lost any speed, huh? Oh, gee whiz, you're getting so embarrassed.  And tell me, does that little girlfriend of yours, Mildred Anderson, know you will? Oh, no, ma'am, she's out of town. Uh-huh, when the cat's away, the mouse will play. Well, I want you to think of me as something any little mouse would just adore. I always have. Oh, thank you. Now, what seems to be on your mind? I guess I've made mine for you, obviously. Well, Mr. Anderson and I are in trouble, Miss Baker. You see, we told Mrs. Anderson we were going over to the Campbell tonight, but actually we were going to the club smoker. Why, you don't. Well, anyway, we just wanted to call Mrs. Anderson and say you're Mrs. Campbell, and then tell her you can't be with her tonight. Would you? Well, if I do this to you, then what will you do for me? I knew you were going to ask me that question and I want you to know I'm totally unprepared for it. Would you take me out on a date sometime? It's a deal. Oh, you dreamed, are you? Oh, I'm going to. Now, you're sure you know what to do? Yes. I called Mrs. Anderson, say I'm Mrs. Campbell, and that my husband, oh, Mrs. Baker, what's the matter? Just saying I had one made me all goose-template. Please, we have to hurry. Well, all right. I'm going to see what you do to me. The blood is just racing through every inch of my body. Oh, it's probably just trying to get the trip over with. Oh, Mrs. Baker, go to work. We'll continue our day and the life of Dennis Day in just a moment. Meanwhile, here's Dennis to sing, I'm sorry, but I'm glad. Sorry, but I'm glad you're low, because if you weren't, you really wouldn't care. I'm so glad you haven't any peace of mind or another heart to share. Sorry, but I'm glad you're crying because you're dream, but if it makes you feel a little better. Well, Mr. Anderson's story to his wife that he was visiting Mr. Campbell's house tonight seems to have been a highly successful fabrication, thanks to a phone call from Dennis' friend, Mrs. Baker. We find him now with Dennis and Mr. Campbell at the club smoker, which seems to be in full swing. So the farmer looks at this brother and he says, no, by cracky, not till the place of corn goes up. That's the best I've heard all night. Dennis, didn't you like that story? Oh, sure. When I figured it out, were you here laughing? You had to bring him, I suppose, Anderson. Well, he's a good boy. Besides, it makes my wife less suspicious. Yeah. We sure fooled him with that story of being at each other's house, didn't we? Ah! We sure did.  Oh, sure. No question about it. Men are much smarter than women on the average. Not till the price of corn goes up. Of course, now and then you run across a case that drives the average way down. Hey, look who's coming over to our table. Wow, Tassel Latour. Must have heard me whistling at her while she was there. Having a good time? You bet, Miss Latour. I'll say. Oh, yes, ma'am. Your singing was just wonderful. You wouldn't kid a young girl, would you? Oh, no, ma'am. Or you either. Hey, no attention to him, Miss Latour. He isn't half like us. Yeah. Hey, you're Jay H. Camelobanker, aren't you? That's me. Nobody draws interest like I do. Ah! I had you spotted. Mind if I sit down? Park it right on my lap, lady.  Gee, how smooth can you get? There we are, baby. Comfy. Perfect. OK, Dave, snap it. Right, hold it. Perfect shot. Thank you. Hey, did that fire? Oh, sure thing, Cuddles. My press agent needed a shot of me sitting on the town's most prominent lap. Well, publicity, huh? Publicity?  Oh, see you tomorrow morning on the front page, Jay H. So long. Oh, no. No. Dave, that's a good one on you, Camelobanker. All she wanted on your lap was a picture. Oh, yeah? Have you forgotten you were sitting right next to me? Well, your wife's there when she sees me. Oh, my sacred Aunt Sally's polka dot animal castle. What are we going to do? My wife will leave me. Mine will leave me lying there. Think of something for heaven's sake. Yeah, anything. Well, we told Mrs. Anderson we were going to look at pictures of Mr. Campbell's fishing trip. Let's tell her that this was just one of the pictures he took on the trip. On a fishing trip? How do they explain Tassel's Latour? Live bait? Wait a minute. By George, I think I've got it. That photographer is a Newspaper man, right? Well? And a Newspaper man can't resist a story, right? Well, what of it? Well, in five minutes, there's going to be the biggest fight in the riot in history right across the street in Clancy's Tavern. Oh, boy, can we see it? You're going to be in it. What? Don't you get it? We go over and take a fight with a couple of guys. John stays here, and in five minutes, he starts yelling, riot, murder, big fight across the street. Yeah? Sure. The photographer runs over to take pictures, and we grab his camera and smash it into an unrecognizable pulp. By that time, we'll be kind of hard to identify ourselves. It's our only chance. Don't you see, they? Come on, Dennis. Now, remember John, five minutes. Oh, boy, all the trouble I'm getting into over this thing. I might just as well be in the same position as you fellas. Don't be silly, Dennis. Tomorrow, you will be single, but our trouble never stops. You see anybody we could pick a fight with? Hey, how about those two over there? Where? In the corner, see? One of them's putting on her lipstick. Don't be silly. This has to be a real struggle. Yeah, I guess they do outweigh us. Hey, look. Those two big Marines over there. Now, that's more like it. They look like murderers. Are we in luck? Yeah, someday, everything goes just right. Oh, they're perfect. And, you know, if one fights, they're both fights. Men in uniform always stick together. Yeah, but couldn't we wait for a couple of Western Union boys? Oh, no, this is it, then. Now go ahead. I'll be right behind you. Gosh, I don't know how a fight starts. I've always been single. Well, here goes. Good evening, sir. Good evening. Oh, yeah, you and who else? Yes, that's all. Oh, mister. Come outside and call me that. What are you talking about anyway?  I'm going to hit you right in the stomach. What is it? Come on, fight. I don't want to fight. I thought so, Marines. See going bellhop. What a crummy branch of the server. I've been trying to transmit to the Navy for years. The Army and the Navy got it all over us, Marines. Oh, yeah? Well, I think the Marines are the best outfit in the world. And I'll lick anybody who says they aren't. Well, now you mention it, I have met some pretty nice ones. Hey, keep off my side, will you? Look, uh, getting kind of late, Sonny. I'm due back at the base. See you, huh? Hey, wait, please.    Look, kid, take a kit. Hereafter, lay off the torpedo juice and it'll shrink your brain. Even yours. Come on. Gee, I'm sorry, Mr. Anderson. Well, it wasn't your fault, Dennis. Well, it's all over now. Yeah, it looks like that picture will be in the paper tomorrow, all right? Yes. And when poopsie sees it. There's a point, as I could hold you. What a mess. Guns, knives, nice furniture, but look, it's, it's, it's murder. Yeah, yours and mine, first thing in the morning. Good morning, Dennis. Good morning, Mr. Anderson. Well, has she, has she seen it yet? No, but she'll be down any minute. And then our marriage will be over forever. And it was such a beautiful relationship, Dennis. We were Tristan and a soulie, Romeo and Juliet, all over again. Yeah, when you weren't Louis and Walcott. Well, we had our little differences, but we always patched them up until this. This is the end. If we could only keep her from seeing the paper. It's no use. She'll ask for it first thing. She always does. Yeah, but maybe we could tell her that, shh, I hear her coming. Good morning, Herbert. Dennis. Good morning, Mrs. Anderson.  What's this nonsense now? Have you the morning paper, Herbert? Oh, there is no morning paper this morning, Mrs. Anderson. No morning paper? Why not?  Well, what could cause such a sudden paper shortage? Too many people rubbing instead of blotting. It's funny. Now let's have the paper. You wouldn't want to see it, dear. Yeah, the news is awful. Oh, there was a big flood down south, a terrible flood. Florida is now located off Boston. We just couldn't stand the news, Pupsy. Hurricane kills millions on West Coast. Fire destroys Canada. Earthquake levels are whole far east. Little lab in a flood dog patch which moves. Now you can stop this silliness right now. I want that paper. But Pupsy. It's no use, Mr. Anderson. We've lied enough. Time now to tell the truth. What? Mrs. Anderson lies in trickery and deceit are far into my nature when I see they won't work. Your husband wasn't at the Campbell's last night. He was at the club smoker. The club smoker? Yes, the picture in the paper tells all. In the paper? Give it to me. Now, dear. Yes, sir. Yes, sir. Fine. The only picture here is of someone named Dave Collins, Tassel, a tourist press agent. It says his taxi was in an accident late last night, and all his camera equipment and pictures were destroyed. What? What? You mean if this fool had opened his mouth, you never would have known? Oh, no. Herbert Anderson. You have to wait for your turn. Dennis, Dave. Wait. No, Mr. Anderson, please. This isn't like you. Wait, you're not your daughter or your wife, you know. You, I can lick. Wait, stand back. Help, don't do that. Dennis Day will be back in just one minute to sing in the still of the night. But first, dream girl, dream girl, beautiful luster cream girl. Tonight, you can see this come true, revealed by a luster cream shampoo. You'll see your hair lovelier, your wave of curls softer, more glamorous, easy to do quickly. Even in hardest water, luster cream shampoo leaves hair three ways lovelier. Pregnantly clean, easier to manage, brilliant with sheen. Don't wait. Tonight, use luster cream shampoo. Not a soap, not a liquid, but a dainty magical cream. Discover why it's by far the top favorite cream shampoo. Get the big jar $1, smaller sizes, either tubes or jars. Tonight, you can be a dream girl, dream girl, beautiful luster cream girl. You owe your crummy glory to a luster cream shampoo. From the musical score of Rosalie, here now is Dennis to sing cold quarters in the still of the night. By parmaid soap, your beauty hope and luster cream shampoo for soft, glamorous, green girl hair. Dentists know what cleans teeth best, and over 4,000 dentists say Colgate Tooth Powder with a two-minute routine gets teeth sparkling and super clean.  Brush inside, outside, and biting surfaces. Always brush away from the gums. See how quickly this gets teeth naturally bright. It removes dull film that improper brushing misses. And Colgate Tooth Powder also sweetens your breath. Try it. Buy Colgate Tooth Powder today. This is Burnsmith reminding you the dentist day returns again next week. Same time, same station. Join us then, won't you? Good night. This is NBC, the national broadcasting company.


Last year at Real World Crypto 2017, a colleague of mine at Microsoft Research, Michael Narek, gave a talk on this very promising post-quantum cryptographic scheme called SuperSingular Assuming Difficult Monkey Exchange, or also known as SIDH. This talk today is a little bit like a continuation of that talk, but focused especially trying to summarize all our efforts to make not only this scheme and related schemes ready for the post-quantum competition that began a few weeks ago, but also try to make it as practical as possible. So, thank you to Melissa. I can keep most of the motivation part. So, I can say that we are going to focus on this talk on SIDH and also in a key encapsulation protocol that we recently designed and that we call SIDH. But before getting into the technical details, let me just give you a very quick timeline of the development of Isoini-based crypto. It all began in 1996 when Covenius described the first Isoini key exchange scheme. Years later, in 2006, after a series of papers by Rostoyev Stobunov, we had a key exchange using ordinary Isoinis. But the problem with all these schemes was that they were terribly expensive. They were impractical. It also was found out that they could be broken in quantum sub-exponential time. So, that was pretty bad. But this was solved, thankfully, to David Javan, look at the FAO, who looked at the problem and proposed a key exchange based on super-singular Isoinis. And that was in 2010. And this is the scheme that we know as SIDH. And with SIDH, we get much better performance. And also, we solve the problem of security because now the attack complexity runs in exponential time. And this is for quantum and also for the classical cases. Now, let's stop for a minute this timeline. Let me give you a very quick explanation of how SIDH works. Okay? So, in the setting of SIDH, what we have are elliptical subgroups. And these subgroups map to Isoinis. Okay? Now, a definition that helps us here is what we call a super-singular Isoini graph. So, in this graph, what we have are vertices, right? And these vertices are elliptic curves or, more precisely, isomorphic classes. And these vertices are connected to each other through edges. And these edges are the Isoinis, the ones that map one curve to the other one, right? Now, in this setting, we have a fixed Isoini class, right, for all these subgroups. And for security reasons, we need Isoinis that have a large degree, right? Another requirement that is important here is that we need these Isoinis to have a smooth degree. What this means is that if we are in the graph and want to walk through the graph to get to another curve, then we can do it as a small step at a time, right? So, to give you a concrete example, in practice, we instantiate these small steps in the graph using two Isoinis and three Isoinis. Okay? So, with this in mind, let me explain SADH at a very high level. We have a starting super singular curve, E dot. And then, at least, what needs to establish is an elliptic curve subgroup, in this case, using a secret essay. And this subgroup that we call it A here corresponds to an Isoini. With this Isoini, we can map the original curve to another curve that we call EA here. And this is actually E dot modulo subgroup A that we just defined. Bob, on the other side, does a similar computation to get to EB. And these two new curves are actually public, made public. They are exchanged between the parties, between Alice and Bob. It turns out that this information is not enough to complete a key exchange. We need extra information that I show here in this slide. We actually need a couple of evaluations on public points using these secret Isoinis. Okay? So, with this information at hand, then Alice can continue the computation taking the curve EB. And using a new subgroup also set up with the secret essay, then we get to a new Isoini that maps EB to a new curve, EBA. That is actually the curve EB modulo, this new subgroup A dash. Bob does a similar computation. And then what is interesting about these two new curves is that they are isomorphic. They actually correspond to this curve called here E dot modulo, the original subgroups A comma B. So, all these curves are isomorphic. That's great. Then we can use the J invariant of these curves as shared secrets. Okay. So, that's for the technical part of the SIDH scheme. Now, what is the problem here that is hard to compute? Well, let's look at these super singular curves in the setting, let's call them E1 and E2. They are defined over quadratic extension fields. Using a large prime P, we have the Isoini that maps E1 to E2. And as I said, the Isoini should have a large smooth degree. And then the super singular Isoini problem is the following. Given points PQ and the images of those two points, then the hard problem is to compute the morphism, the map, the Isoini map, right, here represented by phi. As I said, the best known attacks against this problem are running exponential time. We can see the complexities in the slides for the classical and quantum cases. And these are done through a generic low-finding algorithms. Now, at the time this was proposed, there were still two problems that remain. On one hand, the existing realizations were still very slow. They ran in the hundreds of milliseconds. And worse than that, they were unprotected against time in such an attack, which is a basic requirement nowadays to have a practical implementation. The second problem is that SIDH is not secure when keys are reused. So it's only recommended for ephemeral mode, right? So going back to our timeline, in 2016, we took a closer look at SIDH. This was a joint work with Greg Costello and Michael Naric at Microsoft Research, and we pushed harder on the performance issues to make it practical. So we proposed a new parameter set that we call SIDHP751, that targets the 128-bit quantum security level, and also proposed a series of optimization techniques that push the performance below 60 milliseconds. So that was a great improvement. And, moreover, the implementation ran in constant time as we wanted, right? So getting close to practice, to practical use, maybe for some applications, still not fast enough, and definitely still having the problem of static keys, right? So in 2017, we continued our efforts pushing hard on the performance issues and also looking at the issue of static keys, and that's why we designed this key encapsulation protocol that we now call SIDH. And the design of SIDH is due to Greg Costello, Luca DeFeo, David Yao, myself, Michael Naric, and Joe Srenes. This is a CCA-secure key encapsulation that uses a variant of the Huffman-Kill transform to transform a CPA-secure public key encryption to a CCA-secure key encapsulation mechanism, or KEP, right? And this transform is secured for both the classical and quantum random oracle models, which is good. Another observation is that we observed there is no performance loss when switching from SIDH to Psyche. This is specifically in the case where offline is computed, sorry, the key generation is computed offline. And, moreover, we also propose additional parameter sets, matching the brute force security of AES-128, 192, and 256. In the table in the slide show the details. The name for each parameter set is Syche, concatenated to the big length of the underlying prime. So we have Syche P503, P751, P964, and they correspond to the NIST security levels 1, 3, and 5, which are defined in the call for proposals from NIST. Now, let me give you a very brief explanation of how Syche works. First of all, we have a key generation stage. This can be seen as computed from Bob's side. So first of all, we have to establish a secret SB. And similar to the SIDH setting, that secret is used to establish an elliptic curve subgroup. And with this elliptic curve subgroup, we generate a public key that is called here PKB. And this public key is sent to the other party that performs the encapsulation process. This can be seen as computed from Alice's side. And Alice runs an encryption operation, right? It takes a message M, a new secret R, and then does similar computations to the previous operations, the previous processes, establish a new subgroup using this secret R, fixes, computes a new public key that is called here PKA. And similar to the SIDH setting, we arrive to a J invariant of the curve, in this case, EAB. And the secret here is the hashing of the message M with this cipher text. And now the cipher text is explicitly detailed here in the arrow that you see in the screen that is passed to the other party, back to the other party, that runs the decapsulation process. Now, the decapsulation proceeds to do the decryption and also a partial re-encryption in order to, well, to recover the public key PKA that was sent from the encapsulation party. And this one is compared with the original, the calculated one is compared to the original one in order to detect any, well, in order to make sure that the cipher text was well-formed. All right, if it is the case, then we should arrive to the same share key SS that we show here in the slide. And we instantiated hash functions in our case with Cshake 256. All right, so those were the details for Psyche. Let me just go through some other additional contributions that we have. We wrote a library that we call SIDH. We are at version 3.0 now and this version implements SIDH and Psyche, covers two security levels and contains a bunch of implementations, especially high-speed implementations for X64 and now for ARM V8 too. Also, there are no secret branches in the code, no secret memory accesses, so probably we can say that the code is protected against cache timing attacks on or probably not anymore. As always, the software countermeasures depend on the assumptions made in the hardware, and if the hardware fails, then there is little we can do about it. What we can say is that our assembly code, which has a very good chunk of the implementation, is not vulnerable to these attacks because there are no branches. For the C code parties, the things are more complicated. We have to make sure that we use the right countermeasures, but I'll let the Project Zero team explain it later with more details. We will hear about that today, I guess. But let me get to the timings, to the interesting part, to the practical part. As I said, we have the implementations of SIDH and Psyche, two security levels. I want to highlight in this table the nice numbers that we are obtaining after improving P751. You can see that the numbers for that security level are close to 30 milliseconds, so it's a nice improvement compared to the 60 milliseconds that we had before and even the hundreds of milliseconds that we had a few years ago. So we are steadily improving the performance, which is nice. And especially nice is that the version 503, the security, the parameter set 503 runs in about 10 milliseconds. So arguably, that makes these skins practical for many applications out there. We also have timings for ARM64 platforms, and this is thanks to an implementation by Matt Campania. And finally, let me point out that we have, we submitted Psyche to the NISPOS quantum competition that had a deadline a few weeks ago. The package can be found in this link. And here is the full Psyche team. A bunch of people working on theoretical aspects, hardware implementations, software implementations on different platforms. It's a multi-company, multi-university effort, a great team to work with. And I want to finish this presentation mentioning that in the last couple of years, we have seen a spike in the interest in SIDH and related schemes. That is great. We now see many, many works out there trying to improve several aspects of super-singular studies. So, for example, I can mention there are works on faster compression, making the public keys even smaller, which are, by the way, the smallest one among the most popular post-quantum candidates out there. We have optimized algorithms also and works on signatures, which is great. And I want to, you know, ask the community to continue putting effort on making super-singular studies even greater. So thank you for your attention.


This 2005 Pontiac GTO is stock number 1-2-0-0-2-z. We're here at Summit Automotive in Fond du Lac, Wisconsin. You're new and use sports car headquarters. This 2005 Pontiac GTO has the 6-liter V8 motor, which pumps out 400 horsepower. This car has been fully-safetyed and inspected by our service shop per the state of Wisconsin inspection process. It has a fresh oil and filter change. All the fluids have been checked and topped off. The car has been gone through mechanically 100% and is 100% ready to go. Phantom Black Metallic is the color we shoot all of our videos in 1080p, 60 frames per second. So if you have HD capabilities on your computer, tablet, smartphone, or television, turn them on right now because it is definitely your best way to check out the quality and condition of the car before seeing it in person. If you like the video, you can subscribe to our YouTube channel in the lower right-hand part of the screen. Click that subscribe button and then click the bell notifications to get updates on the videos we do each and every day here at Summit Auto. It comes with the factory-painted alloy rims. This rim is in excellent shape and it has BF Goodrich G-Force Comp 2 tires. These are 235 40 ZR-18s and these tires have a lot of tread left. In fact, you can still see the little wear knobs on there. These tires might be brand new if not 95% or more tread left. Front fender is in excellent condition. Headlight lenses are crystal clear. Factory fog lights, front bumper is in great condition as well. The hood is in excellent shape as well. And this whole car is just extremely clean all the way around. And we'll show that throughout this video. Passenger side front fender, no dents or dings. Passenger side rim, no scuffs or scrapes. You get the slotted rotors. And this phantom black metallic, it's got obviously a little bit of metal flake in it. Let's see if we can get a good look at it. There's that metallic in there. Looks really good in the sunlight. And as you go down this side of the car you can see just how clean that body is, how reflective and mirror like that paint is. I didn't see any dents or dings down this side of the car. I didn't see any on the hood or the fenders. We take these HD videos so if you are far away or even if you're close by and just can't make the trip down but you're still interested in purchasing the car, you can see the car, hear the car and have confidence in the vehicle that you're looking at before you even get here. So when you do get here there's absolutely no surprises. Back rim, very nice shape as well. And these back tires look to be just about as new as the front tires. And there's definitely, I don't see any surprises with this car. Coming around to the back, rear bumper is in absolutely perfect condition. We do have a passenger. We'll get him off of there. But rear, the deck lid, the spoiler, everything on this car is just in really, really nice condition. The interior is fantastic. Wait till we get in there. We'll be in there in just a minute. Coming around the driver's side, rear quarter looks really good. No dents or dings. And for full disclosure, this back rim, yep, we're four for four. Absolutely perfect as well. Rear quarter, really, really nice car. Driver's side door, no dents, no dings. Even the edges of the door seem to be pretty much perfect. Power mirrors inside the GTO package gives you the black leather interior. There are no rips, there are no tears on the seats. You get the GTO stitched into the backrest. And you always want to check on these GTOs, these seams. Sometimes they can sun fade and they start cracking, but this one's in really nice shape. Both these front seats, power factory floor mats, auto headlamps, and power mirrors and power windows in this car. Hop inside. You can see that you get the red faced instrument cluster. This one has 19,113 miles on it. Instrument cluster is very nice and clean. You get the leather wrapped steering wheel with the red stitching on the inside. No scuffs, no scrapes. Really nice condition. Volume and mode, and then next in mode, or volume and mute, I should say, comes with the Blopunct 6 disc CD changer. You have your climate controls there, AM FM radio, automatic transmission, parking brake, window buttons, passenger side format, and seat are in excellent condition as well. No rips or tears. The headliner is in very nice condition. No rips or tears on that. And just really nice car all the way around. We'll start it up. We'll also take a look in the trunk. We'll actually do that first before we start it up so we don't get fumed out here. And this one comes with a car cover. Not surprised at all for how clean the car is. It probably was on the car most of its life. Back storage area is nice and clean as well. And it comes with the car. Oh, look at this. It has the original window sticker and a whole bunch of documentation that goes with this car. Here's the original window sticker for you. Pretty cool. And it has a book with, I believe, all the receipts and everything that's ever been done to this car. Looks like an extra key fob and everything. Just amazing documentation with this vehicle. I'm really glad we came back here to look at that stuff. But that all comes with the car. Looks like there's extra copies of the window sticker. So you get all this with this car. Alright, we'll start it up and then take a quick look under the hood. And I'm guessing it's probably going to be as clean as the rest of the vehicle. Starts right up. No check engine lights. Nothing like that. Very nice and clean. I would personally like to thank you for checking out the video today. And hopefully from this video, you've been able to tell just how clean this car is all the way around. Those headlamps are working nicely. I know, I learned how nice and clean this car was from doing the video. Honestly, didn't know it was this clean. Let me get the hood to pop here. Oh, there it is. Under the hood, we have the 6-liter LS2 motor. 400 horsepower. Engine bay is very clean, runs very smooth. And it's just like the rest of the car. Absolutely perfect. And once again, this car has been fully safety and inspected by our service shop as a fresh oil and filter change. All the fluids have been checked and topped off. Shocks are doing a nice job holding that up. And this car is 100% ready to go. And to see more pictures of this car, or one of our other 450 new and used cars, trucks, SCVs, minivans, Wranglers, GTOs, Corvettes, Camaros, Firebirds, G9s. You name it, we got it. Go to that website right there, www.SummitAuto.com. Full pictures and descriptions of every single vehicle from two locations, all at SummitAuto.com. If you'd like to check out more HD videos, you can go to www.youtube.com. Remember to like, subscribe, and share on this video and all the videos that you see there. Click the bell notifications to get updates on videos we do each and every day here at SummitAuto. In fact, in a second, we'll see a link to subscribe to our YouTube channel in the upper left. A link to more GTO videos like this one in the upper right. A link to this vehicle on our website in the lower left. And a link to one of our latest YouTube videos in the lower right. Click those, check us out. And we're super excited to help you with this Ultra Clean 2005 Pontiac GTO in Phantom Black Metallic. I don't think you'll find a cleaner one. Thanks again for checking out the video.


My name is Björn Ulleros and I am a professor of popular music at the Faculty of Fine Arts at the University of Agde. I am more or less order deduct or self-taught. I have an education in classical music. My career became more and more focused on working as a performer, composer and eventually producer. Music is in many ways my greatest passion. It fills the entire day with all the nuances that music can provide. Any human situation can be associated with music. Music is in many ways the soundtrack of how we feel or a reflection of life. As a lecturer I handle a wide range of topics. My courses are based on a lot of research such as world music, music technology, music history and ensemble playing in different styles. The most important instrument actually to play the song or the melody is this guy. I know, but that's the way it is. I try to create a friendly relationship with my students and not only teach a student relationship with his old fashioned. It is about mutual respect between the teacher and the student. We are colleagues, we play and we create music and art together. Students from all over the world attend our study programmes and having international students is very important because they are the source of inspiration and the cultural input they bring into the classes is essential for the teaching. My professional music career is very varied. I work in several bands such as with my wife, Amir Glee, Bukhdebriusen also a secret guard and world music is kind of a parallel with all these groups. I have led several collaboration projects with international universities and university colleagues. The biggest one is without a doubt the research project Music Without Borders which actually had 52 musicians from 18 different countries and it considers the connection with students and teachers from different cultural outlooks as very important and informative. The university offers possibilities for everyone and that is how it should be. It is important to be inclusive and create experiences and diversity. Like every year in the spring semester I travel abroad with my students and especially in those situations like that everybody gets to know each other in a different way and create other forms of interaction that are decisive for the development both as a musician and especially as a musician.


The StreetBast program is a program that tends to be more informal, more relaxed, and it's out in the street looking at the hazards that exist in that local area. So we find that in communities where FRV is not necessarily going to work, the StreetBast program has been very, very successful. When you look at an audience, you need to say, well, these young people, they're a single couple. They've got no children, so they can be very proactive in their property maintenance. But with somebody that's maybe in their 80s or 90s, you know, maybe have a disability of some sort, they're not going to be able to climb up a ladder and clean their gutter so the community can get behind them and help them prepare their properties and things like that.


Bonjour tout le monde, bienvenue à la meeting d'infrastructure week-learn de Jean-Kinz. Aujourd'hui, nous sommes le 21 mars 2023. Sur le table, nous avons moi-même Damien du Portal, nous n'avons pas Hervé. Marc Waite, Stéphane Merle, Bruno Barton et Kevin Martins sont là. Annoncements, nous allons commencer avec aujourd'hui. Je n'ai pas encore checké. La bague a été placée environ une heure auparavant. Le changement final n'a pas été posté, mais Kevin a créé les updates sur le draft. Pour le faire préparer pour le final. Je ne sais pas quand ça va être préparé, parce que la dernière fois que j'ai checké ci.jankinz.io, c'était encore en train de faire un update sur la sécurité. Ok. C'est en revanche. Oh, merci. C'est très bien. Ok, très bien. La délice du conseil de sécurité. Ça devrait être bien, pour les prochaines heures. Je n'ai pas checké les portes de baguette, mais j'assume que ce sera rapidement là. Il n'y a pas d'issue dans le processus de relance. Je n'ai pas checké les loges et je n'ai pas accès à la VPN. Il n'y a pas de mal. On peut croire que Alex Brandes et les autres ne le prennent pas. Ok. Oh, quelqu'un est regardé. C'est ouvert. C'est bien. On ne le prend pas. C'est bien, c'est bien. Il y a un point de vue. On a l'air de voir un point de vue. Il n'y a pas de mal, mais c'est bien. C'est bien, c'est bien. On a l'air de voir un point de vue. Il n'y a pas de mal. Il n'y a pas de mal. Ok, on est à l'adviserie de l'Adviserie de Jean-Kinz, qui a été élevé aujourd'hui. Security advisory today, today on plugins. So as we said CIGEN Kinsaiyo is back. The advisory has been published on Gen Kinsaiyo a few minutes ago. So everything looks good, I haven't seen any error. So please update your instances and your plugins. Upcoming calendar next week will be, the next weekly will be 28 of March as usual. I don't remember the version, do I've lost track? 2.378. Or you say the upcoming LTS. 387. Oh, next weekly is 397. 97. Ok, right. Next LTS will be 387.2. And that will be on April 5. April, ok. And worth noting there the release candidate may already be available or soon to arrive. Chris Stern is release lead. So we had security release today. Next major events. The scale is finished. Mark is back home safely after visiting Los Angeles. So next really is probably CD con in May. Oh no, DevOps France. DevOps France April 12 through 14. And then CD con in May. Ok, parfait. Perfect, perfect. Is there any other announcement calendar events that you folks want to talk about? No. Ok, let's proceed with the work that we were able to finish during the past milestone. So first of all, a public apology. Stefan and I have let the poor airway alone last week because we were in holidays. And we absolutely gave no reminder to anyone. So you might have been a bit alone last week and I'm sincerely sorry for that airway. Next time. So self-improvement for the person going in holidays in particular them at the portal. Please really appreciate it. So at least raise the topic one week before doing the infra weekly meeting. I usually brag about being on holidays every day a month before. So usually everybody knows. That's like my birthday. I remind people all the time. So next week. We were able to update the VPN. So we were able to update the VPN. So next week. We were able to update the VPN certificate revocation list. It's deployed and it's okay. We received the calendar alert. The new calendar alert for the next version in six months has been placed. The issue is closed and everything is working as expected. No issue. That's a usual task. The credential for third.ci Allowing it to spin virtual machine as Azure agents. Were expired and we had to finish the work related to that topic. The last miles were being able to properly define a full terraform as code automation. So we now have a credential with an explicit expiration date in the terraform code, which is publicly available. So we should be able to monitor that. I don't know if you will have time for that. But at least it's visible publicly. Also on that issue. I've mentioned a topic that has been blocked by numerous people including Harvey and Tim Yakom. I've created a new issue for that. The goal is to use workload identity management inside Azure in order to avoid having to manage credential. So the issue that has been created with no milestone, we won't work on that right now. We'll just remove that password with the whole expiration and rotation and calendar event, etc. And instead that will be automatically managed by the cloud. That will be a nice improvement, but that wasn't the case on the issue. The issue was about renewing the certificates and the improvement was putting it as code. So we can track it. We have one year for that now. I've closed the issue related to Maven 17 because the initial issue was closed. One of the major changes we did two weeks ago was to increase the capacity on CI Jenkins. There were the hypotheses of splitting the workload on different node pools for the BOM builds and the other builds. Alas, right now, since today until the end of the month, we have removed a lot of AWS kind of agents because we went clearly above the billing limits from the AWS account. And adding two different BOM node pools is not right now something we should work on because we don't have the capacity. We had to decrease the capacity. So what we did is to ensure that the Maven 17 agents might be waiting, but they should not be hanging or not working for hours. Just a note, given the decreasing capacity and the risk here, we might need to do a drastic reduction on the way BOM, the BOM builds are done. We might need to add a lock system to ensure that only one BOM build is done at a time, whether it's on the main branch or on pull requests. So that has to be checked and studied during the upcoming weeks. Right now, we'll see the shift, the workload shift was done on Digital Assign where we have credits. So that's why we closed the issue. Unless someone object, we can at any moment reopen the issue, but if we reopen it, that will be a isolated topic. Yes. That's not the same problem to solve. That was an idea and that will be an improvement, but no need to keep the issue open. Agreed. And if we need to use lockable resources or something like that to say that we want only one BOM build running at a time, I think that's perfectly fine also. It certainly is, when a flurry of pull requests arrive from Dependabot for the BOM, it can certainly be overwhelming to see a thousand plus jobs in the queue and 200 machines allocated on ci.jankins.io. Next step. So that one, Stefan, under a new, so same problem as third CI, but in that case, it's for our Packer job. We need Packer to be able to spin Azure Virtual Machine to build our agent templates. So you need a credential for that. Now that credential has been defined as code with the same pattern as third CI. So next time it will expire, same problem. It has been renewed for one year, calendar, etc. And we could study in the future using workload identity management for the same reason. The main difference between both is the set of permissions required for both. There are subtly different. In the case of Packer, the main challenge is that we use Packer with the default Azure Mod, which was creating Azure Resource Group each time it was building. So it creates an ephemeral resource group, puts everything on that build inside that one and remove it at the end of the build. Now, we have restricted the credential because being able to create and delete resource groups at the whole subscription level was risky. So now we have one resource group where Packer put everything within. It's a bit less practical for the Packer process itself. However, that ensures that Packer only have writing access inside that resource group. So Packer is no longer able to reach the rest of the infrastructure on Azure. And we add to fine tune Packer and the credential for that. PK Geology and SSL Certificates. So in the long series of consequence of my mistakes by updating Python 3 on that machine, that one is another one on the list that has been solved. Thanks Mark for you certificate monitoring. We fixed by adding the missing PIP package. Yeah, but without your monitoring we would have waited for the exploration that would have been worse. Clearly, we have a room for improvement on the infrastructure team monitoring. We didn't have time or maybe the priority on that's both our reasons. But now it has been expired and it work and it was. The positive consequences that a bunch of SSL certificate were updated all over the platform showing that the Let's Encrypt system is still working as expected. What do we have? We have one issue that I closed after generating the notes for that. I forgot to post the message. So one of the plugin developer had one issue when releasing their plugin they retried a few hours later and it worked. The reason has been identified the repository permission updated job that run on trusted CI run every three hours and the TTL applications used to publish plugins is five hours. So every time the build run successfully at the end it regenerates the tokens. So if you have one failure then you will have one hour during while you cannot release. So the problem of the user is solved and we have tracked it. So I took on me on closing the issue and opening a pull request on the repository permission of data which aims to retry the steps at least one time. Because these failures are most of the time, at least on the path months, due to a GitHub API error. That's a five or four or five or three server side error. Alex is ok on that. Daniel suggested that we might improve the native Java or Groovy code of the repository permission of data jobs instead of the pipeline. But no objection on both. I understand one can be better but I need help on the second one. I'm not feeling at ease writing Java code for doing so. And I don't want to spend time on that as much. So we have a pull request with the request for enhancement. The usual problem is ok. So issue closed. Unless someone object, of course. No question. Issues that has been closed with no work on it or at least only analysis. Sounds like there was an issue on the docker up description of the Jenkins in BodeAgent image that Alex cooked. But someone fixed it or maybe mixed up. We don't really know but we checked earlier today and it sounds like it's gone. So not sure. I wasn't there every day so someone already might have fixed that and we missed it. But Alex closed the issue saying it's ok now. We had 1, 2, 3, 4 account issues most of the time as people doesn't answer. Thanks survey for managing all of them. No answer 1, 2 or 3 weeks afterwards. So my proposal is we close them and the user can feel free to reopen them if they need. 1 of the 4-1 was flagged as a sensitive a few weeks ago because it's someone asking for the Ops Genie plugin takeover. So we asked them to contact internally in Atlasian. They said they will and never answer back. So maybe it takes time or it's not a priority. Or it wasn't a legit request that can happen as well. Now work in progress. I'm taking them on the order of the list here. Could not create account. Someone had issues with the account. So we tried reseting the person. The person says they've been blocked by the anti-spam system. But the anti-spam system always throw a java stack in the logs. Neither airway or high were able to find this stack so it's worth. But we have more and more of this user. Not sure if there is is there something word running with account app or these people are trying takeover. Not sure. Maybe it's chat GPT for experiments. I don't know. Anyway, in that case, try to reset the password and the person will be guided to send us an email to the new email. We will check by asking an answer by email check the full back and forth exchange to see if that person is a human and is not trying to takeover. If it's not the case, then we can reset the email in the account directly. Main issue today we worked on EC2 that started as a lot of EC2 agent on CI agent, Kinsayo marked as broken states on the left column. It looks like there has been numerous issues with the EC2 plugin.  It was a 30 minutes by default when GCask wasn't specifying any value which we didn't because we used to have something as soon as it was used on the job finish we used to have agent being deleted immediately. I don't know when it started but it started to be 30 minutes. So once it's finished you have to wait 30 minutes before something pass and worst case check if the agent gets deleted or not. That leads to a lot of broken states mostly because spot instances but not only which is still something we can't explain here. But the consequence is that the AWS account went clearly above the budgets. So we did a drastic action by removing any kind of EC2 agent and decreasing the availability. We still have to switch fully infrascii from AWS virtual machine to Azure virtual machine that one will be definitive once done. So we should be able to leverage the amount of billing for this month and we should be able back to normal next month or maybe not. That will be discussed in April. But right now we absolutely need to avoid crossing the 16K top limit. Any question on this? So likewise the previous one they will move automatically to the new milestone because that means we still have work to do on this one. Ma event central package is not found on BuildAge I close that one too quickly I see you reopened it. Thanks for taking care of that. What is the status of this one? Sounds like you're muted. Is it on me? Sorry. Not muted. My problem maybe. Too many lines maybe. I don't know how to resolve it. I'm still in the same as 2 weeks ago. I need your help on this. Sorry, I didn't hear you need I need help on this. Ok, can spend some time on this after the meeting if you're ok. So we keep continue working on this one so that sounds good for you. Thanks. With that issue next issue is from James Nord about agent instabilities on CIG and Kinsayo. I can't grasp how to efficiently use Datadog. None of us were able to find matrix, but the matrix should be collected. So maybe they have been deleted after time window we need to fine tune. But a lot of information on that issue to say one of the builds failed with an error message. Clearly it's not OOM kill because we didn't see any 137 code and none of the usual, these kind of events are shown on the AWS or Azure console. In that case it was on AWS and no alert about pod or container being OOM killed. So that mean that the pod there was still an error. Assumption is that the pod was killed. So the machine could have been removed or maybe the spot instance was deleted and removed and there might be an issue in the ability to retry or to catch the issue. This morning we checked this is a plugin and the build plugin function use retry, the retry pipeline function and it should receive from Kubernetes when there is an event about the pod being deleted and not being drained or something exhausted in terms of resources. We didn't see anything and any retry kind on that job so that sounds like an edge case. Jams build was finally rebuilt two or three times and the pull request was merged. So we don't know what happened and we were unable to observe. Thing is the timeline was during the 2000 builds of the bomb that was on that gray area so gut feeling and only gut feeling I have no formal proof and I don't know but I don't have any way to prove where does it come from. So yeah not sure what to do with this one but any idea welcome there I don't know how to go further here because a lot of hypothesis and assumption but nothing factual or miserable here right. So my proposal is I asked Jams if he was able to to see that problem on another build or another plugin and the last thing for us to do is to check the spot history inside the AWS console. We have a history so we can see if some spot instances were reclaimed on that timeline that will explain the problem. So if it's okay for you we'll move that one in the next in the next milestone and if we don't have any answer back from Jams next week then we'll just close the issue explaining way. Unless someone else want to keep it all hot details. No objection. Okay. We have as your credential for CI Jenkins.io was due 2 or 3 weeks ago CI Jenkins.io wasn't able to spin as your virtual machines and ACI container. Same expired credential. A manual credential has been generated on short term that is valid until June. Now we have to put that one as code. The tricky part on this one might be around the ACI. We will need not only permission on the virtual machine resource group but also the ACI resource group for Windows container but the rest is the same as cert.ca. And also same improvement on long term that should be a candidate for workload identity management in the future. So yep that one move automatically to the upcoming milestone. PGP keys expire on March 13th Mark I took this one was related to the DG certs that we had to generate the PGP key with DG certs. But that might not be the case we should be able to operate this one quickly at least for generating the credential. Right. As far as I know now I hope that 3 years ago when we did this we left ourselves some facility that will allow us to do this without requiring that every user install the new key. But I don't know that for sure we've got to do the research to figure it out and we've got nine days to do it. So we absolutely need to start working on this one. Okay. Is it worth it to go to ask Olivier for help on this one? I think the first that Olivier would want is let's read the materials that were documented from 3 years ago go through them and be sure that we understood what they say and then if we have a question we talk to him but I'm confident given the experience with the DG cert thing where Marc said hey don't have any documentation Olivier then said yes we do it's right here look at this page read this page and it was all right there so I suspect the same thing will apply here is that we've got documentation that was assembled 3 years ago when we lasted this transition and we just need to read it first to be sure if we do need help from Olivier Okay we need to check the impacts that's the most important part do we need to can we just renew the key can we just extend its availability do we have to create a new one I'm not sure Right and that workflow is the key question is the crucial question not a new key and also of course what if we have to focus on depending on the workflow do we need to trigger a new LTS and core weekly release for signing again a new version with the new key if we need a new key and that I think we won't need to at last the last time we didn't what we did was we announced a we did a blog post the last time which said if you are changing please install the new signing key now I don't know if that kind of message will be needed again or if we found a way in our last exercise to allow that to be avoided again so avoided this time sorry it was three years ago I don't remember No problem so that means we need to check with the security team if there are any impact no security impact in that sense because this is all provider authentication provider provider validation information not anything to do with with vulnerability so last time we didn't involve the security team I think at all and they were just fine with it okay my question to them will be more about the impact of renewing the expiration date of an existing GPG key versus creating a new GPG key what we know the the consequences will be interested in the difference in terms of security pattern I see okay and in that case they're experts good thing to ask them that makes sense thanks out of space on the bomb builds survey do you mind giving us summary of what has been done on this one we noticed that the bomb build were using MTD volume to what they have to do and the MTD were using the node space available space the cluster node space which were 20 gigabytes and the build the bomb need more than that so they were filling we increased the cluster nodes disk size to 200 gigabytes and increase their IOPS and type we now need to maybe decrease size to 90 gigabytes it should be enough since there are at most three builds on each node at the same time and the bomb build after the bomb build we can see that 23 gigabytes are used that's a nice data point that we have we know how much space we need on worst case for running bomb builds we also need to check some volumes as they are limited as overlay as docker overlay and not as MTD and so they are they are not efficient as a matter of fact a good rule of thumb will be enabling the read only flag for any container whether it's Kubernetes container or docker container and then solve of the denying right issues by defining docker volume or Kubernetes MTD or TMPFS because these volumes are allowed to be written and the performances and the overlay as survey said are particularly poor so in the case of our builds for instance Kubernetes plugin on Jenkins as proven by chassis create an empty here for the workspace where the build happens which is good however on a default build when you run Maven for instance it creates and writes data in the home directory slash dot m2 repository by default that thing is written inside the container layering file system so if you need to read or write a lot of data the performances will be really bad there so we might want to mount explicitly the home Jenkins as an empty here now the question is we know how it behave with docker docker mounts the directory and copy the expected data on the new directory out of the overlay which is a few seconds more but in the case of Kubernetes we don't know also the slash TMP directory is not a TMPFS and is not an empty here so on to define that as a TMPFS a RAM disk that will take a bit of memory but we have margin on these machines worst case we use 24 GB of the 32 so we have a few GB left so mounting this slash TMP to something like 500 MB will be enough if it's full that means something is going very wrong because you even a build a Maven build shouldn't write that amount of data on a TMP here particularly because Jenkins provide a workspace underscore TMP environment variable which is a temp directory to write files within so these are improvements Erveille what do you prefer so do you want to continue working on that desk first question I will not but I need the help to check where these volumes are ok no problem do you feel we should keep the issue open and work this optimization as part of the issue or the definition of done or do you want to create separated issue as improvement now the problem is solved what do you prefer ok because since I did differently on other issues that way I am asking and both are fine it looks ok for you so just a note we don't have any more disk full issues for the bomb Mark can you confirm that you didn't see any more issues since Erveille's operation on that confirmed we cleared the backlog of 20 pull requests over the weekend and released a new version of the bomb early Monday so or Monday sometime 20 pull requests of the bomb during the weekend yes so it took quite a bit well it was a lovely weekend exercise to try to get that thing cleared and I'm glad that we did it because that meant that there were 36 dependency changes in the most recent release of the bomb 36 is probably 3 times larger than our typical bomb size release so it was time to catch up thanks very much for doing it ok so that means 6000 pods were were executed well one ok I admit one of the one of the things to catch up on those 20 pull requests actually combined six pull requests into one ok so so I did some I did some attempt to machine minimize but it was still at least 10 cycles of the bill of materials therefore you can approximate how many machines were built up yes it was a lot so that mean we that explain partly some of the increase of the AWS bill though but digitalized also it's part of the workload so yeah yes my apologies it probably was I tried to keep the cost low but you're absolutely right it was not free to run that to catch up on those pull requests ok so I will move that issue on next milestone buttons 10 à paradigm les 1 je m'en ai tout à fait rifles Jams 9 50 four non Est-ce que vous vous rappelez que le scope des changements nécessaires pour celui-là? C'est le shooting down release, c'est le CIO de Jenkins.io, pour voir mes questions. Ok, donc le CIO de release doit être le dernier mile avant de serrer, est-ce que c'est correct? Ou est-ce que nous avons d'autres services identifiés pour s'entraîner à ce cluster? C'est le dernier service. Nous avons besoin de bouger de ce cluster pour celui-là privé. C'est le suivi des services publics. Ok. Comment est-ce que l'opération doit être approximative pour vous? Je l'ai estimé jusqu'à aujourd'hui. Je ne pense pas qu'on a besoin de ces deux jours. Mais oui, pour être sûr, je l'ai estimé. Ok. Qu'est-ce que ça fait le plan d'entraînement à la fin de la semaine? Qu'est-ce que c'est le meilleur détail pour vous? Merci pour cette semaine. Ok. Est-ce que ça peut vous envoyer pour tout le monde? Est-ce que vous pensez que nous devons commencer cette partie de la migration? Si le plan est prêt. Pourquoi pas? Ok. Vous devez décider le temps d'un jour, mettre ça sur l'issue, et puis communiquer. Nous devons aussi préparer la communication. Nous devons aussi préparer la communication. Nous devons penser à l'accès de la VPN, parce que ça va requiser les clients de la relance de la CIO pour apporter les accounts avec notre aide, avec notre recommandation, pour qu'ils puissent utiliser les nouvelles instances de VPN privées. Oui. Est-ce que c'est le partenariat? Est-ce que c'est ok pour vous? Ou vous avez besoin d'un peu plus de temps sur cette partie? Non, ce n'est pas seulement le partenariat. C'est pas un problème. C'est-à-dire que vous devez... Est-ce que c'est ok pour vous de prioritiser le plan? Préparer le message, pour que les gens puissent savoir ce qu'ils doivent faire. Si pour les gens qui vérifient comme Christian, qui vérifient la relance de la CIO pour la semaine, qu'est-ce qu'ils doivent faire jusqu'à la semaine prochaine, pour vérifier et monitorer la relance de la semaine prochaine? Alors, on va définir le temps d'adaptation dans l'issue et la communication. Vous avez dit que l'application de VPN, c'est-à-dire l'accès à l'adaptation privée. Alors, est-ce que vous avez pu vérifier l'availabilité de l'application de Windows? Est-ce qu'il est capable d'attendre l'agent et tout? Vous avez dit que nous n'avons qu'à migrer la relance de la CIO. Nous avons besoin d'un set de tests de dummy avec un pipeline qui ressemble à la relance de l'application, mais ce n'est rien d'exception. C'est le matin. Exception d'agents? Je vais discuter avec ce acteur. Je ne sais pas. Je vais vérifier le plan d'availabilité de l'application. Si vous voulez. Oui. Oui, mais ce n'est pas sur comment, c'est sur quoi. Nous avons besoin avant de planir la migration, d'être sûrs que nous pouvons couper les portes de Windows et l'agent Linux avec la même définition de l'application que l'availabilité de l'application. Depuis que ce n'était pas le point que je disais, je sais que si nous pouvons vérifier le plan que j'ai fait, parce qu'il n'y a pas d'adaptation. Depuis que je n'ai pas d'adaptation, il y a déjà beaucoup d'adaptations. Non, ce n'est pas beaucoup. Nous avons besoin de vérifier le plan d'availabilité de l'application. Nous pouvons prendre ce temps comme objectif. Le temps d'availabilité de l'availabilité de l'application sera décidé seulement si nous sommesOK sur le plan. Est-ce que c'est OK pour vous? Oui, c'est parfait. Juste la dernière, parce que c'est juste ma pensée. Nous avons besoin de vérifier le point Azure pour l'availabilité d'availabilité de l'application. Juste pensez à ce point, nous allons parler de ça, mais c'est important. Réguis-le. Oui, des mesures importantes pour vérifier. Nous avons VPN, agent allocation, et nous avons credential Azure Vaults et points. OK. La prochaine tâche est appliquée pour la coopération de Morgenkind Manager et Jennifer Leaders, et cette est pas la question, mais je dois t'en ramassé un email pour les gens et on verra la réponse. Para celles que j'aielescère, c'était déjà le cas. Donc, ce sera mon erreur. Mais je rassure que ce soit собирé. Je ne m'en souviens pas de prendre ce que je vous ai dé Kolk. Je les ai envoyés la dernière fois. unless someone wants to take the subject, and I don't mind either. If they say no for Jenkins CI Infra, the alternative would be to use GHCR as suggested by RV, that could ease the access control and that could scope the images per repository since we really have a kind of airbag permission system inside GitHub. Oh, GHCR is the one in GitHub. OK. Yes. If not possible, we could move to GHCR, GitHub registry. Sure. Ah, you need to write down. Rose better airbag already managed per repository. Risk, in that case, outside the fact that we only have to change the name and create GitHub tokens, that should be OK. That would be pipe and library change. Instead of using the pre-built Docker Hub credential, we use it with IAT, the GitHub application, one-hour value token generated on each call. So we should just wrap a risk credential with the GitHub app and that should be OK. The risk is more rate limit costs in GHCR. I don't know the limitation, but maybe it's free for us since we are sponsored, but that remain to be checked. I mean, GitHub action have limits on GHCR as well. For Jenkins forever, we'll see, we'll discuss. Is there any objection if I send an e-mail to ask the developer what do we still need that one and would GHCR be a solution for this one? Because that one produces unsafe artifacts, so I would rather having that one removed from Docker Hub and not used anymore. But maybe I'm missing something and let's ask the contributors. We have a service that should be sensitive and removed, Robo Butler. That one should be an easy task. It's a set of puppets. I propose to move it outside the next milestone given the work, but that one is uneasy to take if someone is bored and have some time to spend. Is that OK for you? Let's move to backlog. I am not sure what is the Gatsby plugin Jenkins but it shows about, can you, do you remember? Yes, it's about an issue which has been done and you were not sure if we should create a separate GitHub action just for the semantic release action. For me, it's not needed, but I'm not sure. A GitHub action? There is a GitHub action to do the semantic release on this repository and it's the same I've reused the GitHub action from the Jenkins IO components repository and you were not sure about that and you mentioned which might need to create another GitHub action for that. Mike, Oh, a GitHub application, do you mean? OK, GitHub action is a CI system. OK, sorry, that's why I was confused. You said GitHub action, that's not a GitHub action here, right? Or did I miss? Sorry, I don't understand. It's a specific process for the release on this repository and it's using a GitHub app. OK. And you were not sure if we should have used the same GitHub app for these two repositories. OK, I see. Yeah. The risk here is if one application tries to write or perform a release on another repository that use the same GitHub app, then you could have cross repository writings which should not be possible by default. So that's why ends my proposal of creating multiple GitHub app one per repository, but that could be one per area. The question is more, is it acceptable if, in our case, Jenkins IU components that you see on the screen, is the risk of Gatsby plug-in Jenkins layer being able to write on Jenkins IU components? Is this risk acceptable or not? Otherwise, we could increase the scope of GitHub app to, let's say, an area of particular technology or services that have a link between each other. That's my concern. Pour the Jenkins infrastructure that looks like the same area, I will put that under the umbrella of whatever front-end web stuff. The thing is managing manuals, all those GitHub apps start to be problematic and as you underlined correctly, or the last time, now I remember, the amount of manual management and credentials to updates could be a counter-effect of trying to separate properly elements. Unless we have a GitHub app management as code in an automated way, your argument makes some survey and I propose that you can close this issue. It's okay that we don't separate GitHub app because that will be another world topic on that one. Does everyone agree on this one or do you think we should? If I understood correctly, we lower the workload by having some kind of risk but lower level instead of separating everything and having to handle all the credentials. If it's okay for all of you, I will close the issue with a message about the trade-off here. Does it make sense for all of you? Thanks, sir. That means the issue is fixed technically or functionally speaking and we only have to write on the trade-off. Thanks for handling that. To be closed, trade-off secure in term of security and permissions. We have another issue to work on grant access to some security folk to release CI. These people need to be added on both the VPN the new VPN eventually I'm crossing my fingers for this one but they need a VPN account in any case and then in the release CI airbag system. Also we need to check the airbag configuration on release CI because right now anyone with the VPN access and authenticated has too much permissions. So we need to create an airbag matrix inside Jenkins. So that task must be done quite quickly. Not sure what's gonna make it I will move that to the upcoming milestone by default I will take it unless someone want to help me or work on it.  For me, we won't have time next milestone but I want to put it just in case. Update center job is failing. That one the root cause is fixed Ivan closed it yet there are some puppet management things to ensure that we have the correct Blobix for install everywhere and we have to perform a Blobix for upgrade migration that could have consequences on a lot of scripts but I think we will have to do this one quickly however that was the point last time but I saw that was able to solve some issues on other unrelated repository but that also use Blobix for and I don't remember if the the work that you did or team did on this area were able to use Azure CLI instead of Blobix for Ivan stuff OK so if it's OK for everyone the definition of done for that issue will be the second item here meaning putting on the infras code a way to ensure that Blobix for is installed that should be explicit on puppets because it was done manually before once it's done we can close the issue that will be the improvement to avoid reproducing the issue the Blobix for upgrade campaign should be a subsequent issues if it's OK for everyone it won't be priority that could be superseded by the migration to Azure CLI instead that's why I want to make it another issue is that OK for everyone then code signing certificate renewal process that one is quick we are waiting for lawyers of the Linux foundation to discuss with lawyers of digital and lawyers of CDF and once then the CDF Fatih from CDF will come back to mark with a new digital a new certificate to sign the MSI of Jenkins on the jar the impact shouldn't be that big but that should be better if we could have that renewed otherwise anyone trying to run the Jenkins.msi installer will be congratulated with hey no don't I'm not really sure of all the impact though from our point of view in the infrastructure that mean we will take the new private certificate and put it on the Azure Vault which is used by ReleaseCI through the Vault endpoints and my remark earlier ReleaseCI use it to sign the jar and the windows package and that needs to be encrypted inside the Azure Vault password system so that should be only a Vault update so we have to unseal the Vault put the new version seal it and wait for the next release to trigger let's try a replay with a dummy command that say hey do we have the five first character of the key inside just to validate it's mounted correctly so nothing for us there that will move automatically to the next that one is outside our hands any question on this one ok the rest is artifact caching proxy can you confirm that I did everything you needed for merging on javadoc the javadoc project yes I haven't checked is it working as expected or did you had time to check if it was working because it's once a week or I haven't checked on just ok it was running as expected cool so that mean it uses ACP right it's using ACP on CI and it should not entrusted so that should continue working as before is that correct nice job is there any other ACP topic outside the issue you were dealing with are there other projects or can we say that one is almost being able to be closed isn't that lovely that's a big one sorry and that's a big one I mean ACP it's huge but I didn't hear what Serge was saying oh ok so once we are sure that javadoc is ok the last mile for us will be to check can I ask you to drive that topic so you should be able to close the issue the goal is to check the measure from Gfrog to see we have our top IPs and if they are eating Gfrog less than it was in December at least Mark might be able to help and Basil as well and if you see we have decreased and we are not on the top whatever that mean we can proceed and close that issue sounds good to you that will be your end of quarter victory on the real line sorry that HA work in progress I wasn't able to work on this one I need to focus on how to have a replicated LDAP especially inside the Kubernetes the last one computer and BMC plugin removal is just for information in our case Danielle created it, if it's ok we will remove any milestone it's just to track the work of there has been a copyright infringement we received the notification by the Github whatever system used and the Jenkins project at free day to comply so it has been treated by the Jenkins board yesterday and all of the plugin related to compare and BMC has been removed because of the copyright thing the issue there has been an email sent to compare war people by the board Mark also copied the content of the email on the issue there is no infrastructure action right now it's only to track this and Danielle did that as part of the LDAC process any question so I know that's a lot taking a lot of time but we need to check if we have new issues that hasn't been triage right now we have this one I want to create a new account update social link on Josh organization monitored ACPD excusez-vous c'est déjà fait c'est fait ok c'est la question d'aujourd'hui pas de problème si c'est ok pour vous, je vais prendre les issues pour vous remercier quelque chose ok c'est le même c'est le même c'est le même non c'est moi je ne sais pas qui vous référez c'est le même mais c'est le même vous n'avez pas filteré non je ne sais pas je suis juste filtrant avec ma A3 ok donc nous avons 2 tâches d'account et le même c'est plus facile ok je vais les mettre et ce sera fermé parfait d'autres topics ou des issues ou des choses que j'aurais mises ? non ok donc, laissez-moi arrêter la recordation pour tout le monde qui s'occupe, à la prochaine week alors arrêtez de partager, arrêtez la recordation


He had the second big pinch hit in that seventh inning. The first came off the bat of Gio Orcella. Let's hear from Gio. Hey Gio, just what do you think of the way that Domingo Hermann followed up Kluber's unbelievable performance with another solid pitching performance this afternoon? I'm really happy for Hermann. The way he pitched today, that's impressive. He's been pitching really, really good. And I feel so, so happy for him.  Did you feel like you needed that? The need needed a little bit of a rest? No, I mean, I'm always ready. I was just getting a little rest, but I was getting to be, I was thinking like you're ready for any opponent in the game. So that's happened and I played today. When do you start getting the indication and when do you start preparing, thinking that you may get an opportunity there in that seventh inning to pinch hit? I start getting ready when I wake up this morning. Next to Marley for that.  Do you think this is something that is going to completely heal? I mean, there's something that I have to take treatment every day, something that is getting better. I feel way better today. I think one day just disappear, but I'll be good. Gio, anything happened to your hand when you were trying to stretch on the ball in the dirt?  Oh yeah, I just put my fingers in the split a little bit. So with the speed of that, I just, a little bit, but it's fine. No cuts or bruise anything? No. Okay, thank you. You go next to Betel and Machame.  How did that feel? How were you able to essentially deliver a win for the Yankees today? Yeah, so it always feels good, trying to do the little details to help the team win. Today was the case, and I feel like real happy to help my teammates.  Okay, what was that? Yes, sir. With how well the pitching staff has been pitching, and especially today with Ramon and the ball pen. Did you think even though that was only one run, that would be enough to get you guys the win? Yeah, that's bringing a lot of energy to the team, the way they're pitching, like they create a lot of confidence in all of us, and I'm really happy for the work that I've been doing.


This makes you unreachable to the narcissist. This makes you unaccessible and unapproachable. Where it is not possible for them to get a hold of you. And it all starts by realising what is causing you to hold on to the narcissist.  Victims of narcissists often hold on to hope. They hold on to a feeling of expectation and desire for a particular thing to happen. They hold on to a feeling of trust. Because they want something to happen. They want things to change. They want things to be better. And they still believe in the narcissist. They have confidence in the narcissist potential. The narcissist will often show you that they have the capacity to develop something in the future. They will show you that they have qualities or abilities that may be developed and lead to future success or usefulness. And that is what causes you to attach yourself to them. That is what causes you to depend on them. But you're hurting yourself by doing that. It puts you in a difficult and confusing situation. And you get so involved in it that you do not notice other things about them. You don't realise what is happening to you. Holding on to a narcissist potential can ruin your life. You keep trying to make them become who you need them to be. But you need to realise that you are seeing their potential right now. They didn't stop making progress. This is the result of their potential. This person who is abusing you. This person who made all of these promises about the future. This is who they are. And they're quite happy with it. They're quite comfortable laying in their own filth. They don't have any desire to change anything. Which is why you're the one who is doing all of the work. You're the one who is unhappy with less love. Less affection. Less communication. The narcissist is quite happy with it. They don't see anything wrong. Because this is what they used to do. It's familiar to them. So they just expect you to accept it. Or you have to move on. Because as long as you're with the narcissist. It's always going to be an emotional rollercoaster. It's always going to alternate. Between making you excited and happy. To making you sad, disappointed and desperate. That's never going to change. It's never going to be enough for you. But you may accept the breadcrumbs. Which they will use to trap you. They will give you small signs of wanting something. But in reality they have no intention of formalizing. They have no intention of giving it a definite structure.  To keep you in their sights. Because they still find benefits in keeping you around.  Of whatever they think you want to see. They will give you small signs of affection. But it's only to keep you from moving on. The narcissist will seem to love you the most. And you've got one foot out the door. But when you accept their potential. You will end up separating yourself from reality. It will put you in a difficult and confusing situation. You need to get back to reality. The narcissist will show you their potential. Because they don't want you to see the reality. They want to keep you fantasizing about what they could be. They don't want you to see who they really are. Which is why they breadcrumb you. Which is why they give you morsels of attention and affection. It's to keep you thinking about how things could be. If they put all of their effort into it. Because if they gave you all of their effort right away. You may not like them as much. You may think that if they showed you who they really are. You would still love them. But when victims see who the narcissist is. Underneath their mask. They don't love them anymore. If they showed you who they really are from the beginning. You wouldn't like them to become unreachable to the narcissist. You need to avoid thinking about their potential. You need to accept that everything they're showing you. Is who they actually are. There is nothing else. Everything they had to offer to you. Is what you've already gotten. There isn't some other wonderful side. To their personality. You've already witnessed everything that they had to offer. That was the real thing. Thank you for watching. I hope the video readied on it with you. Please like, comment, share and subscribe. If you would like to donate. My PayPal link is in the video description. Coaching inquiries. You can email me at coaching.naxify.uk Thank you for watching and I'll talk to you soon.


What's good, Joshua Ross back again with another video. So I want to talk about this particular fantasy booking idea that I've been seeing a lot lately on social media. And that is the idea that Seth Rollins will turn on Cody Rhodes at this year's WrestleMania. Now, here's the thing. I know some of y'all just want to see the world burn and want to see Cody get screwed over once again at this year's WrestleMania, but it has to make sense. Now, Seth Rollins and Cody, they've had their issues per storyline in the past. And to be honest with you, Cody is pretty much won the feud in every instance. And if it was for the World Heavyweight Championship and that was the story they were trying to tell, obviously, I think we would probably have more of a heel. Seth Rollins in that case. But considering the story they've been telling so far, I think it's going to be a little bit different this time. I think the story they want to portray is WWE, the guys that are there day in and day out versus the bloodline, the people that aren't there and kind of abusing their power. We've seen time and time again how Roman Reigns uses the bloodline to help him win matches. We've seen it with Seth Rollins. We've seen it with Cody Rose and plenty of other people. So the whole championship that Seth Rollins has was initially created so there could be a top champion of sorts on on WWE television. Because right now it wouldn't have been anybody other than Roman. And Roman, this is most we've seen him in quite some time. So that's really what the story they've been building with Seth Rollins title reign as a whole is the the everyday working horse, the working man in the company in and trying to put on best matches. And Roman Reigns is the guy that, you know, the must see attraction that doesn't have to be here or be at these shows often at all because he knows he's the top guy. You feel me? So it just wouldn't make sense if they set it up the way they have. Where Rollins has Cody's back. He doesn't like what the Rock is doing. He doesn't like what the bloodline is doing. Hell, it really doesn't make sense for him to turn on Cody, considering that the Rock and Roman Reigns have both been cooking Seth Rollins at 400 degrees temperature in the oven, like legitimately they have both made him seem like he's a J.A.G. He's a joke. He gets called a walking clown emoji. Like they don't take him seriously and you have the Rock threatening to take his championship away just because he can. It makes no sense for him to turn on Cody, the guy that has his back. The guy that's trying to make things right in the company to put things back in order that that wouldn't make any sense. Some of y'all will say, oh, well, he hasn't beaten Cody yet. Still makes no sense. You can do that sometime down the line if you wanted to. But once again, what story are you going to tell after that? Oh, now we're going to do another feud with Seth and Cody. No, even when they were teasing the idea of Cody choosing Seth to main event WrestleMania, you heard the fans reaction. No one wants to see that. We've seen it enough. Nobody wants to see it there. I don't think there's anybody right now that wants to see that match. Maybe some of y'all do, but the majority fans don't want to see that match because we've seen it before. It doesn't it won't change anything, even if Seth does get a win. He still would have to win more matches to make it even even in their little rivalry feud they have. So no, there's no point in doing that. There's no point of having a swerve for the sake of having a swerve because it makes no sense in the grand scheme of things. It doesn't. It doesn't. I think the overall story they are trying to tell now is WWE versus the bloodline. And the reason why I say that even more, because the rock is mentioned and had some interactions with Triple H multiple times and pretty much disrespecting him. And we all know Triple H is, you know, he's cool with Seth Rollins. Seth Rollins is a Triple H guy, you know, so there's some history there. So it just wouldn't make sense for him to turn considering that he's trying to make WWE a better place in a sense of, you know, champions being there and and on a full time schedule and also not having people just, you know, do what they do whatever they want on the show, especially the bloodline members. That's literally what the vibes I'm getting. So it just for me, I think that's just kind of like nonsensical booking. That's just people wanting to see the world burn. I know it looks like that. And there could be some instances where you think maybe he's going to turn. But once again, that makes absolute no sense because now essentially, if you do do that, you mess up Seth Rollins character because that's just OK, but I can't even put into into words how that just makes absolute no sense.  Go after them, not after after Cody, that makes no sense. And if you do have Seth turn on Cody, there's another pointless for you. And then fans are not going to really care. Like Cody lost and this time it was because of Seth. I don't want to see that feud. I don't my interest level for that feud instantly goes out the window. And my interest level for Cody, I'm going to be honest with you, it dies down significantly like it drops significantly because once again, he's now he has to overcome Seth again. This is a story in a few. We've already been down before, been down the road. It's done. So I think they need to focus on a story at hand. Seth and Cody trying to level the playing field in WWE. And I'm sure there's going to be more people that are aligned with Seth and Cody in the end. Like they're building this up like a very big end game. Night last year was part one of, I guess you could say, the Infinity War. If you want to compare to in to Marvel MCU, Night One was Night One, not Night One, but WrestleMania for 39 was Infinity War. And WrestleMania 40 is going to be the end game because this is it. They they they're assembling their team. So it just doesn't make sense to have Seth try to screw over Cody because it doesn't help him in the end, to be honest with you. It doesn't help him because he still would be under the the the the ruling of whatever the bloodline wants to do. So it it really doesn't help in a sense, considering they've been talking trash about each other, it just it doesn't help. So I just wanted to put that out there. I've seen a lot of people on social media saying, oh, Seth's going to turn or Seth should turn. No. Sometimes the simpler story is the better story. Have Seth side with Cody and have him do whatever he can to help Cody out to overcome the odds and finish his story. And then from there, you figure out what you want to do from there.  But you're going to turn on a guy that has your back.  There's no reason to do that. And then it just kind of kills Cody's momentum going forward in WWE, which I don't think they need to do. So that's just my personal take on it. Comment down below. Let me know. Do you guys feel like that fantasy booking makes sense? Would you guys prefer that to happen? Would you want Seth Rollins to turn on Cody or would y'all like where things are going right now where Seth and Cody are on the same page trying to take down the bloodline and and bring WWE back to, you know, where it should be, where, you know, the wrestlers that are there day in, day out. They are the guys. They are the girls that are, you know, trying to push the company forward, not the bloodline and, you know, the powers that be with them. So y'all let me know down below, but I appreciate all of the sport. Road to 150 K and I'm still going to be the YouTube wrestling champ of the world. Appreciate y'all kicking in with me. See y'all next one. Peace.