It's been grueling. It's been tough. The grind has been real. It's been 12 weeks of facing some of the NFL's best teams. And now, the Titans finally have a chance to reset and prepare to finish strong. Dave McGinnis and Jim Wyatt are here to talk about everything. You don't want to miss this round table edition of Titans All Access as it starts now. We welcome you to Titans All Access. I'm Mike Keith joined by not just Amy Wells, but Titans Radio's Dave McGinnis and TennesseeTitans.com Senior writer, editor Jim Wyatt. Welcome to everyone. We're so glad to have you during the bye week for a special round table. Are you ready to kind of get this thing going, Amy? Oh, yeah. There's so much to talk about with the Tennessee Titans. And I think we have the best people in the business to really break it all down. All right. This segment of the program is sponsored by our friends at Duncan as we talk ball with our group. First question, Amy, you get the first crack. Most impressive part of the Titans offense through 12 games. I think it's what they've been able to do and how much they've been able to do with so many changes. The Tennessee Titans offense lost most of their starters. The big name people that we were talking about in training camp and in the off season. Julio Jones, AJ Brown, Derek Henry, just to name a few in this Titans offense has continued to rise. Continue to see performances by players that we never thought would be main stars on this Titans team. People that we thought would be supporting cast. And they've stepped into these roles in a big way. We've seen so many different starters on the football field. And I think that's been very impressive the way that they've been able to rise and overcome the adversity. Jim White, did she take yours? No, but I'm going to piggyback off of hers. And I think it's the ability to run the football no matter who's running back. And we all saw what Derek Henry did at the start of the season. 937 yards through late game. But just this past week, you see Dantro Hilliard, Dante Foreman both go for over 100 yards. We've seen some different pieces as Amy said in the offensive line. And then the other guys step out with other guys going down with the injuries. And they've continued to be around the ball number five in the league in rushing offense. So I'm impressed by that. All right. Most impressive part of the defense through 12 games. Coach Mack, you lead off this segment. I think it's been the ability to get a Foreman rush when we have all our guys. That changed this defense from a defense that was really scrambling to try to figure out how to get off of the field to a defense that was really getting people on the ground. And that's extremely important. The ability to rush with four people when we had our good people healthy and then the people that added in. Now, once you start losing some of that and we saw it again this last week, it's hard when you only have a limited number of those people across the front. But when we can get those people back, that ability to rush with four and cover with seven, that's what's impressed me. I think it's that they already have 29 sacks to this point in the season for reference. They only had 19 in 2020. So the amount of pressure they're able to get, guys like Harold Landry with 10 sacks already this year, Jeffrey Simmons with seven and a half already this year. There are guys who are consistently getting to opposing teams quarterbacks. And I think that's a huge improvement and a very welcome surprise. Most impressive part of the defense to me is the reemergence of Kevin Byrd. What a year this guy's had so far. 64 tackles, five interceptions. He's caused a fumble. He's got a quarterback sack. He scored the first two touchdowns of his career. Jim, the Titans needed him to be a big play guy again in this defense. And the mayor of Murphysburg is doing it. Yeah, and he vowed to do it. I mean, that's one thing I remember about the end of last season. He took it so hard on himself when like kind of a season in the Zoom call, vowed to be better, vowed to work more, vowed to be a better player. He's done exactly that. I mean, he has been a consistent performer for this team. His leadership has been great. Okay, so those have been the most impressive parts of the offense and defense through 12 games. When we return, the biggest surprises so far as our roundtable discussion during the buy continues on Titans All Access. We welcome you back to the Bet MGM Studio, our roundtable discussion during the Titans buy. Jim Wyatt, Dave McGinnis, Amy Wells, and me, Mike Keith. And Jim Wyatt is the leadoff here as we talk about the biggest surprise for the Titans offense through 12 games. Well, I have to say it. I don't mean to go negative here. I guess the turnovers by Ryan Tannehill. And this is the only time I'll go negative here. Seven interceptions in 16 games last year. Only six and 10 stars the previous year. This is not all on Ryan Tannehill. Obviously, we know the injury situations with this team. AJ Brown being out, who little Jones being out, Mark Johnson being out, young guys stepping in. But it's been uncharacteristic some of the mistakes that he has made. And obviously, if his team is going to get its footing back in the second half of season, that's going to have to be better. Coach Mack? It's being able to switch from a singular running back to a running back by committee. That's not as easy as it sounds. And it's not as easy as it sounds for this reason. When you're game planning and you understand your singular back and what it can do, and you've got two and a half years of knowing what this guy likes and what he does best and how to formulate a game plan individually against the opponents with what he likes to do. Now, with him gone, you're trying to find out not only what you can do structurally, but you need to find out what the strengths are of the core of running backs now that you're trying to run the ball with. Being able to make that switch, that's hard to do in the middle of the season and especially when you're in a playoff push. That's impressed me. My biggest surprise about the offense is David Quessenberry. Starting 12 games at right tackle playing. Well, we know he's a great story. We know he had a four-year battle with cancer. We know he battled his way off the practice squad. We know he started the end of last year at left tackle, which was certainly not his natural position. But at the age of 31, he is the titan. Starting right tackle has played all 12 games and has done a fantastic job overall. For me, David Quessenberry, I think he'd be the starter in the offseason. He has emerged as the most solid, consistent piece at least to this point for the titans. All right. Biggest surprise about the titans defense through 12 games? Coach Dave McGinnis. The biggest surprise to me was that improvement in third down defense. And that goes with the last segment of what I said about a four man rush. Anytime you can win first and second down and you can take all of the angst of your defense on third down, it's a huge plus. But to do that, you have to be able to win first and second down. And to win first and second down, you have to be able to deploy yourselves to put the offense in conflict first and second down. We've done that. And then our third down defense has gotten markedly better. Now, it goes off of what I said in the first segment about being able to rush with four. We need to be able to get back to that because all three of those elements cascade off of that. For me, it's that the titans defense has become one of the strengths of this titans team. In 2020, that was not the case. And you could tell it really bugged not only the guys on defense, but Mike Vrable. And he really put a concerted effort into changing this defense and really getting them back on track. And they've become a powerhouse. They are the game records for this titans team. They're making plays. They're generating points. They're doing all the things that you need a defense to do to play complementary football and win football games. So I think that that has been surprising not only that they're better and they have improved but that they make such an impact every single Sunday. When we come back, the player on offense or defense who has impressed you most through the first 12 games, this will be interesting. Stay with us for more Titans All Access. This segment of the Titans Roundtable on Titans All Access is presented by Nissan, the official auto partner of the Tennessee Titans. Amy Wells is going to lead it off here as we talk about the player on offense who has impressed you the most through the first 12 games. It's Nick Westbrook Akina. He is someone who, even throughout training camp, we thought would be a solid supporting cast player. That's kind of what I expected out of him anyway. To see the way that he has stepped up when his number is called, he's got 25 catches for 297 yards and three touchdowns so far this season. He showed up in a big way and at times when the team really needs someone to make a play. So for him to step beyond being a supporting cast member and to be a star player on this offense, very impressive by him. I'm going to Derek Henry just because he's still on this football team even though he's on injured reserve. The start he got off to, he was at an MVP pace. He was going to lead this league in rushing again. Hopefully we get him back in a Titans uniform again this season, but I just think the start that he got this team off to is really going to put this team in a position to win the AFC South. Ben Jones. Ben Jones has been a solidifying factor in the middle of that offensive line. In previous segments, we've talked about the offensive line juggling people. Cuisinbury is another nice story, but Ben Jones is the rock of that offensive line. He has had different people on the left and the right side of him and also on the edges. The center in the National Football League is so important, especially if you're running check with me if you're identifying fronts, all of those things. The other thing is, is he's been available and availability on this football team has been at a premium this year. That's been extremely important. My vote goes for Ben Jones because I can say this and I think Ben Jones won't mind that I say this. He's not completely healthy. He has been playing through some things and has been playing very well. Ben Jones is my guy. Dave McGinnis, the defensive player who has impressed you the most during the first 12. Jeffrey Simmons. Jeffrey Simmons has been everything that we thought and more.  Well, Jeffrey Simmons did the same thing.  Jeffrey Simmons to me by far is the dude I'm looking at and we need him to continue that for the rest of the season. I'm actually looking at the defense and obviously Kevin Byrd is a player that would be easy to mention in this. I'm going to go Christian Fulton and here's why. Vastly improved corner. And I know he's missed some time with injury, but I think he's a key player down the stretch because in the early part of the year, he looked like a shut down corner. His improvement from year one to year two, vast, excited to see more of him coming up during the rest of the year. I think he could be a centerpiece for this defense going forward. Coach, it's hard to find shut down corners. Well, a shut down corner, I mean, it's easy to say it's extremely difficult to do. I coached for 31 years in this league. I had one, Anis Williams, and he's a Hall of Famer. And so that's usually what those guys are. And Christian Fulton, I agree with you a lot on this, Mike. You can tell the difference when we first got to training camp and just watched him come out on the field. He looked different physically. So he put in that type of work and then he was really having a nice, nice year. And like a lot of our other good players, unfortunately they've been missed some time, but I agree with you 100% on that. Good to have him back. Great to have him back. Players to watch offensively and defensively over the final five weeks of the regular season and hopefully into the post-season, that's what we'll talk about next on this Roundtable edition of Titans All Access. Welcome back to the Bet MGM Studio, Titans All Access Roundtable Edition during the buy. Jim Wyatt, Dave McGinnis, Amy Wells, and me, Mike Keith. Player to watch on offense during the final five weeks of the regular season and hopefully into the post-season. Jim Wyatt, you take the lead here. I'm going back to Ryan Tannehill.  He's a good quarterback. I think we all know that. He's proven that during the course of his career. I think once he starts getting some of his pieces back, A.J. Brown, Julio Jones, some guys start to get healthy. I think Ryan Tannehill is going to take off. He's going to play like a Ryan Tannehill that we've come to know here over the last couple of years. So I'm looking for a strong finish from Ryan Tannehill. He's a guy that we're obviously all going to be watching. I have Ryan Tannehill as well because of his mindset and his mentality going into these last five games. But because Jim Wyatt took mine, I'm also going to say Dante Forman. Because I think that as he continues to get comfortable in this system, we've seen him already have a 100-yard-plus rushing game. I think that as he continues to get comfortable, learn more about this offensive line, get more in sync with Ryan Tannehill, all those things that happen in training camp and OTAs and those times that he just didn't have with this Titans team. As he gets in the groove a little bit more, I think we're going to see more and more of those big plays and hopefully we're going to see him break away for even more of those big yardage moments that we all love so much. Talking about big yardage, I'm going to give you a two-headed monster. We need A.J. Brown, Julio Jones, to show up the last part of this season. That's going to be a major, major for this football team because what we're lacking right now offensively and it's through nobody's fault is the explosive plays. You start talking about Forman in the run game. We talked about the run game starting to coalesce a little bit and come together. Ryan Tannehill is going to be on track. To be on track though, we need more explosive plays down the field. Those two guys can provide it for us. That's who I'm looking for. All right. Player on defense to watch in the final five games. Dave McGinnis, you go first. I'm going to go with Denico Autry and Denico Autry for this reason. People have a lot of film on us right now and they're going to zero in on Jeffrey Simmons and they're going to find ways to get hats on whoever's playing at the second level. Denico Autry is a major disruptor and major disruptors are usually what you can count on towards the end of the season and he has been very, very consistent. Jim said it. He doesn't have the numbers but Denico Autry to me, he's a linchpin for this going forward. I say Jeffrey Simmons because I don't think all that tape that's floating around on Jeffrey Simmons matters all that much. I think that even though teams know what to expect from him and know what he's able to do, the man is a monster. He's a machine and with teams knowing what he's capable of, he's still able to have seven and a half sacks and 34 tackles so far this season and he's taken these last two losses that the Titans have had a little personal. He's mad. He expects more from himself. He expects more from the defense and he said it all the way back in the beginning of the season. I'm the leader of this group of guys and I expect us to play at a certain standard. It seems to me he hasn't seen that standard in the last two weeks and he's got a whole week to just sit and get angry about it and stew. I think that Jeffrey Simmons is going to be a beast in these last five weeks. I'm going back to Kristen Fulton because as you mentioned earlier, I mean he's shown so much improvement during the course of the season. Had that little spell there where he was out. Kind of got himself back in a position where he's feeling good again. I think now the next step for him is to make some of these game-changing plays like Kevin Byers have done at safety. So I look for Fulton to have a couple of picks, make some plays and it's going to help change games here down the stretch. Mine is safety of Monty Hooker and the reason is Monty Hooker had four picks last year and early in the season, before he got dinged up, Monty Hooker was all over the place. He's kind of been working his way back in. I think there are big plays in number 37 the rest of the way to sort of piggyback off of what Kevin Byer has been able to do. As you look for guys who can take that step forward down the stretch, to me, Monty Hooker at safety is a guy who can certainly do that. When we come back, keys to the rest of the season, each person has one. We'll see what they are when Titan's All Access continues. The keys segment on Titan's All Access is presented by our friends at VisitMyrtleBeach.com. It's pretty self-explanatory. Visit Myrtle Beach. Go to this website and find all the great deals, the places to stay, the things to do and the place we ought to be this weekend for the buy week. VisitMyrtleBeach.com So it's time now for each member of our panel, Jim White, Coach Dave McGinnis, and Amy Wells to provide a key to the rest of the season. Coach Dave McGinnis of Titan's Radio, you are first. You've got to get back into the plus turnover margin world. You've got to get back to that. It's incredibly important. It's been an issue. We know it's been an issue and we're always honest. This team, you've got to get takeaways. We defensively have to take the ball away from our opponent. We need to get back to the plus turnover margin world. This team has got to get healthy and it's got to stay healthy. We're in the position we're in now coming in with the two-game losing streak in the buy week because of all these injuries, 17 guys on the injured reserve. I think that's the key of the season. This team's the only way to go as far as injuries and the health of the key players can take them. The Titans need to score in the red zone. They're doing a good job of moving the ball and getting into that scoring area. They are not scoring once they get there. And that's something that really is impacting this Titans team. Just having field goals isn't enough. You've got to score touchdowns. When you're in the position to score, you've got to take advantage of it. You've got to cut out the middle mistakes. You know, the penalties in the New England game early in the contest on special teams were killers. For the Titans, get back to playing smarter.  Got it. But to win down the stretch, I think that's a big key for the Titans and certainly something they're capable of doing. The bottom line though, Dave McGinnis, is the season really starts now. The first 12 games, you're 8-4. You have a two-game lead in the division. Here you are. If you play well from here on out, it can be very special. To this point in the season, everybody is positioning. And the Titans have done enough early in the year to position themselves. Have they done enough to be able to sit in a position where they can't be caught? No. So this is a new season. It does start now to Jim's point about getting people back. That's going to be huge. But all of these points that we've brought up, believe me, Mike Vravel and his staff this week in the off date, that's what they're going over. And then they will very specifically go over, not only as a group with this football team, but individually. They will individually. And that's what you do after you individually go and you have nameless, rankless debriefings individually after the open date. During the open date, you do it and then you have to have honest, honest discussions with each individual player saying, here's what you have to do. Here's what you must do. And here's what you have to eliminate. That's going to go on this week. Yeah, Mike Vravel said it on his radio show, truth telling. We're going to spend some time with the truth, Jim. Yeah. And sometimes the truth hurts, but that's how you get better. And I think that's what this team will do, evaluate itself. Usually sometimes in the bi-week, you do some self-scouting. The bi-week comes late this year. You've got a bigger body of work to look over what's gone right, what's gone wrong. And you've got time to get it fixed. This team's in a good spot with five games left. Now, again, just need to get healthy, play better football. Make a run. Make a run. It's about that time. This is when the football starts to get exciting. This is when every game in the NFL really matters as a Titans fan. This is a great time to be watching football because there's a lot of games out in the world to watch. I mean, even on an open date, there's a lot of games that matter to Tennessee Titans fans. So there's lots of football to watch. And then the Titans have an opportunity to do something really cool and control their destiny a little bit. If you want to know what's going on with the Tennessee Titans, you need to go to TennesseeTitans.com and read every article by Jim Wyatt every single day. He generally has like nine or 10 a day. There's a lot of them. It's amazing. And if you want really interesting insight on the team, it's our all-new podcast, the Titans' Amy Coach Mack podcast with top guests, great analysis, and generally arguments between Amy and Coach Mack. We've had them offset, you know, during the course of the program. You can also follow us at the OTP, the official Titans podcast. We're out twice a week with Game Week programming for the rest of the season with that. Lots of ways to follow the Titans, including from here in the Bed MGM studio with Titans All Access. For Jim, Coach, and Amy, I'm Mike. Thanks for joining us, and we'll see you next time.


