Good afternoon, ladies and gentlemen. On behalf of the Commander, United Nations Command, Combined Forces Command, and United States Forces Korea, General Paula Kamra, welcome to the activation and assumption of command of US Space Forces Korea. I am Captain Monica Callan, and I will guide you through today's events. Please stand for the arrival of the official party and remain standing for honors to General Kamra, the national anthems, and the invocation provided by Chaplain James Pitts. I invite you to pray with me, giver of life and love, creativity, and inspiration. We give you thanks for this day and as many blessings. We are grateful for the call to serve and defend our freedom, the will to sacrifice for things worthwhile, and the means to defend each other and the nation we call home. Grace our ceremony today, not only with your presence, for we seek also your blessing. For Lieutenant Colonel McCullion, who with four words will take upon himself tremendous authority and immense responsibility, may he lead boldly with wisdom, strength, and joy, for command can be an arduous yet fulfilling journey that affects so many for so long. For his family, Mandy, Egan, and Kira, may their love and support never waver. May they equally serve with the rare elegance that is fused with strength and resolve, and may they enjoy a cohesion of family needs not to survive but to thrive. As U.S. Space Forces Korea stands up, we pray for a smooth transition in our organization, the enhancement of space capabilities and support, and our increased effectiveness against any adversary anywhere in the world. Bless us all, O Lord, in the defense of freedom, and as human beings, enjoying and perpetuating that costly freedom, these things we pray in your holy name, amen. Thank you, chaplain Pitts, and the United States Eighth Army Band led by Chief Foreign Officer Five McCulloch. Ladies and gentlemen, please be seated. We are fortunate to have the honorable Philip Goldberg, U.S. Ambassador to the Republic of Korea with us today and other distinguished visitors. Ladies and gentlemen, it is my distinguished honor to introduce the commander, U.S. Space Forces, Indo-Pacific Command, Brigadier General, Anthony Chachi, Master Leader. Ladies and gentlemen, distinguished leaders, commanders, warfighters, what an exciting historic day. I am deeply honored to be here representing General Salzman and the United States Space Force for the activation of U.S. Space Forces Korea. And I am even more honored to share this moment with all of you. Thank you for being here today. I'd like to begin by recognizing Secretary Austin for approving this support and command. It was a very deliberate stroke of his pen that paved the way for the activities here today on pen. General LeCambre, sir, thank you for hosting today's ceremony and your continued support of Space Force Guardians. I believe today marks an important contribution toward your enduring commitment to combat readiness. Ambassador Goldberg, sir, thank you for taking the time out of your busy day to be here with us. General Poitz, Chief Dyer, your support for our guardians on pen has been tremendous. And we look forward to building on our close relationship with the air component going forward. General Ahn, Lieutenant General Park, you honor us with your presence today. I am deeply grateful for your work in advancing the alliance. After assuming command of U.S. Space Forces Indo-Pacific, my number one goal was to establish a subordinate command here in Korea. Why? Well, because the soldiers, sailors, marines, and airmen of the Republic of Korea Armed Forces deserve the best the Space Force has to offer. Our partnership spans over 70 years, serving as a pillar of stability in the Indo-Pacific. And our ironclad commitment to each other has never been stronger. To that end, I was inspired recently to read President Yoon's comments outlining his commitment regarding enhanced space cooperation within the alliance. It is clear that his leadership delivers results. And I'd like to take a moment to congratulate the Republic of Korea on your successful launch of Nuri this past summer. You have joined an exclusive group of nations capable of delivering a one ton payload into orbit using your own national space lift capabilities. The technological prowess here continues to grow and will only help our partnership flourish. And the professionalism and commitment of the rock armed forces to deterrence is a model for others to follow and greatly enhances the strength of our alliance. More importantly, it is critical to the defense of our nations and our whole lands. The AOR has long embraced the value of joint coalition integration during the 625 war or what we call the Korean War. Korean and UN forces turned the tide with the daring amphibious assault at Incheon. Air, naval and land forces combined with their unique strengths delivering a crippling blow to the enemy, setting the stage to roll them back over the 38th parallel. Today the importance of integration has only grown and activating US space forces Korea here today is a reflection of our commitment to joint and coalition war fighting. This team will elevate the integration of space personnel and better synchronize combat effects from space capabilities into the joint coalition operations in the Korean theater. These guardians know this theater better than anyone else in the US space force and are ready to leverage their expertise on behalf of United States forces Korea, combined forces command and United Nations command. Before I close, let me share a perspective on integrated deterrence. United States ability to synchronize in all domains is unparalleled but there is no integrated deterrence strategy without the underpinnings of space. Space creates opportunities where there otherwise would not exist overcoming the tyranny of distance, increasing the combat effectiveness of our weapons systems and projecting power at the time and place of our choosing. This new command will ensure that the space capabilities enabling integrated deterrence are ready to fight tonight, elevating our combat readiness on the panel. Moreover, they stand ready to further synchronize space operations against any adversary in our AOR. Whether it's through participation in combined events, conducting exchanges with our partners or taking the time to earn the trust of the tremendous citizens of the Republic of Korea, US Space Four Corps will advance the alliance to preserve peace and stability in the Indo-Pacific. And there's no other leader I'd rather have taking command than Lieutenant Colonel McCallion. Bootleg, I can speak from experience that it's not easy standing up a new component but your team makes it look easy. Your space expertise is unparalleled in our service. Moreover, your steadfast leadership over five years of living and working in the Republic of Korea make you my clear number one choice to lead this new field command. Your seat at the table in this theater will pay huge dividends for all war fighters across the Indo-Pacific. And there is no more critical region to global prosperity. The dynamism here, let in no small part by our Korean allies, can shape the world for generations to come. With China as the pacing threat, the Indo-Paccon may AOR is our top priority and activating this command underscores our continued commitment to a free and open Indo-Pacific. General the camera, I'm a huge fan of your command philosophy. The guardians here understand your intent and in a few moments they will have a commander that is among the very best our service has to offer. Kachi Kokchida, U.S. Space Force Corps, SEPRESUGA. Thank you, General Mastelir. The first organizational change you're about to witness is the activation of U.S. Space Forces Korea as Lieutenant Colonel McCullian and Master Sergeant Hill on furrow of the field component flag. May I draw your attention to the screen and guide you through its features. Platinum represents the men and women of the Korean Theater of Operations, Space Service Component Command, who faithfully carry out the Space Force mission. The Draco Constellation from Greek mythology, a circumpolar constellation never settling on the Korean Peninsula, symbolizes the Guardian Dragon and pays homage to past space luminaires and leaders that laid the foundation for United States Space Forces Korea. The delta and tail represent the unit's consistent satellite overwatch and strike counter-strike capabilities reliant upon the space domain, while the boundary line represents the Korean demilitarized zone. The black field symbolizes the infinity of space, representing that there are no limits to what guardians can achieve. Ladies and gentlemen, I present you the flag of United States Space Forces Korea. By the order of the Secretary of Defense, United States Space Forces Korea is hereby activated, effective 14 December 2022. It is my privilege to introduce the Commander, United Nations Command, Combined Forces Command, and United States Forces Korea, General Paul Akamra. U.S. Navy veteran, aeronautical engineer and science fiction writer, whom you may know as the author of the novel Starship Troopers, One's Road. Liberty is never unalienable. It must be redeemed regularly with the blood of patriots or it always vanishes. Of all the so-called natural human rights that have ever been invented, liberty is the least likely to be cheap and it is never free of cost. In other words, the freedoms enjoyed by those living in democracies today are only possible due to the risk taken and sacrifices made of those in the armed forces. And the newest armed force created to protect liberty is U.S. Space Forces Korea, which we're here today to celebrate. Good afternoon, I'm Yash Mnika. Excellencies, Ambassador, General and Flag Officers, distinguished guests, it's a privilege to join you as we celebrate this historic event. I appreciate the band and the crew who put this event together. Well done. Bravo Zulu, honor guard, you look sharp as ever. Please join me in a round of applause. Space is a vital domain of national security. For the last 60 years, space capabilities have become essential to the way of modern military conducts operations. Investments in space capabilities have increased in the effectiveness of operation in every other domain. The U.S. military is faster, better connected, more informed, precise and lethal because of space. The establishment of the U.S. Space Force in 2019 has helped ensure the United States is positive to deter aggression and outpace potential adversaries in the face of changing threats in the space environment and growing threats elsewhere. Specifically, the activation here today of U.S. Space Force Korea, the subcomponent of U.S. Space Force's Indo-Pacific, enhances our ability to defend the homelands and ensure peace and security on the Korean Peninsula and in Northeast Asia. It also clearly demonstrates in our actions the ironclad U.S. commitment to our alliance. The new command is a powerful addition to our combined joint fight tonight force. I can think of no better place for the U.S. to stand up a new space force than Korea. The Republic of Korea is a close ally and we can fight alongside in a true technological battle. Together, we are unstoppable. Fortunately, an outstanding leader has been chosen to lead the U.S. Space Force Korea. Lieutenant Colonel Joshua Bootleg, is the right leader at the right place and at the right time. He's punching well above his weight class as the only service component commander in the Department of Defense and in U.S. Forces Korea. No pressure there, Bootleg. Bootleg has been in space operations his entire career. He's a core space battle management operator with a background in space electronic warfare and SATCOM, orbital warfare and command and control. My advice is if some people give you a hard time, not just because of your relatively junior rank, but because the Space Force logo looks a lot like the Starface logo or Star Trek. You can inform them that your logo has been in use by U.S. space organizations as far back as 1961. Star Trek, meanwhile, debuted in 1966. To you, your wife, Mandy, son, Egan and daughter, Kira. Welcome to the team. Around the world today, we see many challenges to international peace and security. Norms of behavior and international law are challenged by our adversaries in space just as they are here on Earth. Many nations have advanced their space capabilities and are relatively looking for ways to deny access to this critical domain. Russia and China have developed anti-satellite capabilities and other nations such as North Korea and Iran are developing assets designed to negate American advantages. Nevertheless, the Force has better posture than our adversaries to deter aggression, defend the Republic of Korea, protect the United States interests and have called upon defeat any adversary in any domain. This is as true today as it was or is in the past. Today, the guardians of the U.S. Space Force ensure our forces are allies and the world never experienced a day without support from space. They serve across the globe working 24-7 to design, acquire, feel, test, operate and defend the critical space systems the nation and the world rely upon. Because of U.S. Space Forces Korea, the alliance is better able to execute multi-domain operations in the Green Theater of Operations and to fight and win the most dangerous distance the last 100 meters of land, air and now space. Congratulations, Boolay, the U.S. Space Force Korea, USFK's newest service component. Even though we know U.S. Space Force Korea will not be fighting Star Wars style battles in space if that time ever does come. Guardians will surely be on the front lines on the front lines where they are always above and make no mistake, we would win. We're always ready to fight and when we fight, we win. Thank you again for joining us today for your unwavering commitment to our mission. God bless our great nations, fight tonight, kachikapchida and separate support. Thank you, General McCullian. We will now commence with the assumption of command. Will General McCullian, Brigadier General Mastalier and Lieutenant Colonel McCullian please come forward. The assumption of command ceremony has been a part of military history dating back to the 18th century. During that time, organizational flags were created with color arrangements and symbols. You need to a particular unit. To this flag, the soldiers would dedicate their loyalty and trust. When an assumption of command was to take place, the flag was passed the incoming commander to indicate a change in leadership. This gesture was accomplished in front of the unit so all could witness their new commander assuming this position. This symbolic tradition has survived throughout generations of military history and today it will serve as the key element of this military ceremony. Lieutenant Colonel McCullian has been entrusted to assume command of United States Space Forces Korea effective 14 December, 2022. In keeping with tradition, the flag is entrusted to the command senior enlisted leader, Master Sergeant Hill, symbolically expressing the special trust and responsibility afforded to the command's enlisted members. Thank you, General Le Camera, Brigadier General Master Lear, Lieutenant Colonel McCullian and Master Sergeant Hill. Ladies and gentlemen, it is now my privilege to present the first commander United States Space Forces Korea, Lieutenant Colonel Joshua Luleg McCullian. I'm young, I should make a good afternoon. I want to take a moment to thank our distinguished guests and senior leaders, Ambassador Goldberg, General Ahn, Sergeant Major Love, Chief Dyer, fellow component commanders and leaders. I'm honored to stand before you today as a commander in U.S. Space Forces Korea. To General Saltzman and General Massalier, I'm humbled by your trust and the trust that you have placed in myself and my team as we pioneer the future of space operations within Korea. General Le Camera, thank you for embracing our guardians. We will absolutely rise to the challenge and advance your objective in the theater. Lieutenant General Cloyce, thank you for your mentorship, your guidance, our two services share deep ties, and we look forward to continuing that relationship. I'd be remiss if I didn't take the opportunity to thank my wife, my family, to my parents. Thank you for instilling with me the work ethic and integrity to stand and lead here today. To my extended family and friends for keeping me grounded, to my mentors for shaping me, and finally, my wife, Mandy, my son, Egan, and my daughter, Kira. Without your support and sacrifice, I wouldn't be able to stand here today. If you haven't noticed, our team's a little bit young. It's because we are. What we lack up in age will make up in vigor. Protected by our bulletproof mustaches, we're better qualified in leading space integration across the Canadian Peninsula than anyone else in these United States space forces. Just as Robin Olds paved the way to modernize the U.S. Air Force, Air Warfare, our team will strive to elevate space operations on the Korean Peninsula. Our U.S. rocked alliance was forged more than 70 years ago as we stood shoulder to shoulder in war. With the world around us evolving, so too must we. Today marks the next milestone in our ironclad commitment to strengthen the alliance. Expanding regional threats exposes the significance of our joint and coalition partnerships to foster a free and open space domain underpinned by a rules-based order. Just 48 miles north exists an existential threat that we must be prepared to deter, defend, and if required, defeat. The U.S. Space Forces Korea, as the newest component, must be prepared with our guardians to uphold the fight to night readiness, a way of life that was coined on this peninsula 70 years ago. Our space combat capabilities will help deter adversary aggression, enhance the warfighter lethality across the air, land, sea, cyber, and space domains, raising us to new heights in our ability to defend our forces and defeat the enemy. To my fellow guardians, I challenge you today, be bold, be confident, and uphold the guardian ideal. General Latamra, in your words, we've got a mountain to move. Let's get to work. Kamsahamnida, step up to your ground. Thank you, Lieutenant Colonel McCullian, and congratulations. Ladies and gentlemen, in keeping with military tradition, please rise and join in singing the United States Space Force song and remain standing for the departure of the official party. Thank you for attending today's historic event. We invite you to join us for a small reception in the back of the hangar in congratulating Lieutenant Colonel McCullian and his new command.