My friend and colleague, Sarah Stewart is our first speaker of the day. Sarah Stewart has been a midwife for many years and currently is the midwifery advisor and manager of the Australian College of Midwives Policy and Professional Practice Unit. Sarah's professional role has many varied elements from developing policy statements representing the ACM on national government and regulatory groups to responding to individual ACM members inquiries and concerns. Her volunteer roles include being company secretary to the Climate and Health Alliance and Sarah has recently completed an MBA and is a member of the Australian Institute of Company Directors. Her research current interests include how open access resources and methodologies can improve governance and management processes within health and healthcare organisations. Ten years ago, Sarah brought together a diverse group from around the world to develop the virtual International Day of the Midwife online conference to celebrate this very special day for midwives. Welcome, Sarah. Thank you very much, Jean. Can you make me a presenter then I can flick the slides through? Oh, that's brilliant. Thanks. And while we're here, can you just quickly confirm what time do you want me to finish? Is that quarter past? I think that is what it is in the program, but I'm not absolutely suit and Sarah, but that would be great if you could. All right. Well, this will be a quick... Sorry to be so vague. There will be a quick flick through. And if anyone has any questions for me once my session has finished, either pop them in the comment box or drop me an email, put my email in the comment box once I've finished speaking. Thank you very much, everybody, for joining us this morning. I cannot believe 10 years ago, when we started this, 10 years ago, I never had any idea that I'd be here talking to you all in 10 years' time. I thought that if I was lucky, this initiative would go one or two years. So to be here 10 years later, I'm just absolutely gobsmacked and absolutely thrilled to be here. So just first of all, I just want to make sure everybody can hear me. I haven't seen any comments to say otherwise. So thank you all very much for coming today. And I'd really like to welcome you all. Before I go any further, I'd like to acknowledge the custodians of the land on which I am personally am sitting in Canberra, ACT, Australia, that's the Nunnamal people. And I'd like to pay my respect to their elders past, present and future. And I'd like to acknowledge the elders of the lands in which we are all meeting today around the world and pay our respect to them. Thank you all very much for coming today. As I said, some of you have been on this journey with me for the last 10 years. Some of us, some of you may be joining for the very first time. I'm absolutely horrified to see there's a picture of me there sitting in a red dressing gown in my house in Dunedin in New Zealand, which is where I lived 10 years ago. And I'm still, I'm sat here now this morning wearing the same red dressing gown. So honestly, it is time I've got a new dressing gown. But we're looking back at the photos and the pictures that we've gathered over the last 10 years. It's amazing how some things have changed, but some things are very much the same. So for those of you who don't know about the conference, it was started with the idea. We started 10 years ago, actually, not with a full 24 hour conference, but it was a one session, one hour session on the 5th of May. And the idea had back in 2008 was that we would put on a series of presentations say once a month over the whole year. But after the first year, my very dear colleague, Deborah Davis, who's online, who's also in her pajamas this morning, we had a chat and thought maybe we'd be better off actually if we wanted to build this as an idea but having a conference on the as a 24 hour idea would be better than trying to spread it out over a whole year. It would allow us to concentrate our communications and so on and so forth. And of course, the most logical day to have a midwifery conference is the 5th of May. So that's where the idea of having a virtual conference on the 5th of May came about. And the idea of having it as a 24 hour event, actually, I have to say we nick that idea from a wonderful group of people working second life, Lorraine being one of them, they had already picked us to the post of this idea of a 24 hour conference. And so we thought we could do the same. And the idea of that was that we would be able to reach from a time zone perspective, everybody in the world, of course, reaching everybody in the world from a technology perspective or a language perspective is another story and one that we're still working on. So these pictures here, the picture up there in the top that was probably Ali and Nikki were probably our first one of our first speakers. And I'm very grateful to everyone, particularly in those early days when we were building up this ideas, a concept very grateful to people like Ali and Nikki for giving us their support. And the picture in the bottom right hand corner, a group of midwives getting involved or a few years ago now up in Queensland, I think, somewhere. And the image in the top right hand corner was a tweet from Merilee Penman, who's an occupational therapist. And I don't know if you can see the writing, but she, she with a group of her friends internationally was so impressed with this idea that they took on the similar event for occupational therapy. So this has been a very successful initiative, not just in midwifery, but also extended into other health professions. It's been very much an idea that we developed the idea. We wanted to reach out to as many people as we could. We wanted to provide education opportunities to midwives who otherwise couldn't get away from practice, couldn't afford to go to face-to-face conferences, but we're very much driven by principles of open access, free open access. And we're also interested in wanting to not just deliver content, but to provide, but to build up a community of practice. And we very much still stick to those ideas. We're not a heavily sponsored conference. We're very grateful to the people over the years who provided that free access to the technology, such as a target polytechnic through to the frontier university. They gave us free access to the web conferencing, but all the work that has gone into this has been given freely by the volunteers who help us out. And believe you me, it's a huge number of people over the years who've helped us, the facilitators, the speakers, the organizing committee. And unfortunately, I've run out of time to name everybody. But I just want to point out that we have used technologies that are freely available. For example, up until a couple of years ago, all the work we did was in this wiki. I'll just finish by saying that I literally, I'm just getting into things and I have literally run out of time, but I do want to thank everybody over the years who've helped us. And particularly the wonderful organizing committee who themselves have become a community of practice. And these are the pictures of some of the people involved in the organizing committee. And there's more pictures of us and we actually got to meet the picture there of Deborah and myself with glasses of wine in our hand. We are scattered around the world and on the odd occasion when we do get to meet up face to face, it really is a wonderful experience. We're very grateful and this was one of my aims for us to be picked up by the ICM and I'm just absolutely thrilled to bits and very grateful to the ICM for advertising this initiative and supporting us. Which leaves me with the thoughts around where to from here. We have got barriers that are reflecting back over the 10 years still are just as relevant now as they've always have been around access to technology. We very much tend, we have been a very much a white English, an English based conference, but the organizing committee that are working with this facilitating this conference now have been extending it into other languages. So getting out to people who don't speak English is a challenge and getting it out, making it accessible to. Be source poor countries is also a challenge and one that we're continuing to work on that being said, we've had some wonderful sessions and presenters from people in India, Kenya, Brazil, Latvia, so this technology and community of practice is slowly, but surely extending around the world. I could talk to you about this all day literally, but I'm going to have to hand over, but I just want to finish by thanking everybody who's been involved with us over the years for all your support and congratulations to you all. And I look forward to seeing how this community of practice is going to extend into the world across the world in greater ways over the next 10 years. Thank you. It's a wonderful legacy, Sarah, and the comments in the comment box have reflected the appreciation from a wide range of medwives across the world who really sort of applauding what you've done and how you've got your vision for getting this going and how it's now even taking into account some of the language interpretation that might go into the future. There was just one question that I picked up and that one was from Deb, is the OT group still going there? Did they get that underway? Yes, they did. They run the six months behind us, so they'll be celebrating their 10th year this year as well. Oh, that's wonderful. Are there any questions for Sarah? I see that Hilma has put me a question wanting to know about the number of participants. It's been a bit varied, Hilma. And it's actually very difficult to say because people come and go over the 24 hours and also people just because you have one person identified in the conference doesn't mean to say it's just one person watching. We've had many stories over the years of people who stream the event up on a big screen and they'll get a big gathering together, so it's very difficult, Hilma, to be able to tell. But we have had a number of research papers published over the years, so if you Google Virtual International Day, the midwife, in Google Scholar, you'll come up. And Annette, one of our organisers is also doing her PhD around this event. So do a bit of a search and you'll find, in fact, actually Annette's there, put a comment there for you. So thank you. Yes, the comment there from Annette around the attendance during the last six years. Thank you, Annette. That's helpful. Thank you, Sarah. That was amazing. And as I say, a great legacy for us to keep going and keep these connections happening across the globe. Thank you very much. Now I'd like to...