He's kind of, huh, fucked. So he thinks, what's the MAC address? Well, what he does? He cries out, who is <IP_ADDRESS>? And he does that very loud. We call this a broadcast. So host B is a little bit pissed off about this crying around, but sends back his MAC address so they can communicate, which then looks like this. So, what can we do? We can be faster or just more shetty. We stress the point that really we are host B and the other one is lying. And you would believe me, right? So, looks like this. He cries around. Etyker hears this as well. So here's the non-answer. Here the Etyker appears, who? And he answers, I'm this host. And, well, what I did, he can lie to both parties as well. So, then it ends up going through his system. Great. This is a short list of tools. There are lots of tools to do this stuff. We did one for Linux and for Windows. The THC group, another German group, wrote the parasite. Itacap is pretty nice because it has a graphical user interface. So, for all the less educated people here, that's pretty easy. The classic is Hunt, which is very good but sometimes strange to handle. And, yeah, there are scores of others. Another thing, local redirection. What do I mean by local redirection? Most people just overlook this. By modifying your own system, you can just modify the way. Okay.  I'm blocking him here on rather one. Well, okay. End of game. No, not really. Etyker called MAP, let's say, victims address here. If this guy is forwarding to the IP address of router one just by setting a fixed up entry. If router one is somehow using MAC addresses for filtering, like, let's say it's a switching router or something, that would pass. Another way, and that's the recommended way, just modify, yeah, that's the MAC address thing, just modify your routing table and use router two. You could even use router two if it had no connection to host B. Why? Because router two would know how to send it to router one and router one would probably accept it. So routers. Okay, we saw we can do nice things with them, but how do you find them? They're passive and active ways. Basically, listen for all the multicast and broadcast stuff or just discovery protocols like CDP. Running around the network, you just map the routers. But, well, this is not very effective because most modern routing protocols don't include the actual information in the broadcast packets. So what can we do? We can do active discovery. We can query routing processes. We call this AS scanning because it's autonomous system scanning. We can send out router solicitations. I really hate this word. Which means we just try around and look for a router. We do, I was fingerprinting, or even more interesting, protocol scans. We just scan the IP protocol. Let's say it supports IGRP. That's a good hint. It might be a router. Or we just do port scans. If it is an order model or just a strange model and it has, let's say, the report open, well, we find it this way. This is an example from our ASS, our autonomous system scanner. The upper four lines, that's passive stuff. It sees IRDP broadcasting, router information, and it sees IGRP, two different autonomous systems. Notice that it includes the iOS version. Very interesting. The rest of it is by active scanning, the IGRP in this case, you see how much information you get out there. It's internal routes or external routes. You see the net itself, the net mask, the next top, various information, even what kind of link it was, and all the information for the routing protocol, like delay, hop count, reliability, and all that stuff. So, which shoots do we have? As already mentioned, we wrote an autonomous system scanner. Etheral is very good in decoding routing protocols. If you prefer to do their stuff by hand, just take this too. The next top can be used to discover central points in the network. That would be a good hint for a router or a server. You will find out. TCP dumps option to show data link addresses is very good, because if you see a packet going from A to B on the IP layer, and the destination address on the MAC layer doesn't match to the IP, well, that's the next top router. Nmap is pretty good for protocol scan. We wrote our own tool before we discovered that Nmap supports this. You basically go down all the IP protocols, and that's a negative scan, so you wait for ICMP protocol unreachable messages, and if they don't appear, this thing is probably running this protocol. And if you get a router by DHCP query, well, why not using it? ICMP router protocol discovery. Okay, I mixed that up. IRDP is mostly, when you enable this on routers, they broadcast periodic updates, and just tell everyone I'm a router, and I know these interfaces, and you can talk to me. IRDP can be requested. That's this router's solicitation stuff, and he will answer mostly. The announcing router, let's say you are the announcing router, is entered in the host routing table with less priority, means with a higher metric than the default router, so make sure the default router is not available. And the metric depends on the preference. Most systems just run with a low preference. If you use a high preference, you're the first guy. So how does it look like? It's pretty straightforward.  You send them out, make yourself known to host A, and make sure that this guy is temporary not available. You want to use it later because how are you going to pass the traffic to this cloud here? So very interesting is the fact if you have a router that runs dial on demand or something, it has to raise the line or just negotiate PPP or something. If this host here is Windows, he would think the router is not available and take the next one in his routing table, which is hopefully you. So again, here are the tools. I recommend this attack as an additional thing because you don't get the traffic right away. So if you do any kind of traffic interception or redirection, you can do this in the background just to make sure if something goes wrong with your primary attack, you still get the traffic. Hosts, as I said, Windows just really likes it. And does it all the time. And he just on boot up. On the other hand, Linux does not care at all. ICMP redirects. Most know these. They were introduced to make routing a little bit more effective. So when host A sends traffic to router one here and router one discovers shit, I forward this packet to the same segment to another router in the same IP network, which is called router two.  And he actually tells this host A. So host A happily adjusts his routing table and uses router two for disconnection. So how do we use that? That works vice versa. The packet is sent from host A to host B through router two. We see this traffic and we think, well, we know a better way. So we actually tell this host A, please use me as your next top. And it works. It even works across routers. If you send ICMP redirect message, let's say across the internet, that works as well. Why? Because the final router who will deliver this packet to the attacked host is actually the one who's probably getting all the traffic, so the host will believe you. Okay, one important thing here. There are a lot of redirect tools out there, but most systems require the first 64 bits of the original offending packet to be included. Why? It would be good to know which direction and which communication caused this problem. So, host reactions. Windows just loves ICMP redirects. And it just adds the thing to the host as a host route to its routing table. So, if you look at your routing table and you have about 500 host routes on your routing table, you should look out for ICMP. Linux host, it depends. You can set this here in this proc file system. But most distributions now accept these things. And it's a little bit evil because you don't see them in the routing table. You really have to go into the proc file system and find out which tools exist, okay? Because we're speaking about it, we coded one. And there's, from Yuri, another one, which is basically the original ICMP redirect tool. Works pretty good. So this is how it looks like on a Windows system. You might not read this, but you see the pattern. It's all host routing here. It's all 255. Okay, let's go routing. Let's make it interesting. IGRP, interior gateway routing protocol. Is this your idea? It has actually 65,535 possible autonomous systems. It's just to separate server routing processes from each other. It uses no authentication. Hello. And various data link information, like hop count, reliability, another word I really like. And bandwidth is used to calculate the metric. Well, hosts can actually listen to IGRP without saying anything. That's called a passive interface. So make sure your protocols scan the hosts. Maybe they accept your updates. Spoofed updates mostly have a better metric. Why? Because you can choose your link however you want and you can easily compete with the real-world stuff. But keep in mind that your sender network, whatever you select as your sender network, has to be enabled as a possible source for route updates. So how does it look like? We could introduce new routes for modifying existing one. We have this guy here, host B, and we have this nice server over here. And we have the three routers here talking IGRP. Our attacker got a connection to another router and he's just way off. Okay, so what does he do? First, he adds the IP address of the server to his interface as a secondary IP and enables IP forwarding. Guess why? Because in the next step, he's telling router 1 using router 3's IP address that <IP_ADDRESS> is definitely the best way to reach the server. So he just makes himself very interesting for the router. Now he tells R2 that R1 is definitely a better route to reach server than the original R3. So host B actually ends up logging into his fake server running there, submitting his password and other information you just want to have or just being curious. We don't do bad stuff, right? And he gets all the traffic. Great, he can even run a fake server on it that looks like the original one. Think about web applications. So you can get a lot of interesting information there. If for some reason Attica just wants to prevent the server talking to host B, he can do another thing. He can do routing loops. He just tells R3, well, the best way to reach your host B is definitely R1. And he tells R1 that the best way to host B is definitely R3. Then he sits back and enjoys the packets using up its TTL. Okay, this is some very old stuff. Routing information protocol version 1. Rip. Good, it's one of the oldest, but it's still in use because it's so simple. It uses broadcast and just runs on UDP port 520. It has no autonomous systems and other stuff. It even uses a fixed network size, at least in most implementations. And it really, really is easy to attack. There's the routing information protocol version 2. That actually includes Nextop information and Netmask into the routing updates. Still has no autonomous systems, but it often uses multicast instead of broadcast. And there is even a ClioTek authentication defined in RFC. But this is so strange that most people don't implement it or don't use it. Cisco actually supports MD5 for Rip. What a bright idea. But since they use a double authentication block, this is not by RFC. If you have anything that is not Cisco, you definitely don't want to run this. So what are the attacks? It's basically the same stuff you can do with Rip as you can do with ERP. Watch out for the network boundaries for the fixed Netmask stuff because if you send updates that don't make sense or you just use subnetting or supernetting, you're going to confuse the network. We don't want this. The multicast stuff, Rip v2, maybe forwarded across segments. Why I love multicast is, for example, if you run a checkpoint on an AIX system, it will forward multicast whatever the checkpoint setup says. So that's why I really like it. There is a thing called Split Horizon with Poisoned Revers, which actually prevents routing loops from happening, not really. You have to have at least one router that knows that there is a routing loop and it is communicating back this to the other routers. If you have just two routers talking Rip, you can do routing loops. So which toots exist? R-Probe and S-Rip from Humble are probably the first Rip attack toots I've seen, which doesn't mean anything. You can use the Nemesis Rip or anything else you can think of based on the libnet because they support Rip. And you can use ASS to scan this. The problem at the moment is the Rip senders I know do not support the clearchecks authentication, which is defined in a RFC, so you might see that. OSPF, open shortest path first. That's a very interesting routing protocol. Unfortunately, it's very complex. Basically, one thing it does is sending out link state advertisements through the area. Area means you can define routing areas in OSPF and every router in the area knows the status of every routing information you might have. So these halo packets are used to tell each other, hey, I'm here and I speak OSPF, but they don't include much information. So there's another thing that makes OSPF more complicated to attack because it's basically one of the most secure routing protocols currently in use. Defined in a RFC are clearchecks and MD5 authentication. But one thing to remember is if you don't understand OSPF, the administrator might not as well. So there's the hard to understand factor. Let's say most people run OSPF in one area because it's simple. So you might have luck and just have a flawed design. So how do we attack this? There are several possible attack ways. I choose one that's more interesting because it's a combination of layer 2 and layer 3 attacks. We spoke about that the attacker is able to decide forwarding and is able to modify the IP traffic. So what are we going to do? Since forged LSAs are often contested by the router, they have a mechanism called fightback.  So the best thing seems to be you just intercept the communication between router 1 and router 2. When router 1 sends out a packet OSPF-wise, you just modify the information and pass it on to router 2 and he will happily distribute it across the area. Thank you very much. BGP4, border gateway protocol, it's an exterior gateway protocol which means it's used in vans. And it's mentioned only here because it's important. Can anyone think of why BGP is important? It runs the internet. So that makes it interesting. It relies on TCP for communication between the routers. It has a port, 179. You probably know how to find this. And more interesting is there is IBGP and EBGP. It means there is an interior BGP and an exterior BGP. Interior BGP actually means how do the routers in one area communicate with each other? Yeah, but to find each other and to do TCP, they have to have a route. Okay, so mostly they use IGP, any kind of IGP, or static routes, which is, okay, if you have a BGP4 network and you use static routes, you're just an interesting administrator. So the best way is often to attack the IGP. Yeah, because you can just prevent the routers from speaking to each other. You could intercept the TCP communication in any way, or you can use BGP communities. That's an interesting feature. It's not fully researched yet how to do evil stuff with that, but it is invented to introduce, let's say, properties to routers you don't own. So let's say UUNet uses communities. You can actually tell the router, okay, whatever I tell you, it's just for the UUNet internal network, or whatever you send me, I don't want to have this and that information. Another one, bad updates. Well, it's not too hard to send bad updates in BGP, but the internet service providers, especially the small ones, are very good in sending updates like dear internet. I actually know where the 10 network is around the world. So the background providers got used to that and filtered them pretty good. It's mostly used for internal BGP networks because you don't want all the hosts in the internet trying to reach the 10 network over your system. Okay, after so much dry routing, here's a fun thing. How to stand by a router protocol? Another Cisco idea, it's used to have a virtual or standby IP address and another virtual-like MAC address bound to an active router.  Is the call for me? No? Okay.  Okay, the active router is sending out hello packets all the time. And if he stops sending out hello packets, the other routers are going to fight for the highest priority and to actually get the active state. Interesting is its first multicast. I already mentioned I love multicast. And the authentication is done in clear text. Maximum eight characters. Thank you. So it basically looks like this. The blue thing down here is this virtual IP address or standby IP address. So everyone is talking over router one. When you tell router one that R2 is actually a new router just appeared in the network and has a better priority, this is not as it is designed, but it works. R2 actually gets the standby IP address. So everyone is using R2. What's that for? Well, you could actually tell both of them that you have the highest priority. Can you wait with a question or is it... Is that a question if there is a key? No, it just uses clear text authentication, but Cisco already went the way to say, okay, HSRP is kind of interesting and if you really want to use it, use IPsec. Okay, tell this at .coms. Was this a question? Okay. So, yeah, you're telling both of them you're the best router to do the job and at the end you have about 20 risk processors just for routing. So you get the virtual IP address and the traffic. And what's the best about it? It's 100% transparent to the hosts. The IP address didn't change. The MAC address didn't change. It looks like it is before. Just there is this guy here deciding which traffic is passing. Well, so, we had a lot of routing and some fun. After so much routing, let's hop into tunnels. Generic routing and encapsulation GRE is basically used to transport protocol A over protocol B in a backpack. It's not even limited to IP. So, normally you use IPv4 and IPv4 but to connect six bone islands you use IPv6 and IPv4. You can transport IPX over IPv4 or vice versa, whatever. The best authentication you can get with GRE is a 32-bit tunnel key. Okay. There are sequence numbers to prevent evil people like... Any evil people here know. To do anything with the routing protocol but you can actually forget it because it's not defined how they work. They're far away from being as good as TCP sequence numbers and they're so bad implemented that it just works if you don't use them. Another very important thing is GRE supports source routing. Has anyone an idea what you can do with that? So, once upon a time, this is a very common situation at least in Europe. The company has an HQ on the right side with this cute little server and has server branch offices. We have one on the left side here. So, they were used to using list lines or something because they just hate central authorities. They just decided, okay, we go for RFC 1918 IP addresses. Most of you know these as private IP addresses. So then, they decided, okay, I'm going to save money because we have the internet. We can pass over traffic to the internet. And then someone said, hello, your stuff is not routable. Okay, the carrier, being a good guy and knows how to do business, offers a VPN solution. He just says, okay, we build a GRE tunnel between these two, this one, and we just encapsulate all the traffic into the tunnel and it's passed from the branch office into the tunnel, gone out in HQ. And for security, because we want you to use security, it has to be secure, we just say everything that's not out of the tunnel is dropped directly here on the interface. And whatever comes into this router and the destination is not a local network, we just put it into the tunnel. So, that makes it perfectly secure. Our poor guy editor has its own router and actually a routable IP address. Anyone noticing the IP address? No? Okay. So, he's facing the following situation. He has a network, a target network, let's say this branch office here, which uses not routable IP address and uses a filter here to prevent traffic from coming in and on top of this uses GRE. So, he's lost, isn't he? Not at all. He just sets up another system. In this case, a concept we call an attack router. Then he decides, okay, this system is my default gateway and he passes traffic to this attack router. Notice the destination of his traffic is actually the host here. It's not routable anyway, but he's sending this to the attack router. The attack router encapsulates the packet into GRE and the outer packet is addressed to the branch office router, which is getting the traffic, seeing that the source address is the HQ, guess why? He finds out it's GRE, decapsulates it, puts it back on a routing process, finds out he can reach the host over the internal interface and just pass it to the host. So, what does the host do? The host actually answers the packet, whatever that was, and sends it back to his default gateway, the branch office router, who will, according to his routing rules, encapsulate it into GRE and send it back to the HQ. So the HQ router is used for internet access as well, so he knows a way uplink to his provider. So he figures out, well, this packet is reachable over the internet, so I just send it out and see our attacker just gets the answer, which means it looks a little bit strange, but you're actually talking to a system with a private IP address across the internet, behind the GRE tunnel, behind filters, and you have fun. So, since this is so funny, we'll actually put some more work into this. There's, at the moment, no support for the source routing, which makes it so interesting. A thing to do, probably, is you can apply the same attack to IPX encapsulation, X25, any takers in the banking industry here? You can encapsulate IPv4 and IPv4, or even attack IPv6, Six Bone Islands. So what about taking over IPv6 host before it's even on the internet? So, quick ramp up, what tools do we have? Yeah, it's not that interesting, but for reference, you can download all the stuff here and the slides on this URL, or actually look at my shirt. Summary. There are a lot of ways to alter... Sorry, this one. You can actually grab me and I can tell you how to write that. Okay, I'll put it back on later. Yeah, summary. You saw there are many ways to alter traffic paths. This was not a complete... Don't go away, there's a demonstration going on later. Okay. This was by far not complete. There are a lot of routing protocols, even undocumented ones. It has still a lot of heck where you, especially the BGP4 attacks. Most routing protocols, as we saw, are very interesting protected. Means nearly nothing. And unencrypted tunneling protocols are really a high risk and really demonstrate the fact that these so-called private IP addresses do not protect at all. So, yeah, thank you to these people, especially to these red people here shipping me here. And a special thank you to you, not falling asleep and listening to me here and being at DEF CON. And whoever is interested, I'm going to show the GRE attack now live. So, I know I'm probably over my time, but this is really a fun part to do. Unfortunately, my laptop has a blank screen now for me. Just relax. What do we have here? On the upper left side, we have a tenant session to assist the router who is actually representing this branch office thing. I tried to show you in the presentation. On the right side, top right side, we have a TCP dump. I'm looking for ICMP because we are doing simple pings here. On the lower left side, we have this already mentioned Viper thing, which is our study in attack routing technologies. Now there. On the right side, you see the local routing table. So, what are we going to do? I'm trying to write blind here. Actually, it doesn't work, right?  Actually, it works pretty slow. So, we ping this one, and here on the right top side, we see the Cisco answers actually with administrative prohibited packages saying bad guy, bad guy. Don't send traffic to me, please. Okay. Now we have a new routing table. The new routing table says, please use this attic router, which is this poor little laptop here, to do the GRE encapsulation. We'll show the configuration file later, but it basically just includes tunnel source and tunnel destination for this virtual interface here. So, now, we actually do the same ping. What do we see? I know it's very hard to read in a crowd here, but on the right side, you see actually this interface, this virtual interface has the MAC address, double A's or double A's, and you actually see that the echo request is sent to this virtual interface and then passed on. We don't see the pass on here because someone thought it's a good idea. We show something with sniffing and they gave us a switch. Thank you. Okay, just to illustrate that you can do some more stuff with that, I'm trying to write something here. Does this make sense? Does it? Okay. We actually don't want it to do NSLOOKUPs. Where's the shit? On the left side, we see the tunneling packets, which is just the verbose output. On the right side, we see it's actually scanning through this virtual IP router and go figure we bound this IP address on a loopback of the Cisco, which is by now pretty clear. That was it. Thank you.


In the last segment we took a look at an energy balance for pipe flow and what we came up with was we came to a conclusion that we weren't sure how to be able to calculate the bulk temperature as the fluid was flowing through the pipe, be it a constant surface boundary condition or a constant heat flux. So what we're going to do now, we're going to explore in a little more detail the bulk temperature with position and what we'll do, we'll derive a differential equation that enables us to explore the two different boundary conditions, either constant surface temperature or constant heat flux. So let's begin by pulling a couple of equations from our energy balance segment that we just looked at. So this is one of the equations that we came up with from our energy balance. And if we consider a section of pipe and what we're going to do, let's consider a little differential element in the middle of that pipe, which is what we did when we came up with perform the energy balance. dx is the length, so x is going in this direction as we go along the length of the pipe. And we have some form of heat transfer taking place. We'll quantify that as qs, double prime, giving us watts per square meter. Now what we can write is knowing this is one equation that we have, but we can also do a balance based on the amount of convective heat transfer taking place. So what it'll do, let me go to the next slide. So dq convection can also be expressed as our surface heat flux multiplied by p, the perimeter of the pipe times dx, that would be the area. And then that can be equated to our m dot cp dt, the bulk or the mean temperature change with distance. And so what we're going to do here, we're going to play with this equation beginning by rearranging. So what I've done here is I've taken these two and I've done a little bit of rearranging. And we end up with a differential equation that gives us an expression for how the bulk or mean temperature is changing as a function of position within the pipe. What we're going to do, we're going to take this and let's take a look again at Fourier's law or the way that we quantify convective heat transfer in the pipe. And so we have this expression here for qs double prime. And that would be the heat transfer, the convective heat transfer, due to convection on the wall. There we have our wall temperature and then the bulk temperature.  So let's go through that process. So this provides us with a differential equation where we have the slope or the gradient of the bulk temperature with position on the left. And on the right we have an expression that contains the bulk or the mean temperature. And also embedded is the convective heat transfer coefficient. Now if we're outside of the entry region of the pipe, so we're in the region that we call fully developed flow, the convective heat transfer coefficient in pipe flow does not change with position. So that is a constant outside of the entry region. And these other two terms, if we can assume that the specific heat is remaining a constant, mass flux is going to be a constant. And if it's a constant area duct or pipe, perimeter does not change. And so those are constants as well. But that gives us a relationship. And what we are going to do, we're going to explore this equation. And we're going to explore the equation to examine how tm varies with x. And we'll do it with two boundary conditions. One is a constant temperature boundary condition. The other one is constant heat flux. And so that's what we're going to be doing in the next couple of segments is looking at this equation and seeing what it can tell us about the bulk temperature for those two different boundary conditions.