All right. This quick one. Guys, men who take care of themselves make better impressions on everybody. Pro tip, when you're dealing with, excuse me, when you're dealing with high quality women, women with some style or some class, they look at how you take care of yourself. This is why it's when I talk about men burning candles around your house, place smelling good. People look at how we take care of ourselves and infer and say, if he takes care of himself that good, if I get on his team or if he likes me, that's how he's gonna take care of me. That's how it works. I had the light just went out. That's how it is at work. That's how it is in life. This is why if you actually take care of yourself, treat yourself well, it's one of the best investments you'll ever make because instead of thinking about, that's wasting money. No, no, no, no. What you're doing is you're pre-filtering the kind of people and the kind of experiences that you want the world to bring you. I know this sounds like some hokey pokey, metaphysical hoo-ha, it's like, yeah, man, that's a bunch of, you know, the secret and I'm telling us not what it is, man. It's been scientifically proven and shown, man, men who were in clothes that are pressed get better results than men who were enclosed that are not pressed or wrinkled. Men whose shoes did it shine, get better results than men whose shoes aren't shined or dusty. Men whose fingernails are nicely clipped and manicured, get better results than guys whose hands are not or dirty.  You ever sit in somebody's car that just got it nice and detailed? I mean, nice and detailed. It just smells, it seems like the air condition is colder when your car is freshly washed, right? It seems like everything is, I hate it, it seems like everything is better.   You like, man, this brother just spent some money in here, I'm gonna take care of it. Okay, let me hit you where it really hurts. Go into a bathroom in a restaurant.  It's one of the best restaurants in the city. You go in the bathroom and the bathroom looks like a nightclub. Piss all on the urinals, got that urine smell coming out of it. Your automatic perception of the restaurant's gonna go, pfft. But if you have just an average look at a restaurant, then you go into the bathroom and it's clean.  And nothing in there. Toilet paper, the toilet roll, I mean, it just looks immaculate. You know, the little, the shitter wraps or sitting on the wall, the toilet paper's right. You go to the urinal.   It's human nature. It's how we are. When we see something that's well taken care of that can normally go either way, we treat it better. You know you do. You know you do. That bathroom thing you know for sure happens that way. Guys, stop treating yourself like a nightclub bathroom.  That's, that was pretty good. That's as good as you get.   Come back and tell me your Godfather's wrong. Peace.