Hey, YouTube, this is a video right up for the challenge Polyglot from CodeFest CTF 2018. Challenge from here essentially gives us some C source code and apparently a compiler or GCC weird thing, but we actually didn't end up even using or needing at all to solve the challenge. Props to, I think it was Sauronint on the Discord server in our Discord team and the team that we played with to tackle this. He just like stumbled upon it and totally solved it and super duper cool. So props to you showcasing it because of you. We actually have, I went ahead and downloaded the source code here, so let's take a look at it. And what we particularly notice in the source code is that it has a lot of peculiar white space in it, like random spaces and tab characters. So this is a pretty good indicator of something like white space, where maybe trying to hide a message or information out of spaces and tabs, which could actually be interpreted as binary ones and zeros. So that's what we tried to go with. And let's actually create a script to go ahead and work with that. I'll call this just a get flag dot pie. Pretty confident that we'll get the flag with this.  Let's go ahead and actually open up the secret file, secret dot C, and try and handle it and work with it. I should go ahead and do this with like a contact manager because people are hating on me for that, but whatever. Let's just actually get the new lines off of it in our read lines because we want to read through this line by line for X and this thing and then H dot close. Okay, so for line in C, we can print that line. And then we have the source code written here with the spaces and tabs and all that included. Let's go ahead and try and scrape out just those characters. Let's go ahead and import regular expressions. I did this XE all the way to the very end without the new line character because read lines will create a list or an array for us, but will include the new line characters at the very end. I don't particularly want them. So let's run now all read off find all with our line, but let's get any rostering for one thing. Let's get any multiple of white space characters. So see what we've got here. Find all, sorry, run this. And now you can see, okay, sometimes we are getting a actual occurrence where we match multiple space characters or a tab character, et cetera. So we can say num or whatever, whatever temporary variable that we want. So if we actually got a result, so if it's not an empty array, we can say this, it can go ahead and equal a joined position of num. So we'll print these all out. And let's go ahead and replace them so we can change all the space characters to something like a one or a tab character with a zero. Let's go ahead and print all these out. So now we have potential binary characters and values here. Let's switch these around. We're going to end up having a 50-50% chance. But okay, some of these may be in the range of zero to 255 or actually in the ASCII range. So we consider these to be binary with int2. Now we get the numbers that were visible. Some of them may be in the range zero to 255. So they may be ASCII characters, like I said. Let's go ahead and add these in the character form. Now let's just say num can equal that value. And if num is actually in the range from 255, let's add it to a flag variable that we'll have right up here. Flag can equal an empty array. And then if it is in that range, we will add a flag append, chr, so the character of that num. And then at the very end, we can print out our flag all put together just like that. So we can see we have something interesting in here like the flag. However, it is reversed. So let's go ahead and reverse our string here. And now let's go ahead and scrape the flag out with just regular expressions. Find all. We'll use a new string with the flag format code fest CTF anything inside the curly braces. And we'll get our results. And we have our flag just like that code faced CTF spaces and tabs are get flag script all combined for us. So a handy dandy thing to just carve through getting those white space characters out. And that's that. That is the polyglot challenge. Let's go ahead and mark this as complete. If we wanted to run that get flag script, save a static copy of it. You can submit that for points handy dandy. All right, special shout out to those people that support me on Patreon. Thank you guys so much. You guys are fantastic. $1 a month or more on Patreon will give you a special shout out just like this. $5 or more on Patreon will give you early access to all the videos I create before I release them on YouTube. If you did like this video, please do like comment and subscribe. Join our discord server link in the description. It's a cool community of CTF players, programmers and hackers. We will be playing ICTF knock CTF and all the upcoming capital flag games as they come forth. It's a cool, cool thing just to have like 700 people on the team and the server and it's a whoever can play. It's open to everyone. We're all about getting people to learn and get better. So please do join. Thanks for watching guys. Again, it'd be awesome. I'd love to see you on Patreon. I'd love to see you in the next video. You're the best.


The idea of cloud is changing from a set of remote services somewhere out there in the cloud to an operating model that supports workloads on-prem, across clouds and increasingly at the near and far edge. Moreover, workloads are evolving from a predominance of general purpose systems to increasingly data-intensive applications. Developers are a new breed of innovators and Kubernetes is a linchpin of creating new cloud-native workloads that are in the cloud, but also modernizing existing application portfolios to connect them to cloud-native apps. Hello, we want to welcome back to HPE Discover 2021, theCUBE's ongoing coverage. This is Dave Vellante and with me are Scott Buchanan as the Vice President of Marketing at VMware and Toby Weiss, who's the Vice President of Global Hybrid Cloud Practice at HPE. Gents, welcome to theCUBE, great to see you. Thanks for coming on. Thank you, Dave, great to be here. I agree, thanks for having us. So you heard my little narrative up front and so let's get into it. I want to start with some of the key trends that you guys see in the marketplace and maybe Scott, you could kick us off from VMware's perspective. What are you seeing that's really driving IT today? Well, Dave, you started with a conversation around cloud, right? And you can't really have a conversation around cloud without also talking about applications. And so much of the interaction that we're having with customers these days is about how we bring apps and clouds together and modernize across those two dimensions at the same time. And that's a pretty complex discussion to have and it's a complex journey to navigate. And so we're here to talk to customers and to work with HPE to help our customers across those two dimensions. Great, so Toby, I mean, it's always been about applications as Scott said, but the application, the nature of applications is changing, how we develop applications. I mentioned data intensive applications, we're injecting AI into virtually everything, the apps, the process, the people even. From the perspective of really a company that supports applications with infrastructure, what are you seeing in the marketplace? What can you add to that discussion? Yes, yeah, great point, Dave. With applications becoming more central, think about what that means and has meant for developer communities and developers becoming more important customers for IT. We have to make it easier for these developers to speed their innovations to market, right? The business demands, newer and faster capabilities of these applications. So our job in the infrastructure and what's called the platform layer is to help. We need to build these kinds of platforms that allow developers to innovate more quickly. So we talked earlier about sort of modernizing apps. I mean, it seems to me that the starting point there is you want to containerize. And obviously Kubernetes is the key there. But so okay, so if that's the starting point, where's the journey? What does that look like? Maybe Scott, you could chime in there. Sure, a couple of quick thoughts there, Dave and Toby to build on. First is, if you look at the cloud native computing foundation landscape today, which you can do at landscape.cncf.io, holy smokes, is that a jungle? So a lot of organizations need a guide through that CNCF landscape. They need a partner that they can trust to show them the way through that landscape. And then secondly, there needs to be ways to make these technologies easier to adopt and to use in practice. Kubernetes being sort of the ultimate example of that. And so we've been hard at work to try and make it easy and natural to make Kubernetes part of one's existing infrastructure. So that building with and working with containers can be done on the same platform that you're using for virtual machines. So let's talk a little bit about cloud and how you guys are thinking about cloud. I remember Toby that back in VMworld 2010, it was the very first VMworld for theCUBE. All we talked about was cloud, but it was private cloud was really what we were talking about, which at the time largely meant the virtualized data center. It was kind of before the software defined data center. And today we're still talking about cloud, but it's hybrid cloud. That's kind of the narrative that I set up upfront. The data center, it's become, for the most part, software defined. And so how do you see this changing the IT operating model? I think it's a great question. And look, today you will see us talk a lot about this notion of cloud everywhere. So less differentiation about private and public and more about the experience of cloud, right? Public cloud brought great innovations. And what better than to bring those innovations to on-premise workloads that we've chosen to operate and work there? So as we think about cloud more as an experience we want for our developers and our end users and our IT organizations, we begin to think about how can we replicate that experience in an on-premise environment? And so part of that is having the technologies that enable you to do that. The other part is we've most of us have evolved our IT organization operating models to operate our cloud infrastructures off-premises. Well, now expanding that more holistically across our organization. So we don't have two operating models, but a single operating model that bridges both and brings the ability of both of those together to get the most benefit as we really become to integrate and become truly hybrid in our organization. So I think the operating model is critical and the kinds of experiences we deliver to the users of that IT and infrastructure and operating model is critical as well. Are you guys are both, you know, basically in the infrastructure business and so Scott, maybe we could start with you. There's a lot of changes that we're talking about here in IT, generally the data centers specifically, especially big changes in workloads, you know, with a lot more data intensive apps, AI being injected into everything, Kubernetes making things more facile. And in many ways, it simplifies things, but it also puts stress in the system because you got to protect this. They're no longer stateless apps, right? They're stateful and you got to protect them. And so they've got to be compliant. Now you've got the edge coming in. So my question is, what does infrastructure have to do to keep pace with all this application innovation? One of the conversations that we are having increasingly with our customers is, you know, how can they embrace a DevSecOps mindset in their organization and adopt some of these more modern patterns and practices and make sure that security is embedded in the life cycle of the container? And so, you know, I think that this is part of the answer is equipping the operator through infrastructure to set guardrails in place so that the development organization can work with freedom inside of those guardrails. They can draw on catalogs of curated container images, catalogs of APIs, start from templates. Those are the building blocks that allow developers to work faster and that allow an operator to ensure the integrity and compliance of the containers and the applications of the organization's building. Yeah, so that's kind of, when I hear Scott talk about that Toby, I think infrastructure is code, designing, you know, security and governance in, right, we always, we always said that was an afterthought. We kind of bolted it on. Second, the security team had to take care of that. This is always the same thing with backup, right? Oh, we got an app. It's all ready to go. How do we back it up? And so that's changing that whole notion of infrastructure as code. Well, I want to talk about Green Lake in a minute, but before we get there, I wonder if you could talk about how HPE thinks about VMware and how you guys are partnering. I'm specifically interested in where each of you sees the value that you bring to the table for your joint customers. Yeah, great question. You know, and starting to think about history like you did 2010 being the start of a theCUBE journey. I remember in 2003 when we first partnered with VMware in the very first data center consolidations and we built practices around this. It's been quite a long partnership with VMware. And I'm excited to see this partnership evolve today, especially into this cloud native space and direction. It's critical. We need, you know, customers have choices and we need great partners like VMware to help satisfy the many different use cases and choices that our customers have. So while we bring, you know, good depth when it comes to building these infrastructures that become highly automated and managed in some cases and consumable, like on a consumption basis and automated, like we help clients automate their CI-CD pipeline. We depend on technologies and partners like VMware to make these outcomes real for our customers. Yeah, I think there's a way to connect a couple of the points that we've been talking about today. Got some data from us, state of Kubernetes study that we just ran. And this is 350 IT decision makers who said that they're running Kubernetes on-premise. 55% of respondents are running Kubernetes on-premise today. And so, you know, VMware and HPE get to work together to bring Kubernetes to those enterprises. 96% of them said that they're having a challenge selecting the right Kubernetes distributions. There's 60 of them in that CNCF landscape and the number one criteria that they're gonna use to choose the right distribution to set them on a path forward is that it's easy to deploy and to operate and to maintain in production. And so I think that this is where VMware and HPE get to come together to help try and keep things as simple as possible for customers as they navigate a fairly complex world. That's interesting, Scott. So who are those on-prem users of containers and Kubernetes? Is it the head of, you know, is the application team at an insurance company who's kind of maintaining the claims app? Is it guys building new cloud native apps to help companies get digital first? Who are those? What's the persona look like? In our conversations, you know, this is the infrastructure and operations team scene that there's energy around Kubernetes and maybe there's some use in test and development in parts of the organization. And by centralizing ownership of that Kubernetes footprint, they can ensure that it's compliant, that policy is set properly to your point earlier that it's, you know, meets the security standards for the organization. And so it's increasingly that SRE or Site Reliability Engineer or Platform Operator who's taking ownership of that Kubernetes footprint for the organization to ensure that consistency of management and experience for the development teams across the larger org. Toby, is that what you're seeing too? Yeah, we see quite a few, we engage with quite a few developer teams in business leads that have ambitions to speed their application development processes.  And often, as I stated at the intro, they might be coming off of a much older deployment maybe from 2015 where there were an early adopter of a container platform methodology and wanting to get to some newer platform or they may be in charge of getting a mobile banking application and its features to market much more quickly. So, and often when we get a quote maybe from a client it might come from, you know, the VP of a business unit, but often as we engage, it's, you know, the developers are pretty much our customers and their developer leaders and teams. So, you're running into container technical debt already. You're seeing that out there, it sounds like, legacy container deployments. Yeah, I think so. It takes some expertise to come off those older, you know, the first instantiations of these container platforms where pretty much open source and yeah, you want to bring it to something that's more modern and has the kinds of features, enterprise grade features you might need. So, is it not so problematic for customers? Because as I said before, a lot of those apps were sort of disposable and stateless and now they're saying, hey, we can actually use Kubernetes to build, you know, mission critical apps. And so that's when they sort of decide to pivot to a new modern platform or is there a more complex migration involved? What do you see? Okay, I'll give my hot take here Toby and then ask you for yours. But I guess, I feel like the conversations that I'm involved in with customers is, you know, always begins with their broader application portfolio. These enterprises have hundreds, thousands of applications and job one is to figure out how to categorize them into those which need to be re-hosted or re-platformed or refactored or reimagined entirely. And so, you know, they're looking for help figuring out how to categorize those applications and ultimately, you know, how to attack each category of application. Some should be re-platformed on environments that make best use of Kubernetes. Some need to be refactored, some need to be reimagined. And so they are again, looking for that expert guide to show them the way. Right, and when we engage in those early discussions, kind of, we call it right mix advisory, you know, you're trying to take a full broad scope as you said, Scott, down to a few and, you know, determine kind of the first movers, if you will.  Again, like mobile applications for banking, I think are a good example because, you know, they have an ambition. I mean, the leader of that kind of application may very well think that is the mission critical application for the company, right? But of course, finance, they have a different point of view. So, you know, that application to them is the center of their business, getting, you know, their customer access to the core banking features that they have. And, you know, they want to zero in on the kind of ecosystem it takes and the speed at which they can push new features through. So we see both as well, you know, the broader scope application weaning down to the few discovery application and then, of course, a very focused effort to help a particular business unit speed development on their mobile app, for example.  I mean, there's always an ongoing, but Y2K was one of those, the big move to SaaS was another one, obviously, Cloud.  We all know the stats, right?  You know, there's always a promise we can change that. It reminds me of the, every year I would go to the Boston Marathon, it was this guy who would run and he had a hat on with an extension and it was a can of Budweiser way out there and he couldn't reach it. And so he would run, it was almost the same thing here, is they never get there because they have so many projects coming online in the project portfolio and then the CIO's got to maintain those in the application heads. And so it's this ongoing thing, but you do see spikes in rationalization initiatives and it feels like with this push to modernization and digitization, maybe the pandemic accelerated that too. Is that a reasonable premise? Are you seeing sort of a milestone or a marker in terms of an increased effort around rationalization and modernization today because of Kubernetes? Yeah, definitely. I think that there are a couple of, Kubernetes is a catalyzing technology and the challenges of the pandemic or a catalyzing moment, right? And I feel like organizations have seen over the past 18 months now, that those enterprises that have a way to get innovation, to market, to customers faster, not once a quarter, but many times a day are the ones that are separating themselves in competitive marketplaces and ultimately delivering superior customer experiences. So it comes back to some of the ideas, you know, full circle that Toby started with around delivering a superior developer experience. So that, you know, those developers can get code to production and into the hands of customers on a much more rapid basis. Like that's the outcome that enterprises really care about at the end of the day and Kubernetes is, you know, part of the way to get there. But it's the outcome that's key. Great, thank you. Dave, in one of our practices, Dave, there was, you know, that's been our bread and butter for so many years. This, you know, this broad-based discovery narrowing down to a strategy and a plan for migrating and moving certain workloads. We see a slight twist today in that clients and organizations want to move quicker to the apps they know that, you know, they want to focus on. They want to prove it through the broad-based discovery and kind of a strategic analysis, but they want to get quicker right away to the workloads they are quite sure that need refactoring or leverage the benefit of a modern developer environment. Yeah, and they don't want to be messing around with provisioning LUNs and servers and all that stuff. They want that to be simplified. So I'm going to end on GreenLake. And I want to understand how you guys are thinking about GreenLake in terms of your partnership and how you're working together. You know, maybe Toby, you could sort of give us the update from your perspective. Can't have a conversation with HPE today without talking about GreenLake. So give us the Kool-Aid injection. And then I'm really interested in how VMware thinks about, you know, participating in that initiative. Absolutely. And thank you for helping us out here. You know, I see more and more of our engagements with clients that ask for and want to sign a GreenLake-based contract. And that is one very important foundational element. And there's so much more. Because remember, we talked about the cloud experience in cloud everywhere. And GreenLake brings us an opportunity to bring dimensions to that, especially on the consumption model. Because that's an important element. If we begin adding partners such as VMware to this equation, especially for clients that have huge investments in VMware, there's an opportunity here to really bring a lot of value with this cloud experience to our customers through this partnership. All right, Scott, we're going to give you the last word. What's your take on this? Hey, listen, hard for me to add much to what Toby said. He nailed it. You see a ton of energy in this space. I think we've covered a bunch of key topics today. There are ongoing conversations with our customers in GreenLake is a way to take that conversation to the next level. Guys, really appreciate you coming on. Give us your perspectives on Kubernetes. And thank you, Scott, for that data. 55% of IT decision makers out of 350 said they're doing on-prem Kubernetes. That's a new stat. I wouldn't have expected it to be that high, but I guess I'm not surprised. It's the range the developers want the latest and greatest. So guys, thanks so much for sharing your knowledge and appreciate you coming on theCUBE. Thank you, Dave. Thanks, Dave. And thank you for watching theCUBE's ongoing coverage of HPE's Discover 2021, the virtual version. We'll be right back.