Hello, everyone. My name is Philip Kuznetsov, and I will be presenting root-causing incidents without redeploying prod. Cool. A little bit about me. I am a software engineer at New Relic, where I spend most of my time building Pixi. Let's just jump right into it. So here's the situation. Imagine we're working at an e-commerce company called Online Boutique. We're selling a bunch of hip, trendy items, and things have been shrugging along pretty well recently. We've had no problems, code is shipping, everything is great, until today. The front-end service is panicking. Something is happening there that we don't really know what's going on. What's worse is we haven't released code to the front-end service in weeks, so there's no way that any changes in the front-end service are responsible. This is a classic problem in microservices. You have dependency trees across multiple different services that, when one thing changes in one service, causes a break in another service. So one thing we did change recently, which we highly suspect is the problem, we recently added this new product item called Sticker, a simple online boutique sticker, and we don't know why this is causing us any problems. The search. So we're looking in the logs, and we see this one log with the panic that says one of the specified money values is invalid. It's a bit weird. Our money values is weird. Okay. We keep seeing this error, and it keeps getting returned by this sum function. Before I dive a little bit deeper into what the sum function is, you should understand why we need to have a sum function in the first place. Why don't we just add these together? The way money is represented inside of our service, let me drop a head. It's split up into the units section and a nano section. The units is the values before the decimal point. The nanos are the values after the decimal point, but represented as nano units. So a billion nano units are one unit. Unfortunately, whenever we see this error from the sum function, we don't know what value is actually invalid. It's like what is actually causing this problem. A valid money type, as I mentioned before, is one that has matching signs between the units and the nanos, so both positive or both negative, and that the nanos are in absolute value less than a billion. For some reason, some value showing up through our system is not matching one of these conditions or both of these conditions. Unfortunately, it's not that easy to tell what happened in our environment. Ideally, we just go and add a log in here and just print it out, but in many different environments, especially production environments, that's not really an option. We might try to reproduce this locally, but sometimes a bug doesn't really appear locally. It's hard to reproduce, and again, we're searching for that root cause here. Sometimes deploying a prod just takes too long. There is a situation where you might just go and add this log in and hope that you kind of discover what's going wrong. I guess the severity of this incident is rather low, so it would be okay to go and add this log in, but that also brings in its own risks as well. Maybe while we're adding this log in, we sneak in some code that actually breaks things, such as some buggy code or something like that, and then often, for many of our production environments, we have to comply by certain rules, and deploying a production willy-nilly, especially adding just logs or something like that, is really kind of out of compliance and something we don't want to do. If only there was another way. I wonder where that way is going to come. Okay, so I'm going to show you. BPF Trace is a great tool that's going to help us add these logs in production. BPF Trace is a way to get kernel-level visibility inside of your running applications. As it mentions here, it's also a high-level tracing language for the Linux EBPF, and EBPF is really just a way to run sandbox programs inside of your kernel, sandbox being something that guarantees safety and security for your executing programs. Specifically, EBPF was designed to allow kernel developers and actually people who are not just kernel developers to extend the capabilities of the kernel and get access to the high quality data as well as the privilege context that the kernel provides. The basics of EBPF and I guess BPF Trace as a result are, for us, we're going to add this probe called the Uprobe, and that's going to intercept the running program, run the EBPF program, and then that EBPF program is going to ship the data out that we want to collect. So in our case, the arguments to this is valid function. You can think of this as analogous to a debugger, specifically a breakpoint in a debugger.  So BPF Trace and EBPF are very similar in that regard. Instead of you poking around though, we have a program that specifies the poking around, I guess. So here's an example of a Uprobe, sorry, a BPF Trace script specifically on this is valid function that we want to go and add a log to. We specify the type of probe, Uprobe, we specify where we want to go collect this data on the symbol, and then we have this body of the function which goes and figures out how to grab this data that we want, and then we print it out.  But in a Kubernetes environment where you have many nodes, this can be really difficult, or at least just tedious. You have to go and find this specific node that is running the specific pod that you want to go trace, you have to find the binary path for that specific pod's server that you're running, specify that, and then you can deploy your BPF Trace probe. At Pixi what we've been working on recently is making this process a lot easier. Instead of specifying SSH into your specific cluster, your specific node, and finding that specific binary that you want to instrument, instead what we want to provide, or what we have provided, is a way to specify a set of pods that you want to attach to. You can specify the labels inside of your pod that specify which pod you want to attach to, and you specify the namespace, and then Pixi will take care of the rest of adding that BPF Trace probe program that you want onto that specific pod. So together BPF Trace and Pixi makes it easy to add print statements in your production Kubernetes environment. All right, let's try a demo. Actually, before I do that, so this is online boutique. You can see kind of what's going on here, just e-commerce site. And then what I'm going to do is I'm going to add this BPF Trace program to go and check our isValid call. And so I'll show you that actually before I do that, here's the data we get out. So if you remember that structure I mentioned earlier that split up the float value for money into two different integer values. We have our units value here, we have our nanos values here. And so you can see actually right at the top here we have 99 cent items up here, so that is the sticker. So that looks good. That means actually when we put in the 99 cent item, things are working. So it probably is not just from that entry point. So something in our code is probably manipulating it to cause some problems. And okay, so I have to go trigger the error.  So you see an error, runtime panic, no fun, no stickers for us. But now what we can see if we run this again, we can see that we have this really weird representation.  Let me run it again so it looks better. We have this really weird representation. We have units and nanos that are not aligned in their sign. And isValid is throwing an error or returning that this is not valid and then we see an error out in our locks. So this is really bad. But what's really good is this actually gives us a big clue onto what's happening. Now I mentioned that nanos are 1 billion nanos equal to 1 unit. So if you convert this negative 10 million into units, that's negative 1 cent. So you have 1 minus 1 here, $1 minus 1 cent, that's 99 cents. So I think I have a better idea on what's actually happening here. This 99 cent value is entering into some of our sum functions. And it's being converted in a really wrong way. I'm trying to think of where we actually call this, but maybe I won't show you that actually. So in our sum function, we call sum a number of times. I'm gonna skip ahead a little bit here. So I've seen that sum is called the number of times. One time it sees a zero and the next time, sorry, one of the arguments is a zero value. The next argument is that 99 cent value that we've added. And then when I was digging into this earlier, I noticed that this condition right here, which is basically another validity check after we've summed values together, this validity check is actually incorrect. When the unit's value is zero, but the nano's value is greater than zero, we actually don't pass into this if statement here. Even though that value, which would be 0 and 99 cents, would actually be correct. So we're missing this statement and then we end up down here. And so here is where we increment the unit. So one becomes zero, sorry, zero becomes one. And then nanos get shifted over to this negative 10 million. So here's that script again. Takeaways, we're able to insert some logs into our running Kubernetes pod. And we're able to determine the root cause of this tricky incident by just seeing some of these logs come out. And just give us a little bit more visibility that otherwise would have taken a long time or taken a lot of effort to get. There's a lot to learn about these tools. I've shown you one example of where BPF Trace can be used. So specifically, we're using a U-Probe. But there are many opportunities, which stands for a user space probe. But there are other places where you can probe as well. So such as the kernel, a bunch of static trace points that kernel developers added, as well as library developers have added. And there's just many great tools that have been already listed out here that you can go try today. On top of that, I talked a little bit about Pixi. I've showed you a little bit of Pixi and shown you how you can combine the tools together to get a nice Kubernetes experience with BPF Trace. The EBPF application landscape is pretty interesting. There's a lot of great tools from networking to observability to security, and you should also check these out as well. They give you this nice access to this kernel-level visibility that EBPF gives you and add a bunch of great features on top of that.   There's some challenges with writing BPF Trace with Go, but it is completely something you can overcome. And it's very valuable once you have this tool in your tool set. I guess with that, I'll be at the Pixi booth in the Project Pavilion. And you can come and talk to us, talk to me and my colleagues more about what Pixi does, what BPF Trace does. And I think that's all. Thank you. Questions? Just raise your hand. I was just hoping you could go back to your Stack Trace code slide. Sorry, the Stack Trace or this one? I can also show it in the application if you want in Pixi. Sure. Yeah. Yep. That's it. Thank you. Oh, OK. Yeah. So do you have to run a Pixi agent on every node? And how privileged does it need to be within the cluster? Yeah, I think you need the exact names for them. But yeah, you need pretty high privileges to run Pixi. And you need to run a, we have a daemon set, so you need to run a pod in every single node of your cluster. Are there any security risks associated with that? Like, can you see that being abused as an attack vector? It's always possible, I guess. But we try to provide some guarantees for access control and everything like that. You can host Pixi entirely inside of your own cluster so that everything is maintained within that cluster. What should I keep in mind to leave my applications debuggable? I see that you have some symbols there, like with the variable names. And when I'm producing a production quality binary, I typically strip the debug signals. The symbols or everything. So what should I take care of to not... What should my future me wish that my current me would do? Oh, with the symbols and everything like that. Yeah, I think we recommend you keep symbols around to make... Is that it? Yeah, I think that's the biggest thing, as well as dwarf infos, typically helpful. I actually don't know the exact difference between the two, but yeah, I think having those two around is very helpful for integrating with a tool like BPF Trace. And what about for other technologies? So if I want to do something similar for Java, is that that easy or what else is required for...? I know Java is a bit more challenging. There's some benefits that the programs are jitted as well, but I don't know actually the details on what you need to do for Java. We have actually implemented a separate feature, not the BPF Trace feature, but a profiling feature in Java. And so there's an option to go look at our commits there. And we have a Slack channel, you can go and talk to us on Pixi on how we did that. And maybe that'll help you with figuring out the BPF Trace on Java or something like that. Wonderful. Thank you. We have a lot of time for questions. Oh, thanks. This might be a totally insane request, but could we see sort of what like a BPF Trace on the node would look like for contrast with the Pixi thing? I can try that out. Okay, well, yeah. The hard thing is I have to go and find that binary. So I mentioned it was hard. Didn't lie. Let me see. I think there's a easy way for me to grab this data. So process stats. I guess I'll, I think this is gonna take too long. I'll just show you what the rough idea would be. So, let me just copy this part out. So we have this Uprobe here and Pixi doesn't require this, but let's say vanilla BPF Trace does, you would typically add like path to app, path basically. And then you would have to go SSH into your node, make sure BPF Trace is installed and then go and add this, then run the script basically. So I guess, yeah, I'd be running that. I'll just save it. A BT. I can do it on this like dev machine. I just, it just won't create any data. Oh man. Okay. I thought this would be easy. Okay, well, let's, before we do that, I'll just show you how to run the BPF Trace script first. So this is a approximation. Let's see. Isvalid.pt. So you'd run something like that. I actually have to adjust it so that it is. Okay, so that's attached now. And then if I can get the front end service running, then it should work. In the meantime, I could take another question, I guess. How long does the trace? Oh, thank you. How long will the trace that's injected last? We set a TTL for Pixie. But if you notice here, actually, when I was doing it locally, it just runs until you control C. So you send it a signal. So if the pod crash loops and restarts, will it get injected again? Yeah, so we're, I think that's the next thing we're working on for this particular feature is just making sure it comes back on. So we just released this feature. I think we're actually releasing it on Tuesday. So follow us on Slack and we'll update you on that. But it's coming out soon. Perfect, thank you. Oh, but sorry, to that point about releasing it, we have a K-Probe feature already. We're just supporting user space probes with this selector thing on Tuesday. To your demon set, can you start the demon set after you've found there is an issue and you want to debug? So does it not run all the time on the cluster? Yeah, you could deploy the demon set after you've run into the issue. It's not requiring, it doesn't require you to go and run it continuously. So if you want to add it afterwards, you can totally do that. And we've made our deploy process pretty fast. So you can deploy and get data within, I think, three or so minutes. And, or deploy, let's say, deploy Pixi and get BPF trace data in three minutes plus the time it takes to write the BPF trace script. Yeah, this can address a lot of security concerns because if it's normally not installed and then you install it only for the time that you need it for debugging, this would be made in production very easy. Sorry, say that one more time. So if you only install it for a short debugging time in production to figure out a serious problem, it's something very good because then the security guys are much happier. Right, right. All the time. Yeah, yeah, because you can delete it and make sure it doesn't, like somebody doesn't see it as an opportunity, yeah. Do we need to make any changes to running pods for Pixi to be able to observe it or Pixi? As long as your pods have symbols, both Pixi and BPF trace should work. And there might be a few more caveats on that as well. It's in our docs. But I know that symbols are important and to some degree Dwarf Info is helpful, but I don't think actually Dwarf Info is a hard requirement, so yeah.  Yeah, if you just use the default build. Oh, I think up here. Yeah. Really just kind of a follow up on the symbol thing. Yeah. I was just wondering if there was a way to use an external symbol store so you don't have to embed them in your production images, but you can have them available somehow for your running purposes. We have not designed anything like that before, but we've thought about it, and I think that's a really cool idea. So it might be something. So actually we have Pete back here. He's somebody who works closely on this and he can talk to you about this afterwards. Yeah. I think there's a question back there. Here? Uh-uh. Here? Of course. Sorry. Routing people. So if I understand it correctly, if you have access to the Pixie agent, or at least that UI, you can run any code you want. I guess I was just curious how you control access to those agents and search it or what, I guess, what's the security stuff for that? Yeah, there's a few different options. So there is this data collection side where we offer the ability to redact key PII containing information so you can run in restricted mode. With regards to BPF trace specifically, we have adding more access controls on the roadmap. So I think a temporary solution for, say, getting the observability power of Pixie while we are working on the access control side of things, you can go and pipe that data into some open telemetry collector and create a view on that side, basically. So I guess you can pipe that data to an open telemetry collector, send it to Prometheus, and then use Prometheus views or something like that, or a Grafana or some other tool like that. And that way you can get that data and everything like that while preserving the permission layer, I guess. You can also just remove certain users, I guess, from your system. You can hide certain users, or prevent certain users from signing up, so. Okay, I can respond about symbol stores. We are, I'm also on the Pixie team, so kind of back to the question about that. We are aware that there are already existing symbol store technologies, and we are, that is not on the roadmap yet, but it would be a really, really neat thing to enable both for BPF Trace and also for the profiler. And in general, it would be super useful. I can see that. So should anybody join us on Slack and want to discuss symbol stores where we are absolutely interested and looking to find the capacity and somehow improve along that dimension? No one else? Okay. Oh, there are some questions over there, okay. By the way, we have t-shirts at the door, I think. Is that true, Michel? Yeah. If people want t-shirts, feel free to grab them. Can you explain a little bit how you target what you want instrument? Because here in the probe, is it gonna probe all the methods that have that name or Pixie's smart enough to use labels to target special pods? And if within the pods, maybe a container as well? Yeah, yeah, so we have this full symbol name, first of all. So I guess it's a little bit more specific. But yeah, you can specify the exact pods that you want to attach to. There is this label selector down here. We have our label name and then the label value. So app is equal to front end. So it's only attaching to the front end service that was having the issue. But we actually, we have this code in a lot of the other services as well. But we wanted to ignore those because those services were not having that same problem. Okay. Yep. Any other hand on the other side? Yeah, we still have five minutes of time. Right here. Folks, who is living, please just leave quiet, okay? Is there a performance penalty in having that as part of, you know, Kubernetes demo set or processing Kubernetes instead of having that as a byte code waving or something like that as part of my build process? You're saying you like insert an agent or something into your code. So instead of running, instead of having that been applied to a running pod, use those, the same script to apply during my build pipeline so that those are injected, you know, into the binary itself before I run it. I've, we've never done a like toe for toe comparison between the two as far as I'm aware. But I imagine you can continually optimize, say the byte code injection and stuff like that. But the same way you can continually optimize the EBPF injection. But at the end of the day, you're kind of doing the same operation. So I imagine that the performance is comparable. Right, so. I don't have the great answers to that, unfortunately. That's good. So just to be clear then, you're doing that process once only. You're not doing that continuously. You're not reapplying or applying the same waving to the byte code continuously, right? When you click run, it just only once. Oh yeah, it deploys only once and then it's kept around for the TTL that you specify down here. Five minutes there. Yeah, yeah. And then it does another processing of the pod or the binary to remove the probes. Yeah, yeah. We are like manager service. You can call it that. We'll go and remove the probe that's running. Okay, thank you. I think it's done. All right, thank you all again. Thanks for the great questions.


Okay So thanks to the previous speaker for leaving a few additional minutes for me. So I'm gonna take full advantage of it So I'm Rachel and I'm going to try to tell you about our new work on Bob-Op's construction of Concurrently secure protocols. This is joint work with sort of Rappel at Cornell Okay, so as you have heard many times the problem that we're looking at is this secure multiparty computation problem And in particular the goal here is to allow a set of mutually distrustful players to be able to collectively Collaborately compute any function on their own by just sending a few messages to each other and Two things we want to guarantee is the first correctness that is the output of the computation needs to be delivered correctly and second privacy That's the private inputs of each players should remain hidden and We would like this to hold even when there is no honest majority in the protocol execution So these two intuitive requirements in the literature is formalized by this beautiful concept called Assimilation paradigm where we would like to compare the real world where players simply send a message to each other With an ideal world where they get help from a trustee third party who simply compute the function for them and We would like to say that the real world is actually as correct and the private as the ideal world and Meaning that for every anniversary in the real world launching some attack There will be another anniversary in the ideal world who can launch the same attack So if that's the case then intuitively this must be secure because in an ideal world There's no attack and therefore there will be no attack in the real world either So here's slightly more formulae by saying launching the same attack What we really mean is that it's gonna achieve the same effect on correctness and privacy and in particular for correctness We would like the output of every player in both worlds to be the same and for privacy We would like to see the simulator can learn whatever the real anniversary can learn how by simply simulate its view So in this talk, I'm going to focus on a specific type of anniversary who always performs static malicious corruption So traditionally this multi-party computation Problem is considered in a standalone setting But just as motivated by the previous talk already This is not how the real world look like the real world looks like this So there are many sets of players executing many different protocols or at once and it is possible that now an anniversary can potentially participate in many protocol execution and launch some kind of coordinated attack So what we want is that we want the real world where many Executions of different protocols can simultaneously remain as correct and private as the maximum many Executions in the ideal world with independent trusted third party so as We have heard the name the most desirable and the strongest the formulation of this intuitive requirement is universal Composability it is mostly desirable because they really put forward the strongest Concurrency requirements however because it's so strong and it becomes impossible so in order to get around this impossibility without and In particular without going into additional use of trusted infrastructure Many previous work has started to consider a relaxed notion of security called a super polynomial time simulation where we simply allow the simulator to run a little bit longer and Along the same line there have been a few works Trying to propose related notions as lacks the security notions where they put a precise more precise Condition on how much more powerful those simulator can be But in general overall in all those notions by allowing the simulator to be more powerful The good news is that now concurrent security becomes possible So great however here I would like to argue that these results so far only feasibility results only Why really due to the nature of their non-black box Construction where there's a ton of cop reduction flying around in the protocol So naturally here we would like to seek Black box solutions where then we will have automatically no cop reduction and potentially will give us more efficient protocols So where do we stand with respect to black box? Marder party computation protocol So in the standalone setting great the problem is basically soft After a long line of research so far we have constant round the black box Marder party computation protocol from the minimal assumption of I'm honest OT to the concurrent setting the situation become much less complete and The only positive results we know are those unconditionally secure UC protocols using very strong trustee setup like ideal OT or hardware tokens And in fact, we know no black box construction in any weaker setup model or in the plain model So naturally the question is that can we have it can we get a black box concurrently secure protocol in the plain model and In this work We provide you such a construction So we give a black box construction of concurrent secure Marder party computation protocol in the plain model our protocol is based on the minimal assumption of some honest OT and Achieve security in this model called the UC with super paranormal time helper Without you don't have to know the detail of this model But just keep in mind that it directly implies super paranormal time security and also enjoys universal composition Okay, so great. How do we do that? So the result is achieved in two steps So first of all it follows from the classical results that every functionality can be implemented using ideal OT so this step is Unconditional therefore by definition black box and they achieve security in the UC model So the main body of the work is really try to implement OT using a stand-up Stand-alone some honest OT in a black box way So previous works achieve this step in the standalone setting and in this work We try to tackle the concurrent setting and we implement OT in the UC with super paranormal time helper model So the main tool that we use in this step is a black box construction of a notion called the CC secure commitments Which was first introduced by connecting and passing 2010 and this is really the key notion that Enables our results. So let me first try to tell you what it is So CC secure commitments at a very high level can be viewed as the commitment analog of CC to encryption So look at a man in the middle execution where there's an adversary trying to break the hiding property of a left the commitment While having access to an oracle that breaks commitment of its choice Here by breaking we mean that for every commitment of the world is the diversity sent to the oracle The oracle will return back the committed value in this commitment if it's valid Otherwise it gives bought So I want to note that in fact this formulation is likely different from the original definition in cell p10 There they consider a stronger oracle that gives also the decommission information besides from the committed value The reason that here we're considering this weaker oracle is because in order to get a black box construction We can in fact only achieve this weaker notion But luckily as we show in the paper that this weaker notion also suffices for building concurrently secure protocol Okay, so now with this oracle in mind Where I say that a commitment scheme is Children commitment attack secure or CC secure if in such a man in the middle execution with the committed value oracle One of the two things happen Well, either he forwards the left commitment to the oracle Therefore trivially he gets a committed value. I guarantee no security. This does not happen Then the left-hand side committed value must remain hidden So this is really exactly the same a copy the twin brother of the CC to encryption So in the literature, there is a very closely related notion called the concurrent Nominable commitment some of you may have been wondering what's the relation between them So not many more commitment requires that the diversity should not be able to commit to any related values that's With the commitment that he received So this definition can be equivalently formulated as Allowing the diversity having access to the committed value oracle at the end of the whole Execution and getting all the committed values back in parallel So naturally immediately we have the CCs Commitments is stronger and the implies nominability So now with this definition of CC secure commitment in mind, I can tell you the results in this work More formally into theorems. So the serum one is that said There is a black box construction of CC secure commitment from the minimal assumption of one-way function and The second serum says that once you give me such a commitment and apply some honest OT protocol We can black box they implement the ideal OT functionality in the concurrent setting So for the first serum to give you such a black box construction We actually have to borrow many techniques from previous works in particular like techniques behind the non-black box construction of CC Commitments, we used the black box trapdoor commitment construction in PWO 8 and we used the cut and choose technique for consistency checking originally introduced the four building black box nominable encryptions and A lot of work a lot of a blast went and tears so There's a lot of interesting ideas going on in this step, but because it's so complicated I'm going to spare you This part in this talk and they just focus on the second theorem So what I want to show you is that really CC secure commitment is the key notion The right notion for building black box concurrent secure MPC protocol Feel that even without the first the serum theorem 2 is interesting When it's on because if in practice we're willing to assume that some practical schemes like a yes is Assisted a commitment then plug it into theorem 2 we directly get a very efficient constant round black box concurrent MPC protocol Let's finally try to get our hands dirty a little bit try to prove theorem 2 So first I Just trust me that it falls from previous work that we can in fact start with something stronger Not a some honest OT but Malaysia's Sender OT that is already secure against the Malaysia's Sender But only secure against the some honest receiver and the task here is to try to use Some classical approach so that we can lift up The security against the some honest receiver to security against the Malaysia's receiver So roughly the protocol will look like this where the Sender and the receiver first They do in parallel Many to an Malaysia Sender OT executions using completely random inputs So at this point notice that each of these basic OT execution is only secure against the some honest receiver So what we would like to have is that we want to enforce this actual Malaysia's receiver to behave honestly in those OT executions So in the non-black box word Stribute this is like crypto one-on-one right give us your knowledge to prove that the receiver has acted honestly however, in the black box word we can't do that Instead we're used to cut and choose technique which says ask the Sender to choose half of those OT executions at random and Request the receiver to send back the randomness used in those OT executions and The Sender would only accept if the receiver indeed acted honestly according to those random coins that it reveals in those OT executions So nothing if a receiver can pass such a test with respect to So many OT executions chosen at random and it must be that it has acted honestly in most of the OT executions Otherwise, it would have been caught with high probability So with this very strong guarantee We can then use some known sub protocol called the OT combiner to try to utilize the rest of those The rest of the OT execution that hasn't been opened to transmit the real input Well good This is awesome because it seems like this simple protocol works. We already have a protocol that is secure against the malicious receiver Well, there is only one catch that is the catch is the cut and choose Make the protocol lose its security against the malicious Sender now So without going into too much detail, let me directly tell you where the problem is the problem is Now in order for a security proof Against the malicious Sender to work out the simulator while acting as the receiver need to be able to bias the set That is that it needs to open There's no way of doing it right now with this protocol because here the malicious Sender will simply dictate the set T So naturally to solve it We're gonna change this protocol so that the Sender and the receiver will participate jointly in a coin tossing protocol to decide that the set to be cut and Now with the coin tossing the simulator can bias the set to be cut and the security proof will go through I have just shown you is that a very very at a very high level roughly speaking Give you give me a semi honest OT protocol and the coin tossing protocol We can implement ideal OT in the standalone setting and this is indeed what previous work has shown so now when we move to the concurrent setting the main issue is that I Need a much stronger coin tossing protocol. I need a coin tossing protocol. That's in fact the simulation sound What it means is that no diversity can bias the coin tossing without even if the simulator is doing so Or more formally to see the problem Consider this main middle execution where the diversity is participating in many left and many right-hand side the coin tossing Executions now here the simulator comes along and it wants to bias the coin tossing results for each of the right execution The first execution is as 42 Second execution is as 42 again Well, it can do that So the requirements now is that even when the diversity is Receiving those bias the toy coin tossing executions We would like to say that he himself cannot bias the coin toss results on the left-hand side So our results shows that as long as we have such a simulation son the coin tossing protocol and Plus as I'm honest OT then we can implement ideal OT in the concurrent setting in a very similar way as I have just told you So now everything or the task you have reduced down to constructing such a simulation sound Coin tossing protocol. How do we do that? We're gonna use the CC secure commitment So I'm gonna I guarantee you this construction is really simple. Everyone is gonna get it Okay, so how do I construct such a coin tossing protocol? Take the vanilla coin tossing protocol Everybody knows and simply replace the first commitment with a CC secure commitments So why is this simulation son? Look at this main middle execution? How can a simulator bias the coin tossing result on the right-hand side? It can do so if it can break the CC secure commitments in the first message So now it follows you from the CC security that even if the simulator Has access to a committed value oracle in order to bias the coin tossing results the left-hand side the CC secure commitment is still hiding and Therefore the adversary cannot bias the coin tossing results on the left-hand side done and This concluded the proof for theorem 2 So in summary what I have shown you in this talk is that we give a bubble construction of concomitant secure multi-body computation protocol in the play model and The key construction is a black box CC secure commitment Which I actually didn't tell you about how it is constructed But just I want to really highlight the point that I think CC secure CC security is the key notion and the reading being that in a black box Construction there's lots of cut and choose lots of opening and we would like to guarantee that some security will hold Even with respect to openings So one catch unsatisfactory part of our result is that the construction has a very High round complexity. In fact, it's it's an order and runs. So one obvious question is can we get a better rounds? So that's all what I want to tell you. Thank you