All right, so we're mostly all engineers here, right? Let's take a look at some numbers first. Europeans living with diabetes. There's about one in 11 European. I don't want to make any politics, but Europeans, just general Europe, I don't. I've been told it's a touchy subject. So Europeans living with diabetes, one out of 11. Europeans living with asthma, one out of 12. And I'm pretty sure if I ask this room here, there's maybe 200 people. So if I ask who has asthma, like there's probably, we see a few hands. So that's fine. You know, that kind of goes close to the statistics there. Arthritis. Europeans living with arthritis. There's one out of five that will eventually, usually starts at an older age. I'm starting to feel it in the mornings. It's kind of a guess I'm getting at that age. So about one in five and people living with mental illness. Also one in five. That's a little bit more of a, you know, I'd say a shocking statistic. So mental illness is one of the most prevalent chronic health conditions, but we just don't talk about it.  Nobody would have raised their hand, right? We don't talk about it. This big taboo. So today I'm here to talk about my own experience. I'll talk more specifically about burnout, which is one of the many mental illness that it covers under that statistic. Mental health covers a lot of different things. It covers things like depressions, schizophrenia, OCD, and so on. But I'll focus on burnout. I'll focus on my own story. Now here's one thing I'm not a mental health professional. I'm only here to talk about my own experience. So your own experience may differ. And if you have any question, I mean, don't rely on me. Just go ask a medical professional. It's very important. The reason why I do this talk, though, is to kind of help to break that stigma around mental health, especially mental health in the workplace. Like I said, we don't like to talk about it. So by doing talks like this, I'm hoping that it will help to open up conversations. Now I'm not used to talk about myself.  I'm much more comfortable talking about containers than I am talking about myself. But we'll see how this goes. Let's give it a try. So a little bit about me. Hi, everyone. My name is Joel Lord. I am French-Canadian. That's the little charming little accent you might have recognized there. I currently live in Ottawa in Canada. And I do some talks. I work as a developer advocate for Red Hat. So I spend a lot of time traveling, going to conferences, just like this one. If you ever want to get in touch with me, Twitter is always the best way. So that's Joel with 200 scores, Lord. Whenever I have Twitter notifications, I get really, really excited. And yes, that's a gift of me, because why not? Burnout is a heavy topic for the first talk in the morning. So I thought I'd lighten up a little bit. All right. So burnout can be kind of hard to define. It's not like having a flu.  It takes some time. It spreads along a long period of time. And it's a little bit like whenever you go to the movie theater and they slowly fade out the lights, and you only realize that the lights are out once they're actually out. But it's really hard to say at what point they started fading those lights. A little bit like that image you might not have noticed, but it was a very nice image at the beginning and slowly faded into this post-apocalyptic image. So it's a slow fade, and it's really hard to see when it actually started or not. But it's easy to see the end result, though. So for me, at one point, I woke up one morning and everything was hard at this point. I had to get out of bed and drag my body out of bed. It was so hard. I had no motivation. I had to take a shower. I said, ugh, really? And I got into the shower that morning, and I started crying. I had no clue what was going on, but I was just crying. And it was this really weird feeling, because I was completely losing control of all my emotion. I didn't know what was going on. Now, my wife, who had been incredibly supportive during that period of time, she'd been telling me for a while that something was wrong. But I'm strong. I'm not going to go see a doctor. I don't need that. I'm just a little tired. But when that happened that morning, I kind of realized that something was wrong, and maybe it was time for me to actually face it. So what is burnout, exactly? So burnout is a state of emotional, mental, and physical exhaustion caused by excessive and prolonged stress, and it manifests itself in ways including anxiety, loss of motivation, confidence, and even degradation of physical health. In my case, so it kind of mimics a lot of symptoms of depression, so it's kind of hard to diagnose when you're just looking at the symptoms. In my case, I had a complete lack of motivation. Like, I didn't want to do anything, never, ever. And a lot of anxiety. I started having so much anxiety, and I started getting physically sick as well. I had a flu, but it lasted over a month. I mean, that's not normal. When your regular common flu lasts over a month, you should probably talk to a doctor. I had so much heartburns, like so much stress. I actually bought tums at Costco. I said, no, there's no problem. I'll just take more tums. Nothing's wrong. I should have put an image of that dog. It's fine. And I was having so much trouble controlling my emotion. That was actually one of the hardest part. Everything was kind of like this rollercoaster of negative emotion. I went through anger, and then sadness, and then aggressive, and then oh, super anxious, all of a sudden, and then impatient, and then discouraged. And it's a really weird feeling when you can't even control your own emotions. I felt like I was almost losing part of my mind, you know? And the lack of motivation, I've touched about it, but it was, I didn't want to do anything. Like really, my friends would call me to go and have a drink, and I'd find an excuse. I just didn't have any energy to do anything. So most of my weekend, we're just spent in bed, you know, watching Netflix. Someone once told me that a willpower or motivation is a little bit like a bucket of water that you have in the morning.  So that's why they usually say, you know, all the things that you don't really like doing, like going through your emails and bill, you should do early in the morning, when you still have some energy and some willpower and some more water in your bucket. And as the day progresses, you should do things that are more fun, that don't require as much energy to get started, right? So you'll do coding towards the end of the day, because then you can really get into it and thought more fun. And some days you wake up, and the bucket might be a little bit smaller. Maybe you have young kids, and they kept you awake all night, or maybe you're traveling from Canada, and you're jet lagged, and maybe there was a social last night, then you have a beer too many, or maybe it's a mix of all of that, but sometimes the bucket is a little bit smaller. But ultimately it's up to you every day to manage how you're gonna spend that water.  You wake up in the morning, and already you start thinking about all the horrible things that are gonna happen today. And already it's hard to get out of bed, because there's all that energy that just drained out.  And by the time you get to the office, I mean there's absolutely no energy left to do anything else. So that's kind of how I felt when I was at the worst part of my burnout. So where does it come from? So burnout can be prevalent in organizations that promote hero culture, and where employees maintain a strong sense of duty, or feel they have no alternative in the employment market. Now that last part might not be as true. I think we live in an industry where we have a lot of chances to move, although sometimes we feel like we're kind of stuck in our job. And there's also that hero culture that we have in the tech industry. Jessica kind of touched on it yesterday, where everybody has to be the best, and somehow everybody has to be a nastier everybody else. So the tech industry tends to have that hero culture. High number of working hours is often seen as desirable as well. And when you're done with your work, what should we do? Well, we should go back home and work on a blog post based on whatever we learned today, or work on that open source project because we need that for our portfolio, and there's always something else that we need to do. At that time I was doing about 70 hours a week for my job, and it never seemed enough. I could never accomplish what I needed to do in my days, and so I started working at night, because that makes a lot more sense, because I didn't have any interruptions at night. So, and no, don't do that, please. Not very healthy. And it's also that startup culture where everything moves at 2,000 miles per hour. In my case, there was also that false sense of responsibility. I was working as a manager back then, and my manager would ask me to put together some project or put up some new processes for different things, but I didn't have any power to change anything in the organization.  So this type of thing kind of leads to a toxic work environment, which is definitely not very good. So a lot of people think that or associate burnout with just being tired, that it will go away with a little bit of sleep. Well, once you reach the state of burnout, usually it's a little bit too late. I mean, you will need to recover at some point, but it's not just getting a good night of sleep that'll fix everything. So occupational burnout is considered a real disease. It's recognized by the ICD as its own ICD code recognized by the World Health Organization. And it can be diagnosed with the Mastak Burnout Inventory, which is a series of questions that you rate from zero to six. The questions themselves depend on your profession and a few criteria. Now, when you go see a doctor and because you feel like something's going wrong, be careful on how you will answer those questions. Be honest. So one other question, and I remember this clearly, the doctor asked me, what was the question there? Are you having difficulties getting along with your colleagues? So I thought a little bit, and I was like, well, today I got into a fight with only two of my colleagues. The yelling lasted about 10 minutes each time. So that's 20 minutes out of 24 hours. So rarely, no. So try to be honest.  If you're unsure whether you should actually see a professional or a mental health professional, the Mayo Clinic released a quick survey that you can do to decide whether you should or not see a doctor. So those are some of the questions. Have you become cynical or critical at work? Do you drag yourself to work and have trouble getting started once you arrive? I mean, outside of Mondays, right? Have you become irritable or impatient with coworkers, customers, or clients? I have so many stories. Do you like the energy to be consistently productive? Have your sleep habits or appetite change so it can have physical effects as well? Are you troubled by unexplained headaches, back aches, or physical complaints? If you answered yes to any of those questions, you might be experiencing job burnout. Be sure to consult your doctor or a mental health provider. However, some of those symptoms can also indicate certain health conditions such as thyroid disorder or depression. So if you feel like something is wrong and you're saying yes to at least one of those questions, well, maybe it's time to actually think about it and go talk to your doctor. All right, so what should you do if you feel like you're going through burnout? So first of all, go and see your doctor. I said it many times and it's very, very important. Actually, do so. I think a lot of, especially people my age, but we feel like we shouldn't talk about that stuff and we should be strong, right? And we shouldn't see a doctor and it's very important that you actually do so. And they might recommend or prescribe some medication. If you have any doubts, ask questions. Just ask them questions. They are health professionals. That's what they do. Ask them questions. Is that something that might be addictive? Is that a medication that I'll eventually be able to get off of? So think about it, what it is that worries you and just ask those questions. They'll probably also recommend therapy. You should do it, definitely. One thing about therapy though is and that people don't say enough is shop your therapist. It's really hard and if you wanna get some real benefits out of a therapy, you need to be with someone that you trust and you might have to shop a therapist to actually find one. All right, but what else can you do, apart from seeing a doctor? Well, do a little bit of introspection. That's always a good start. Think about what it is that put you in this position. Where is it that you get that pressure from? And don't just go and blame others. Think about it, really. And maybe it's just you that can't say no to anything and maybe that's something that you actually need to work yourself. Or maybe there are some external factors that are putting you in this situation. So do a little bit of introspection and really, really think about what it is that is causing you this stress. Take a break. Of course, not all employers will give you a full month off, but sometimes you might have personal days off, days that you can take without any questions asked. So by all means, take them. You should take them. Maybe take a long weekend.  I like to do canoe camping with my wife and it's in the middle of the forest, of the Canadian forest. And it's exactly like you would imagine. And there's no cellular data, no cellular connection whatsoever. And it's great because I can't answer any emails or anything. So I kind of need that. But, you know, do something like that and try to disconnect a little bit from work and other worries that you might have. Oh, do less. That's obvious, right? Just do a little bit less. But by that I mean, try to offload some of the work that maybe you don't have to do. Here's an interesting story. When I started dating my wife, you know, I wanted to impress her and I would do the cooking. And like every night I'd do dinner, prepare dinner. And she wanted to be like a traditional, you know, wife and she did all the dishes after the meals and we did that for a while until we actually talked about it.  I absolutely hate it. And she loves it. So it turns out that I was able to do a little bit less by delegating that to her. Now, I know what you're thinking. I do the dishes now, right? So, but that's something that I actually enjoy doing. I find that it's a really relaxing way to end a meal, to actually just clean up everything and everything is nice back to the original state. I think it's, I don't know. I love doing the dishes. And it's, but it was an interesting discussion and when we realized that, never since, I've never cooked bitter anymore and she never does the dishes. So I'm doing a lot less because it's not as much effort for me. So, you know, try to see if there's anything that you can offload in a work environment. Maybe, maybe you can ask someone else to take on that code review that you don't want to do that today. You know what? Ask that junior in the team to actually do that code review from that senior developer because that will offload some of the work for you and it will probably be a very beneficial experience for the other two parties involved. Say no. This one is there mostly as a reminder for myself. If conference organizers ask you to fill in for a talk, you know, maybe say no. Like, no, that's not true. But you don't need to be a superhero. I mean, you don't need to justify whenever you don't want to take on a task. And you know what? Saying no sometimes actually increases the values of your yeses. So say no from time to time, it's very, very important. All right, save your fucks.  So you kind of need to save some. If you choose your fights, you won't be able to save the world by yourself. So you won't be able to please everyone. Just pick some fights, some that you can win ideally, and bring them to an end. So you have a limited number of fucks that you can give in a day, so you know, use them wisely. Ask for help. That's a really, really hard one for me. But reach out to people. Reach out to people that you trust. Reach out to talk to your spouse, your significant other. Reach out to your friends.  Just tell them that you're going through a rough batch. No, don't need to go through the details, but you never know what's gonna come out of that. Sometimes you might find someone's unexpected support. Do some exercise. All right.  It's good for you. It does endorphins and things in your brain. I'm not the exercise type. Who am I kidding? One thing that was very important for me, though, is find something that you like to do. Find a hobby. Try to find something that is completely different from your work and that you actually enjoy doing. For me, I started brewing some beer. They usually say, yeah, don't drink too much when you're going through depression or burnout, but yeah, I only brewed the beer. So I started doing that. And whenever I have, in this picture of me, my cousin and my brother and we're our brewing partners, we brew big batches of 20 gallon beers every few weeks. And those are the only morning where I actually set up my alarm at six in the morning. I get there as quickly as I can. I get very, very excited about that. And if you're not familiar with brewing beer, essentially the process is you get there, you drink a lot of beer, and you watch some water boil during a few hours. That's pretty much all you do. But whenever I have brew days, I sleep so well at night. Might be the beer drinking. But it's also the fact that I spent a full day doing something that I really enjoyed with people that I really love and I don't have to worry about anything during those days. So find something that you actually like doing and pursue that. All right, so if you see people going or if you wanna help people that might be going through burnout, so what can you do to help? Well, there's a few things that you can do as an employer for starters. First of all, you might wanna enable remote work. There's a lot of controversy around that, but remote work can definitely help people if they need to take an appointment with a health professional during the day, they might bless you. They might not have to justify that or they might not have to feel like they have to justify that. Offer some personal time off is very important. Let your employees take some days off without asking for a justification or asking for a doctor's note. Just let them take some days off. Have an employee assistance program. Those are very, very important. If you're not familiar with an employee assistance program, it's basically just a phone number where you can call and get all kind of help, whether it's from mental health or even sometimes legal stuff. Now, if you have an employee assistance program, be really careful on how you promote it. I used to work at a place where it was a very nice open floor office, right? And right in the middle of this floor, there was this big column and there was a poster and the phone number for the employee assistance program was right there in the middle of the room. Now, for some reason, go figure. I never saw anyone actually go up to that post and take a phone number and note and give them a call afterwards. No, you wanna put that in a place where people will have a little bit of privacy. Good places are maybe in the bathroom stalls so people can actually just take the number and note and then they'll be able to call later. So be careful on how you promote it. Make sure that it's available and that people don't have to be shy of taking that number as well. Train people to the mental health first aid kit. So there's a program called mental health first aid, kind of like the regular first aid programs, but aimed towards mental health so you can take a look at that. And there's the mental health in tech guidelines for mental wellness in the workplace, which was published by OSMI. I'll come back to OSMI later, but you might wanna take a look at this. As a manager, all managers here, lead by example, that is so important. Don't send emails at two in the morning. I don't care if you think they don't have to answer at until seven in the morning, just don't send them. Schedule them for eight or nine in the morning. If you don't need an answer now, don't send the email now. End of story. If you send emails at two in the morning, your employees will feel like they actually have to answer back at this time. Take some days off, take your vacation, especially in tech, where we have this unlimited vacation policy.  And talk about mental health in your workplace. Now as a colleague, there's a few things that you can do as well. Mainly language matters. Be careful on how you address different situations. Don't call people crazy and things like that, which might not be very good. There's a great guide that was published by Bell Canada. They have a program every year, which is called Let's Talk. The link is there, as you can see. They'll all be, I'll publish everything on Twitter afterwards.  Listen to people, don't jump to conclusions. Things like, ah, you'll get over it or just relax. Usually don't help. You know, ask instead or say, I'm sorry, you're not feeling well. Ask how you can help. And break the silence. Talk about mental health in the workplace. That's very important. So the talk is called Post Burnout Thoughts. So what now? So I've been through that. And I found out that it wasn't only negative. I mean, sure, when you're in the worst part of your burnout and you feel like everything is dark and it's not a good place to be in. But you know what? Things will get better. It'll only get better from there the moment you start talking about and the moment you reach out for help. So it's what helped me to find this job. That was a very good output for me. So I took that time to do some introspection. I thought about what is it that I like doing? What is it that I actually enjoy in my work? And what is it that I don't like? So everything management out the window and a lot of things like mentoring and coaching people are things that I like to do. So that's why I do what I do right now. And it brought me so much closer to my friends and family. I got to recognize who was my real friends. They were there to help me out whenever I needed. A lot of times without me asking, they just knew I was going through a rough patch and they'd reach out to me and help in various different ways. So now I live a much better balanced life. So I think overall the output was very positive. Sure it wasn't a lot of fun when I went through it but now that I think of it and that I look at it it's the result is a lot more positive. So I'll leave you with this quote from Christopher Norring, a friend of mine which actually lives in London here. And he said something along the lines of if you don't get burned out by working for you you get it by working with for someone who doesn't appreciate your work. So make sure that the extra hours that you're putting in are for yourself. So if you want to write that blog post after you're done with your work sure go ahead but make sure that you do it for yourself. If you want to learn that new shiny framework that they've been talking about at the conference today sure but make sure that you actually do it for yourself and not because your employer expects you to learn about it next week. So I talk about this. I do a little bit of volunteer work for the open sourcing mental illness group. So you might want to take a look at their website. They have a lot of very good reference there. So I'll leave you with the final resources. So the OSMI website, Mental Health First Aid Kit Belkanada Let's Talk and everything will be published in one single link at the end. So with this, thank you very much.