I have the feeling that all the whole team had in the dugout prior to the game watching that ceremony for CC Yeah, that was that was really special. I've been a part of a few ceremonies similar to that, but um You know that one just had a real personal feel to it with Ember and the kids and and obviously miss Margie Read messages to CC and I was sitting next to the judge Told him I needed to put my sunglasses on when they started doing that because um, you know CC just means a lot to me obviously we've got a great relationship played together for a long time and Gonna be different here without him, but um, you know just thought it was a real special ceremony and Cold witness was that the sentiment throughout the dugout a lot of guys reaching for sunglasses. Yeah, maybe so I mean, you know, like I said, and you saw during the during the video, I think he's He's made a big impact not just on his teammates here in New York and the city of New York in this community and the fans but all across the country he's You know affected a lot of people in a positive way, so You know, I know that um, you know, it's a special day today What impressed you playing behind Louise today in his second start? I thought he looked really good I thought his fast block of man was good. Maybe have a little more life to it Sliders seem to really have an extra gear to it when he needed it with two strikes especially and Thought he looked like his normal self out there You've been part of a lot of teams that have played here in this building You guys have not dropped a series at home since April. What was different about playing here in 2019? Um, we just seem to play well at home I mean, obviously our team is built for this ballpark but you know, we love being at home with our families and In our own beds and playing in front of our own fans and and here in our clubhouse, so um, you know, I think that You know, it's one of those things where we've just been on a roll been playing good baseball and um, you know, hopefully finish up strong this last week Right with a week to go you guys are gonna be half came down from Houston. They have a tiebreaker How important is that to beat them out to get that on film your mind? Well, I think it's important But I think it's more important for us just to play well and finish the season on a strong note and And go into the playoffs clicking on all cylinders. I mean, we can't control what they do this last week. So Just go to Tampa in Texas and continue to just Try and slow things down take things one day at a time and Continue to play good baseball You try to keep up with judge in the power derby the home runs He might be trying to keep up with me, but um Yeah, he's um, he's trying to we'll see how this next week goes, but I've I told him a few weeks ago. I was pulling hard for him to get to 30. So I think he'll get there With the season wasn't he back to you the most and what had he been with you as a teammate? Uh, he's been like a brother to me, um, you know since 2009. Um, so I guess for the last 11 years, um You know, it's just been a pleasure to get to play behind him and and get to know him here behind the scenes and Not just a guy. He is on the field not the field but away from the field and the way that he treats people, um You know, it's um, he's set a set a great example for uh for all of us to follow Right with the home runs. You're pretty close to 30 now Does that mean anything to you with the week left to play? Would you go for that? No, the 30 doesn't I mean, I've already hit 18 or 20 more than everybody expected me to hit so um, you know, just continue to try and have good at bats and We go out there every day and and try and continue to take care of myself and be ready for october