Well, if you or someone you know has experienced the loss of a baby, loss of a pregnancy or a premature baby, then this walk is for you. The Bemidji March for Babies will give people the platform to share their stories and make sure others have their voices heard as well. The March for Babies Committee was already working ahead by organizing the items for the silent auction on Saturday. The March for Babies is actually the oldest fundraising walk in the history of our nation. So it's really amazing to be a part of that and to have such a strong Bemidji community involved. The event kicks off at 9 Saturday morning with the walk starting at 10. It happens at the Bemidji State University Rec Center and will feature special care nursery graduates and several children's activities. If you've enjoyed this segment of Lakeland News, please consider making a tax deductible contribution to Lakeland Public Television.


Jesus' life was not taken from him. I have authority to lay it down and I have authority to take it back up again This charge I have received from my father. When Jesus was crucified make no mistake. He was crucified Voluntarily at any given moment. He could have called down the armies of heaven to usher him away into safety But instead he endured why Jesus said earlier on in the chapter that he is the good shepherd who lays his life down for Jesus talks of the shepherd who leaves the 99 sheep that he has in safety to find the one sheep that has gone astray Isaiah 53 says that we all like sheep have gone astray every one of us has turned to our own way But the Lord has laid on him the iniquity of us all while we were still sinners Christ died for us bearing the weight of all of our sin and shame that we could be a part of his sheepfold That he would be our good shepherd our father that in him we would find rest for our souls


Yeah, no, D-Led, as I said I'm proud to coach this group, you know, you know we're building something in there and these guys fight and so you go on the road like this against a really good veteran team and we our guys kept swinging it's unfortunate with the what happened at the end and you know we'll go in there and we'll watch the tape and we'll keep moving forward and correct things but you got a ball game it's 28-25 we're backed up we get to third and inches and we don't convert then obviously they get the short field and they go up and then a couple tip balls later and that's what the score was but we got a group of fighters in there at D-Led and I'm proud to coach them. No, I just think what happens is humid is hell out there you know I got to look at it I don't want to overreact their D-Led but a lot of times those guys are rushing they're tired and so it's just kind of two guys kind of fighting in the mud there and they did a nice job getting their hands up we got to evaluate you know how that happened why but that's my snap judgment there's a lot of plays you know you can't just blame it on one play you know it's a lead-up you know we we got to be able to convert third and inches to not even put it put the punter back there you know everybody's got a job to do obviously you get down in the fourth quarter those plays are magnified but there's a lot of plays that lead up to it like everything we'll go in there and evaluate what we did well what we didn't and you know we got to keep improving clearly. The margin error is small in the NFL and usually comes down to you know turnovers and right they we had three they had one and you know ours came at critical times in the fourth quarter and I would say that about any game in the NFL I mean very few times you'd say the margin error is big in the NFL I mean these are professionals you have two teams going out there fighting it out so that's everything that's every week like margin error is small yeah look I mean they got what two pick sixes all tip balls so that's 14 points right there so yeah it looks ugly in the box score you know if you're just on the surface looking at it but understand the context of the game you know we got a chance in the fourth quarter we got we got to convert and to go win it or worse you flip it we had all our three timeouts maybe a pen you know pin them back and and you got it you got a chance but we didn't convert they did and that was the difference yeah you had the one right at the beginning the half to what's that right well look I mean the things why that happened backed up you know I could give you the reasons they sound like excuses we can't let that happen for multiple reasons you know and luckily we didn't we still had a timeout and we handled the situation pretty well I mean they had a ray of penalties we took advantage we were getting the ball hoping to go double them up we got a field go right at the end of half and then you know we get the ball rip off a decent run and they tip it up and they intercepted it right and when they believe they went up 28 to 10 so yeah we got to clean stuff up that's every week we'll look at that Jeff but you know I haven't said all that these guys keep swinging and you take advantage and at least we there's a positive we handle the situation before the half but we didn't double them up because we got the tip ball right there and they went up 28 10 there's usually a reason when you lose you know and you look back on those certainly doesn't help but there's everything we got 15 more this group's gonna fight Jeff that's who we're gonna be and we're gonna keep improving yeah sure you know you go in there we were better in the red zone like I said two minute right for the half proud of the defense you know we went aggressive they stopped us on the quarterback sneak and the you know we put the defense you know out there with the short field with Tom Brady over there but those are the risks we were gonna come out here and not swing so yeah I mean those are things that kind of stick with you and these guys kept coming back and back and back and it's just a shame when you get in there and you're a three-point game and then it it ends the way it does but again they took advantage and credit goes to Tampa look like I said that the score got out of hand but a lot of that was on the offense right I mean you could almost put four of those touchdowns give or take two of them for sure pick sixes one of them was a tip ball right in the end of the red zone and then the other one we went for a fourth down so I know that you know everybody feels sick when you get that you see that box score but there was some positives they got to the quarterback Dante made a big big play that was a huge play you're looking for another positive there Jeff you know that that changed things because that could have gotten ugly Dante stepped up and and and caused the sack fumble you know those guys they got they at times they got pressure I mean we we knew they're gonna throw it down there and credit them they made the place I go it's it's that's life in the NFL we got to look at it gotta look at the injuries obviously we take everything serious and it's the next guy up and that's our job as coaches to adapt and like I said that that is unfortunately that is life in the NFL and so you've got to find ways and put the guys in the best position to succeed so we'll look at that you know we don't want to make those decisions right now yeah so they picked up the horse collar is that what you're asking about yeah and they also they had the horse collar so there was two flags and they picked up the horse collar and so they went with the block in the back again that's their call those guys have a tough job to do but yeah that was a pretty big yeah swing there because that kind of led I believe right the lead coming out we had the run the next one was the tip pass yeah yeah well because here's why I mean you you want to get something positive going we had something we were trying to get in the punt you know clearly didn't work and just where the game was right then and you got to make those calls you know you don't want to get in the short field I felt better the next time wanted to be aggressive got into it I felt we needed something to get us get us a spark or something to go through so that was why I mean the numbers are I mean it's what the coin there when you go for it but early in the game where I felt we were I made the judgment it's in the punt team out see if we could get them to jump obviously we didn't so we punted it yes he's a good football player so we hope to build off that it's fun to coach glad he's on our team I think it's it's a show it's a sign of his growth like I said Kyle will continue to add every week it's a credit to him and then obviously the comfort level with Matt and him I think you've seen that starting to pay off it's it's hard it's a hard position to play in the NFL in the way we ask him I mean you're asking him to go be a receiver you're asking him to go block like a tackle of times and we move them all over the place a lot of rookies can't handle that Kyle clearly can and like I said I'm excited we got 15 more opportunities to work with this group and it's a long season and we got to continue to get better there was good signs but obviously we got to find a way to win these games and not have the things that happen in the four quarter that's a difference they're all different they're all different the guys and coach that's why I don't do comparisons because it's not one size fits all it's what they can handle and you know hopefully Kyle have a long productive career but have other guys at that spot that it's been maybe slow and then they've taken off year two year three well I think what you're seeing is why we brought Kyle in here I think his growth is accelerated and what we're asking him to do so please with that hopefully continue to build off it


Hello folks, welcome once again to problem solving and in this session we have taken a different equation, this is not an algebraic equation, we have taken an exponential equation. Now what is an exponential equation you know, let's understand that first and then we'll see how we can use the methods known for quadratic equations to solve exponential equations. For that matter any expression, exponential expression will be of the form of a to the power x right, so a to the power x is nothing but where a is a constant, a is constant and x is variable okay, so this is how is it different from algebraic expression, so if you see algebraic expression will be of the order of the nature x to the power a, where x is variable a is constant here, it's upside down, so the base and the exponent has, have changed their places right, so hence bases are constant but the exponents are variables and if you have an expression containing those terms then it is called an exponential expression and when you equate this exponential expression to anything else it becomes an exponential equations, so if you see here 2 is the base, x minus 2 is there is a variable power on 2, similarly 3 minus x is a variable, x is a variable so hence 3 minus x keeps on changing so hence 3 minus x itself is variable varying and hence the base is 2, so base is constant power is variable so hence you know and there are 2 such terms and then they are added together and equated to 3, so hence this is an equation, exponential equation, how to solve them, very good, let's try and solve them, so hence can we simplify this a little bit, so if you see using the exponential rules we can say to the power x minus 2 is to the power x divided by 2 to the power 2, similarly you can see 2 to the power 3 by 2 to the power x is equal to 3, this is what we can say by a to the power minus n is equal to 1 upon a to the power n, this we have learned in the rules of indices, so now what, so if you simplify further it is 2 to the power x to the power upon 4 plus 8 upon 2 to the power x is equal to 3, now we will play our card, definitely this is not a quadratic but let us say y is equal to 2 to the power x, I can say that, so the equation is reduced to y upon 4 plus 8 upon y is equal to 3, so this implies it is y square plus 32 having the common denominator as 4y, correct, is equal to 32, is equal to 3 sorry, so hence if you reduce it further it is y square plus 32 is equal to 12y and this will become y square minus 12y plus 32 equal to 0, so hence y square minus 4y minus 8y splitting the middle term 32 equal to 0, so this implies y times y minus 4 minus 8 times y minus 4 is equal to 0, isn't it, so this implies y minus 4 times y minus 8 is equal to 0, right, so hence y is either 4 or y is either 8 but we want x not y, so what was x, so if you see y is equal to 2 to the power x, let us write it again, so 2 to the power x is equal to 4, so can be written as 2 square and here similarly 2 to the power x can be written as 2 to the power 3, so if the bases are same then in an equation, exponential equation we can equate the coefficient, sorry the exponent, so hence x is 2 and here x equals 3, right, so for exponential equation what you need to do, you make sure the bases are same, the bases are same then you can equate the exponent, so hence there are 2 values, 2 roots to this equation x equals to 2 and x equals 3 my friend, so hence even exponential equations can be reduced to quadratic equation and then can be solved.


What's going on guys got Kyle here with latent sports cards, and we are ripping this is one box for Talon H We've got a 2022 formula one light tops chrome Good luck Talon let's see what we got it really is always it really is it happened quick it happened quick man that Honda engine Once they switch the Honda Red Bull kind of took over I Think they're going back to not Honda right soon. All right. Good luck on the light here, mr. Talon This one's got a ray way then and I can feel it If it does it's going to be Carlos signs on the ray wave to start us off black and white ray weight Carlos signs portrait got a check-out Shumacher and williams Williams team card there What's up pitman Just in time for some f1 got some uh sapphire right after this one Just in time to watch some f1 here We've got a Joe Guan Yu base rookie and this is black checker going to be lance stroll non-number Lance stroll car card there for Aston Martin is Callan Williams on the black and white ray wave There's a louis hamilton a little sticky on this box And refractor that one's going to be val 3 botas Mercedes they're getting the w getting the w Yeah, it's funny always too because you don't see uh You don't see toto wolf as much anymore. I saw them interviewing him today and I was thinking that I'm like We don't see toto as much now that Now that max is all over There's lando on the refractor driver of the day austria Speed demons of max that he is that he is there's a verstappen And team card there for alpha rameo There's a Joe Guan Yu rookie car card That is a ferrari team card There's a k mag Got prima racing on the team card and this is going to be max verstappen driver of the day france On the true purple to 399 Very nice one there verstappen Driver of the day france. Yeah, right always. He was man. He was I know max didn't want to be in the show for most of the seasons, but uh I know toto was toto and uh guinter toto and guinter were the stars for sir, man First couple seasons at least They were interviewing the crap out of toto first couple seasons because they were winning everything Now we've got a golden purple. This one's rookie joke on you not numbered on the golden purple out of light Nice rookie there though It is still short printed. They are not numbered on the uh, the double colors ones Very nice one there. That is a beautiful looking card as well That's a sweet one Team card for uh, alpine There's mick shoemacher quick mick refractor and speed demons of lance stroll Not so much. Uh, he had a nice finish today though I don't know if I call him a speed demon, but There's a future star as callan williams on the black and white ray wave refractor check-o That is that it's pretty scratched there. I'll send a box with this one.  We've got a williams black and white ray wave. Nice one here charles the claire portrait nice charles portrait sidle charles again wave coming It is gold wave marcus armstrong number 14 of 50 For the f2 high tech driver Nice low numbers here for the uh for the light box. You go talent on the gold wave to 50 marcus armstrong for uh high tech Speed demons dany rick. The heck is going on my re-stream today. There's a refractor latifi And uh team card for acid marten Nice little color at the end There's a marino sato formula one uh our future stars for f2 And we've got alexander albon on the uh purple checker to 399 or 199. Sorry Purple checker to 199 there for williams All righty talent that will do it for your uh one box of f1 light We will get a box out with that damage card. Thank you so much my friend get it right out to you


Even before the COVID-19 pandemic, the world was not on track to end world hunger and malnutrition in all its forms by 2030. Under the shadow of the COVID-19 pandemic, up to 161 million more people were facing hunger in 2020 than in 2019. New figures estimate that between 720 and 811 million people around the world faced hunger in 2020. The prevalence of undernourishment increased this past year to reach a level of 9.9%. Around 660 million people may still face hunger in 2030, in part due to lasting effects of the COVID-19 pandemic on global food security. This represents 30 million more people than in a scenario in which the pandemic had not occurred. More than half the world's undernourished are found in Asia. An additional one-third reside in Africa. Globally, 2.37 billion people did not have access to adequate food in 2020, an increase of nearly 320 million people in one year. Globally, malnutrition in all its forms also remains a challenge. In 2020, 149.2 million children under age 5 or 22% were affected by stunting and 6.7% suffered from wasting. The actual figures are expected to be higher due to the effects of COVID-19. 38.9 million children of children under 5 or 5.7% are overweight. In 2019, the high cost of healthy diets combined with income inequality caused healthy diets to be too expensive for around 3 billion people, a number expected to increase for 2020. In this environment, food systems transformations aimed at bolstering food security and nutrition are more important than ever before. Major drivers negatively affecting food security and nutrition include conflict, climate variability in extremes, and economic slowdowns and downturns. When food systems transformations focus on fostering greater resilience to these drivers, food systems can better provide affordable and healthy diets that are sustainable and inclusive. Six transformation pathways tailored to their specific context will help us emerge from the shadow of the COVID-19 pandemic. And such a transformation can be a powerful driving force towards ending hunger, food insecurity and malnutrition in all its forms, for all.


This is his first time ever seeing FPV and he's watching bubby fly right now. Oh my god. Why am I flip upside? Oh this is cool. Yeah the props are on right. Yeah you need video like like okay so listen up this is how it works you've got these goggles. You can't actually fly FPV without them. You have to go. So you guys might be uh seeing my quad and like you've got motors will be having an air. I'm flying the pita vex motor I'm slowly making the transition to success on a light-lit build and I've been wanting to try a lot of different success motors so this one's really cool because it's a 2306.5 1985 kv and I know James put a lot of thought into this like I don't know where he is I wish he was here like so we could talk about it but oh this motor right here yeah this 6s 1985 kv 2306.5 why you choose those specs that's the year I was born is it actually yeah thank your old bro exactly I want everyone to know I'm an old man the specs are pretty similar to the motor I was flying which is a t-motor f40 okay but yeah I like the little bit extra height on the stator okay it gives you a nice mix of like the feel of a 2306 and a 2207 nice what a lot of people like about 2207 it's just like that raw power that you get so yeah when you're hiring the throttle you can really punch it and get that stealth when you're low in the throttle which where I usually hang out it's like nice and smooth so if you check on the top of the bell right these tiny little nubbins actually little spikes and these are excellent for prop grip trying to use all the premium parts you know so we got like a single strand winding that's going to be more heat resistant nice that nice heat resistant coating on it just simple design with like six spokes nothing crazy the base has an interesting feature where the side of each hole where the screw comes out there's a little cut out oh you actually see the screw as it starts to come through right problem with a lot of other motors and their bases is sometimes you'll have like a short motor screw and you can't really tell yeah when it starts to approach talking about the top you get that confidence that your screw is actually going up and not contacting things like your winding super durable super nice performance what you want exactly yes it's everything james wants in motor it's a premium motor available about rhoda.com it's like I mean I'm just testing success because little little sneak peek I am working on my own motor and it will be 6s and 8s capable so yeah I didn't come prepared with anything so I just put these on and I'm gonna go get my man gooey and set up and just gonna rip I just got my first practice cruising around james your motor like it's so like mushy yeah it's very different very different than anything I float this there's there's just it's the same there's nothing here and I wonder how much of this is like 6s too right like high kv6s isn't something you've been flying either um I mean off the record I have been flying it a bit well I wouldn't call those high kv though like 1850 that's that's I've been flying um oh yeah I guess the quad that I was flying was super light yeah yeah but it's different it's different yeah so I'm gonna get someone practice on it and try to like because I think what I'm gonna end up doing is using more higher throttle you're gonna be like going so fast yeah let's see yeah okay I just get someone packs up it like if you want if you want punch you gotta blip the throttle and that's what I do is lots of little blips like I'm I'm on throttle very short periods I see why you fly the way you do yeah it doesn't it doesn't really suit your style as much like I can see even like when you were coming up here like I would have blipped a little right before I went over the top yeah and it gives you that extra edge and a little bit of float because there's when you go inverted there's like different ways of doing it some people like to be on throttle where it like the quad has some power to it still but it that tends to send the quad downward a little bit because it's got that that you know downward authority the way I like to do stuff is like I'll blip the throttle and like hook it backwards and then go off throttle and it just coasts through the air it's not as like smooth you get like a weird kind of like jerk right before but it's almost like a popping and locking you know kind of motion I think that's how like a lot of juicy pilots get there that juicy look oh I will say it's weird not having that low end control you watch my sticks when I fly I hardly ever go above 50s throttle and when I do it's just those short little blips so it helps to have the throttle like feel the way it does where it's soft and kind of like cushy definitely just like violence at the top and just like we'll just send you all right so what's your setup all right so my setup I'm rolling with the old school apex impulse rc frame been loving it ever since I got into the hobby two years ago nice I fly kiss ultra fc also fat tech fc the ec's I run are usually the fat tech 45 amps I run most of those on my rigs but on this one I do have the foxier uh reaper nice which I haven't saw any difference actually I mean some people probably hate me for this because of this but I do like how fat tech feels a lot better yeah it feels a little bit more locked in on me when I fly with the kiss ultra fc and the fat tech 45 amp it's been awesome for me dji o3 air unit I have been flying the v2 vistas and the air unit old school air unit for a while nice but the o3 is just that the quality quality is man it's just peachy yeah and then uh what do we got here so my receiver I fly usually a flight tracer but on this rig I'm trying out elrs given that I try people have been telling me to give it a go so any issues with it yet not yeah and no fail saves or nothing so and the penetration has been nice so nice nothing at all yep um as far as props I fly I always fly the s3 props mango props uh hq props for me are the best hq hq baby team motor motors I fly uh f60 1750 kv props nice I love the 1750 kv I love that low kv gives me nice go resolution and all nice I'm still stuck with the old school session five so I do and everybody's been telling me to go I think session five is great if I could get them I'd be flying it's awesome yeah off for it off for it off for it but nice and then I see what the batteries I usually fly the 1300 gmb's he's been nice they like they have like a 175 gram weight to them oh for a 1300 yeah for 1300 for 600 that's really good so we got to rock the camera buddies you know and camera buddies are just mac tech is a man he makes the best stuff you know for sure but haven't tried that have you tried the camera butter oldies on the oh I've tried every I have all the camera butter products okay I am the biggest fan of camera butter and I say there's there's so amazing yeah I love them I'm rolling with the best so I'm gonna see I've seen you do a lot of these like really fast flips and stuff like in the same space what's your rates like my rates yeah my rates are a little higher than most 1100 1100 yeah yeah that's why my flip flop did you did you like start high and then go down to like what I could I started at that you started at that and then I just had to tweak my expo and everything else so what's your curve at is it like pretty linear no it's not linear at all so I got a pretty nice little curve so I'm at 2.24 my expo nice not bad so you got a good like little mushy like in the center and then you go at the end you know yeah yeah yeah and a high sensitivity so sometimes you'll see me like a little twitch it's just part of me or my nervousness so I'm gonna excited to see you rip the spot I bet we can we could probably power loop do it he could probably power loop do it right now with the momentum hold on there if you do it uh slow enough and smooth it out do it right now let's do it guys this spot is so good this is like totally my gym it's got all the stuff I kind of like it except for like it needs a good trippy something you know like a big hole what is this like team van over today love it isn't this the van over channel right it's pretty much I mean sometimes it feels I like my man over shirt yeah I love it I didn't come prepared what's up jean I'm now left to be in the shop because I didn't wear the shirt a few minutes later fly right anything like that dude never in my life like not in person exploring my mind right now just flew through james I know it's it's blowing my mind like how quickly you can go through something so tight that dvr has got to go in the episode that was sick everyone else is flying their five inch clouds out here um I didn't get my five inch clouds fixed in time so I decided to fly the vision 40 I'm gonna brag about this real quick just because everyone says that tiny whoops are only good for indoors and whatnot but this thing actually rips and you're going to see that in the footage right now so jean is here and I'm going to prank him I'm going to fly right into his uh like so many lights it's gonna I think it's cooler than this what's happening right now buddy I feel like I'm getting some really good clips I I'm feeling really good about what I'm getting maybe I'll watch it back and be like all that stuff we've been ripping here for a couple hours and honestly right when I started flying I was like oh I'm not feeling it but right now the lighting outside is beautiful you know the people left were finally got some good packs and I'm really feeling it james is flying right now like he's just in the flow look at him


Okay, so here you are standing in this train moving at 30 km per second to the right. You jump upwards, what happens? To make things easier, we'll draw some X and Y axes, okay? So just before the jump, what is your velocity in each of these directions? Pause the video now and see if you can have a guess, okay? So I'm standing in this train and the train is moving at 30 km per second. And since I'm staying in the same place relative to the train, I'm also moving to the right, at 30 km per second. I'm moving with the train. And so my overall velocity is represented by this arrow here, okay? What about just after the jump? So let's suppose my leg muscles are such that right after the jump, I'm moving upwards at 10 meters per second, okay? But what's my velocity in the X direction? Pause the video and see if you can guess. So just before the jump, I was moving with a velocity of 30 km per second in the X direction. And just after the jump, I still have that velocity. I'm still moving at 30 km per second. Because for that velocity to change, I'd need some kind of horizontal force to act on me, to slow me down. But that doesn't happen. I just jump upwards. So all that happens is I have a velocity of 10 meters per second added to my velocity of 30 km per second. So overall, my velocity is now diagonal. It has a 30 km per second component and a 10 m per second component. And so because of that, if this is the train and this is you, you will move with the train during the jump. And so from your point of view, you will land exactly where on the train you started.


All right. So welcome everybody to our community chat for Thursday. We are joined today by Council President Lynn Griezmer. Also a fellow neighbor. Hi, Lynn. Hi. And as well as your town manager Paul Bachman, my name's Brianna. Just want to remind everybody that this is being recorded. So please refrain from asking any, you know, personally identifying health questions or otherwise. If you'd like to ask a question, please use the Q and a feature within zoom or raise your hand from zoom. If you're on the phone, please press star nine to raise your hand. And we will acknowledge your question. So before we launch into questions, I will give Paul and Lynn a chance to kind of give us any updates they might have. Sure. So there's a lot going on and a lot coming up too. And so I want to talk about what's coming up first next week. You know, the Amherst college and the university probably will be starting to reveal more about what they are expecting to have happened on their campuses in the fall. They have sort of both have sort of said June 30th would be sort of a target date. I think they'll be some, you know, for the college there might be a little more flexibility in that date. But I think they're going to start talking about what it means to be open on the college campus come the fall and what that calendar, which we already sort of know will look like. I think it will have dramatic impacts on the town. So much to pay attention to there. The second thing is today the department of elementary and secondary education for the state came out with additional with the guidelines for reopening elementary schools in the fall. And I have not really gotten into it, but I know the superintendent has and lots of concerns, lots of review. A lot of discussion will happen on that topic over the coming weeks as they have a gargantuan task and trying to get the elementary schools open so that students can return safely so that parents and guardians can have someone take, you know, with their children so that they can get back to work safely. And also to be able to make sure the staff are able to return to work safely because that's the most critical point. That's that's where the education happens is between staff and students. Staff been doing a tremendous job, you know, remotely as we all know. So a couple of other things I wanted to mention, Puffer's pond has been open. We're managing it more aggressively this year aggressive in the sense that we have actual people there from 10 in the morning to six at night. And they're checking people in there, making sure the beach doesn't get too crowded. There's people information folks at the start of State Street. So it gives us a chance to educate people, let them know how we're going to how things are going to work before they park their cars. And then there's people greeting people at a tent as they enter Puffer's pond. And that's been working out pretty well actually and people appreciated those more rational approach to it. Oh, Lynn changed your background. That looks good. And the last thing I want to mention is that downtown is starting to bustle. We have put out picnic tables on bowl and walk. There are now sections of North Pleasant street that are carved out. In the street that we were putting seating in. On Amity street for Amherst coffee to expand. So there's lots of really good stuff happening downtown restaurants are open. So. Lots of things happening. So Lynn, do you want to provide an update or are you too busy with your backgrounds? No, I'm not. I'm not. I'm not. I'm not. You're on mute, Lynn. Sorry about that. I needed to change locations. Because we're having some work done outside and all you could hear was hammering. Oh, that's why you're walking. That's why I was walking. So I'll actually go back to my old background. But let me start by saying the council is extremely busy. We actually for the first time, except for two Monday holidays. We had a meeting last week on Monday, but in that instead of been meeting every Monday. In the beginning in March, we started meeting. We were using those meetings as somebody, you know, for the purposes of really hearing more about what the town's response was to COVID. And again, I want to just thank the town manager. And Julie and our first responders because they really have been on top of it from day one. So we've been able to see the town manager. So we've been able to see the town manager. And we've also set up a special website, which is still available. And so what now the, the responsibility. Before the council is to really try to see what we can do to support the economic development. And opening of the town. And, you know, we've done that with some special zoning. Legislation. That the town manager brought to us, and the town manager has put out. So that's going on. We're getting ready for budget. And it's budget, budget, budget. As many of you know, we passed a one 12th budget to just get us through the month of July. But on Monday, Paul will be introducing the. The rest of the FY 12, 21 budget. In other words, the full 12 month budget. And that will immediately be referred to the finance committee. And that will be in July, July 13th. And that will be twice a week. During most of the rest of July. And until we get ready and come back to the council for the budget, hopefully to be passed. Sometime around July 20th. And that includes a hearing on July 13th. That we will hopefully hear from all of you. And there will also be public comment at all of the finance committee meetings. We will also have a special meeting of the town council. And we will also have a special meeting of the town council. And we will also have a special meeting of the town council. And each meeting will focus on a very various pieces of. The budget as well. We also have just called a special meeting of the town council. The focus totally on the public safety, specifically police in light of all of the crises that have been going on regarding. Racism. And so what we're doing is to find out more about our own police practices. Our policies and the statistics. It is not to dismantle. It is not to disarm. It is to make sure we're well educated. So as the public asks for questions and brings concerns to us. We know what we're doing and we can look for opportunities. Whereas always everybody can improve. But we also want people to understand that we're not in the business of. Putting our police department aside. Calling a lawless society. So that's going on at this point too. So there's lots of things happening. We're getting ready to do the town manager's evaluation. Close your ears, Paul. And that includes soliciting public comments. So we hope you will do that. And then we'll be back with our next slide. And then we'll have a solicit comment from all committees and committee chairs. And those notices, I hope we'll go out Monday or Tuesday, or Wednesday of next week. And that's a process. We go through every summer. We're actually trying to move it up earlier into the year next year. And that's just a few of the highlights of what's going on. Lots and lots of things. With all four of our standing committees. Okay, great. We have some questions here already. And I know Lynn mentioned how busy the council was and talked about some of the. The items that are up in front of the council at the moment, but in general, can you go through some upcoming town council agenda items that people might want to pay attention to? Sure. First of all, the water and sewer rates have come to the council once they've been to the finance committee. They are coming back. They're coming back to the council. And if people want to do, make public comment, there will be a public comment period at the beginning of the council meeting. Well, not quite at the beginning, but toward the very beginning. The, there is a slight increase in both the water and sewer rates. However, we're still lower than many of the town surrounding us. And interestingly enough, part of that increase. Yes. So we're not only looking at students around using campuses, but also it's because people are being more conservative. And which is a sign of really looking at sustainability options. So it's, we can't be too critical of the fact that we have to do some changes. One of the issues that goes along with that, of course, is keeping our plants and our water sources healthy and available to all of us. And I think that's a really good point. And I think that the board is a very, very, and I do want to say so very slim. Capital budget. We're basically investing in sidewalks, a little bit in roads and putting some aside to reserve those things we know just can't be held off. For another year. The, the library has created a lot of opportunities in the city. We've already gotten a glimpse on the elementary schools, includes the library includes all of the town services. We've already gotten a glimpse on the elementary schools and also the regional schools. And we've gotten a glimpse on the library because those boards have passed those budgets. And sent them on to the town. So it's really our opportunity to look at all of it together. And come up with our best. Yes. budget. Great. We had a question that just came in from one of the attendees. Has the state provided any estimates of local aid, transportation, funding, school funding, et cetera, for fiscal year 2021? You must have been sitting on my shoulder when I asked Paul that question just yesterday. The answer is no. We don't expect to get any guidance until August if we're lucky, maybe September. I was reminded in an MMA meeting, Mass Municipal Association meeting a couple weeks ago, that there was one year that we went with 112th budgets all the way into November. Yeah, just to add to that, I wish we did, we don't. What did come from the state is that they said that we should expect payments on the same level of state aid that we had for FY20 for the first two months, meaning July and August for FY21. So they are saying level funding at this moment in time and constructing the budget that we are presenting to the town council on Monday, we have projected level funding of the state aid coming into the town that includes education and everything else. And if in the likelihood, and it is a strong likelihood that state aid actually is reduced, the council and the staff have all agreed that we will replenish that lost revenue from our free cash, which is our rainy day fund, which is what that's there for. And the fact that they said two months, it makes me think they're not close to doing a budget. The house hasn't even gotten through the budget yet and it has to go through the Senate and then it has to go through reconciliation and then the governor has to sign off on it too. So I think they're a long ways away from a budget. Another question here for Lynn, what is the council doing to address the national and local concerns about policing and racism? Thank you for that question. First of all, we actually have been having a variety of conversations. Every councilor is engaged in these conversations with their constituents. Two of our counselors specifically were invited by a group of residents to meet with the police chief and with Captain Ting. And in addition to that, about six or seven of us listened in as well to that meeting. That led to another meeting where three counselors went to a meeting of the Human Rights Commission and the Human Rights Commission has now taken on a responsibility working specifically with D. Shabazz and also Gazette Gaia to pull together an opportunity for a citizen's forum where they are reaching out, particularly to people who are not comfortable maybe speaking at a council meeting, understand their concerns and bring those back to the council. But meantime, what the council is doing is making sure we're better educated about the practices and policies of our police. And with great cooperation from the chief and his staff, we will be having a special meeting on the 6th of July at 630 that will focus totally on public safety with an emphasis on police and supporting services, including the way they work with the fire and AMS. All right. Great. I want to add that's just the beginning of the conversation. We don't see this as the end of the conversation. We see it as trying to assess where we are, make sure that before we make any moves, we actually understand what our police department does. Paul, do you have anything to add to that? Now, I think it's a conversation, I think, that has to happen at multiple places, multiple venues, multiple ways. Not everybody's comfortable in every forum. And I think a lot of people might feel it might be difficult for folks to come to a council meeting. And so I think that the more ways we have for people to interact with our police department and with everybody in the town government, the better off we are. And then quite honestly, you and I and others, our town staff at our last staff meeting, we talked about the work that we have to do as town staff. So I think while it's a moment, it's not a passing moment. It's something I'm really committed to having an engaged conversation and the sort of re-examination of how we do our work as town employees. In fact, Paul, you might want to give just a little preview on one item in your budget. Yeah, so we are trying to, you know, a lot of this work doesn't happen for free. And so we are finding money to make sure that there are resources available for us to move forward to engage people to help guide this work. Great. I got another budget question that came in the room. If the rainy day fund is also meant to support our large building projects, such as the school, DPW, et cetera, will you put a cap on withdrawals shifted to the operating budget? So, yeah, I mean, I think that we're, you know, having really tight communication with the council and with the finance committee and with our, you know, having, again, having Sonia Aldridge and Sean Mangato on the team and really good communication with the library and the schools, we're all going to be having these conversations with the budget coordinating group as we go down this road. There's so much uncertainty and I don't think we're going to say there's a cap because we just don't know what the future looks like, but I think we're all incredibly cognizant that we do not want to lose the opportunity to move forward on our major capital projects and that having those reserves is an important component of that. But the world has changed and we have other tools that we can use to manage our budget in addition to, you know, using reserves to fill the holes, basically. Yeah, and let me add to that as a counselor and also as a member of the finance committee. And that is in the guidelines that we've given the town revised from the original guidelines because of the change in times, you know, we've made it very clear. We're watching we this is not a keep using cap until, you know, keep using our funds until they're gone. It's at some point and we hope we can make it through the year with the black budget. But if we have to look at it in the mid year, it's always tougher. And that's what we're trying to avoid. But I we've never said there's a cap. But all of the council is committed to the major capital projects. Some of them may be delayed longer than others, although at this point, both options for the library and for the elementary school are still out there. And in fact, the elementary school is moving forward with the naming of a building committee. Great. I'm going to just take a quick chance to remind our attendees who have joined us live to use the Q&A function to ask your question or raise your hand and zoom so we can address your question. I also wanted to take a quick moment that will be. I know we're talking a lot about the budget in in July and early July. We'll be doing a kind of multi channel ask me anything with our finance director so that you can ask any and all your questions about the budget. And we'll have that up in many different platforms for people to send in their questions and get access to our finance director's answers in a kind of timely fashion. So there'll be more to come on that. OK, I'm really excited by that. I think, you know, Sean, I got our finance director and Brianna have worked on this to put out there for, you know, for hours and hours, they'll be available to ask ask me anything and they'll answer to you online. And I think that that is very brave to do that. And I think that it'll open up some opportunities for the public to ask those kind of questions that they might might not otherwise have the opportunity to ask. So we'll see if people respond to it. But it's a I'm really thrilled that they've taken that initiative. Yeah, and it should be it should be July 9th. We'll put out details, but leading up to that, if you have any suggestions of what platforms you use and like best so that we can also factor those in, feel free to email me at info at AmherstMA.gov with any suggestions. And when you talk about platforms, we've talked about Reddit, we've talked about Facebook, we've talked about Twitter, those are things that were when you say platforms. That's what you mean. Yes, that's what I mean. And I know in our community, a lot of folks are using Nextdoor or other different listservs or things like that. So we want to be sure we're reaching people where they are. We have a good sense of kind of the most popular ones, but we want to make sure everyone's included in the conversation. Even if it's just emailing us a question or sending us a letter with a question, a letter. Wow, that would be exciting. That would be really exciting. Mail US mail. We don't get much of that anymore. So we have we have about 10 minutes left. Oh, I see a question coming into the room. Is there is there a plan to physically open up town government meetings to the public? So at this point, we aren't opening our buildings to the public. We're getting prepared to open our buildings by appointment, which a lot what a lot of communities are doing. So there are two things that are taken into consideration. One is the production, the protection of our force, our employees. So we have brought our employees back under strict protocols about how we conduct ourselves when we're in this building up in Town Hall and Brianna's in Town Hall. So so and then and then we'll have strict protocols when people enter the building. And so the idea of opening and creating meeting spaces is just not where we are at this point in time. When you talk about a meeting, you're talking about a group of people in this community tends to be older people in a room for an extended period of time, sharing same space. Even if they're socially distanced, you're still sharing the same air. And that's the recipe for for viral spread. Our health director is really not in favor of it. We are abiding by the state's rules in terms of discouraging it by allowing smaller groups to get together with public meetings. You can't control how many people will show up once it's open. It's open. You know, you can have 10. Nobody show up or you can have 100 people show up. So one of the things that we've learned is that the Zoom platform is quite beneficial in people. A lot of people, a lot more people participate. And this added benefit that Lynn has mentioned is that every meeting is recorded every meeting. And so that has really expanded the way people can access the public bodies as they can do their do their work. I have a comment here or suggestion. Please invite the town clerk to a future chat. I am interested in the preparation for the fall's election. Wow, that's a really great suggestion. She's really actively working on that. There will be changes for the fall election. These changes will have to go to the council. And so we're looking at different alternatives for the fall because we have a September election and a November election. Both will be pretty competitive, I think, because we have a senator senatorial primary and the September election. And of course, the presidential election in November and how we do them socially distanced with all the proper protocols with a reduced election staff and being cognizant that many of our election locations are in schools is a big challenge for our relatively new town clerk, who's also our elections official. The good thing is that Chavina is an expert in elections and election law and knows this stuff backwards and forwards and has been working in this area. And so she has been she has a team that she's working with, which includes our fire chief, our superintendent, public works, our facilities manager and the facilities director for the school department. And they're all sort of scheming out different ways that we can serve the public and make that happen. But that's a really great idea. I appreciate that. OK, let's see. We have a few more minutes and so I just want to give a last call out to the to the folks in the room. Now's your chance. If you want to raise your hand and zoom or use the Q and A button within Zoom to put your question to our panelists. I don't see any hands or any questions. Is there anything that either of you didn't get asked that you might want to speak on now, Lynn? I I get so many emails and I made a commitment as president that I would answer all the emails that come to the town council as a body. And, you know, every once in a while, the emails start having a similar rhythm. And so I tend to use a similar answer or the same answer each time. But, you know, some of the emails that we get when I had recently, in fact, I just answered this morning, they were people who were looking for where were we, how were we communicating about both the covid pandemic and racism? And when I got done writing the response, I thought to myself, I probably should have published that list someplace because the council and the town staff have been enormously attentive to both of these issues. Covid early on and continuing the but though we don't do a special feature at each of the town council meetings like we did starting in March. There is a section in the town manager's report on covid every time he does a town manager's report, which is for every council meeting. And I mentioned earlier in the show the specific things that we're doing to kind of get the conversation going and toward any changes we may see making around public safety based on all of the race and the racist issues that have been going on. This this Monday, for example, we actually are passing a proclamation about Asians because with covid we've seen a lot of discrimination against the Asian population and people have been failing that. And so two residents and three councils are sponsoring that proclamation as well. So it's there's been a lot of activity. The council itself is a lot is really kind of back to normal. If we can call it that, it doesn't feel normal. But we're meeting a lot and and our meetings are really getting the business of the town moving forward again, which I think in the beginning in March, middle of March, we felt like we're all kind of a little stuck. And now that does not feel that way at all. So I had swing some things back to personal things for me. As one is, you know, we went out to Mission Cantina for dinner Saturday night. That was a blast that we sat outside all the good food, all the margaritas. And so as my father's day family type of event. So restaurants are opening up and sitting outside in this beautiful weather under a shade structure or a tent or an umbrella has been really great. We got a grant for ten thousand dollars that we're working with the bid on to make some more create more amenities on our outdoor eating establishments downtown. Yesterday, I've got my hair cut for the first time since covid started and went over to Matt's and not plugging one part of Barbara, but to say he had really good protocols in place and felt really comfortable there. I had to keep a mask on the entire time he kept a mask on the entire time. But, you know, listening to some of these businesses, they're going to have a hard time getting through. And their economies have changed so dramatically where their revenue is cut in half just because of the protocols they have to put in place, the PPE, they have to purchase the number of people who are hesitant to visit them. So I really worry about a lot of our businesses that are the ones that are going to survive, but they're open. They're trying to make a living. They're they're working their their butts off to make it happen. So kudos to the ones who are out there working. And I ask the people to go out and support them. All right. Well, I go ahead, Lynn. I just want to give a plug for the work that the chamber and the bid have been doing the extent to which the town has been working closely with them throughout all of this. Absolutely. All right. Well, I don't see any other hands or questions in the room and we're at 12 30. So I think we'll wrap it up here. We'll put this recording up shortly after and we will be back next Thursday at the same time. Same link and same phone number with a new guest. So I want to say thank you to Lynn for joining us today and also to Paul. Yep. Thank you. Thanks, everybody. Bye. Bye.


All right, now it's my very big pleasure to introduce Hanno Beck to you. He's no stranger to the Chaos crowd. He's been to several Easter Hacks and at several other Chaos events. Today he's here to talk about TLS 1.3, what it's all about, how it came to be and what the future of it is going to look like. Please give a huge applause and welcome Hanno. We have a new version since August, TLS 1.3. In truth, I'd like to go a bit into the history of why we have this new version, how we got there and what design decisions there were to make this new protocol version. So the very first version of SSL, which it was called back then, was released in 1995 by Netscape and it was quickly followed up with version 3, which is still very similar to the TLS 1.2 that we mostly use today. And then in 1999 it was kind of taken over from Netscape to the IETF, which is the Internet Standardization Organization, and they renamed it to TLS. And so that's kind of the history. We had SSL and I've marked it in red because these two versions are broken by design. You cannot really use them in a way that is secured these days because we know vulnerabilities that are part of the protocol. Then we had, in 1999 it was renamed to TLS and TLS is kind of still kind of okay if you do everything right, but that's really tricky. So it's kind of a dangerous protocol, but maybe not totally broken, same with TLS 1.1. TLS 1.2 is what we still mostly use today and TLS 1.3 is the new one. And what you can see here for example is that the biggest gap here is between 1.2 and 1.3. So it was a very long time where we had no new development here. Okay, you probably heard that we had plenty of vulnerabilities in TLS around TLS. And also these days good vulnerability always has a logo and a nice name. And I want to go into one vulnerability which doesn't have a logo. Not one of the variants. I was very surprised when I realized that. But that's so-called padding oracles. They are in CBC mode which is encryption we use for the actual data encryption, the symmetric data encryption. So the thing is when we encrypt data what we usually use are so-called block ciphers. And they encrypt one block of a specific size of data. It's usually 16 bytes. And this CBC mode was the common way to encrypt in past TLS versions. And this is roughly how it looks like. So we have some initialization vector which should be random, wasn't always, but that's another story. And then we encrypt a block of data and then we XOR that encryption into the next plain text and encrypt it again. Now one thing here is that because these are blocks of data and our data may not always be in 16 byte blocks, it may just be 5 bytes or whatever, we need to fill up that space. So we need some kind of padding. And in TLS what was done was that first of all we had some data. Then we added a MAC which is something that guarantees the correctness of the data, the authentication of the data. And then we pad it up to a block size and then we encrypt it. And this order of things turned out to be very problematic. So this padding is a very simple method. If we have 1 byte to fill up, we make a 0, 0. If we have 2 bytes to fill up, we make a 1, 1. 3 bytes, 2, 2, 2, 2, 2, 2, 2, and so on. So that's easy to understand, right? Now let's for a moment assume a situation where an attacker can manipulate data and can see whether the server receives a bad padding or whether it receives bad data where this MAC check goes wrong. And here is the decryption with CBC mode. And what an attacker can do here, so the first thing the attacker does is throws 1 block away at the end. It just blocks the transmission of that block and then he changes something here. So what we assume here is the attacker wants to know this decrypted byte because it may contain some interesting data. So what he can do is he can manipulate this byte with a guess. And the byte is only 256 ways, the values the byte can have. So he can guess enough times and XORs it with this value. And if you think about it, we XOR it here with the plain text. That means if we end up with a 0 here, then the padding is valid. If we end up with some garbage value here, then the padding is probably invalid. So by making enough guesses, the attacker can decrypt a byte here under the condition that he learns somehow whether the padding is valid or not. So he could decrypt one byte. But he can go on. Let's assume we learned that one byte. We have decrypted it.  So we XOR this byte on the right with the guess with what we already know that it is and with the one. And then we XOR this next byte with our guess and also a one. And if this ends up being one one, then again we have a valid padding. So the attacker learns the next byte. And he can do this for all the bytes. This was originally discovered in 2002 by Sergei Bruny. But it was kind of only theoretical. So one thing here is that TLS has these error messages. And there are different kinds of errors. And if you read up in the TLS 1.0 standard, if the padding is wrong, then you get this decryption failed error. And if the MAC is wrong, so the data has some modification, then you get this bad record MAC error. So you could say this would allow this padding oracle attack because there are these error messages. But the attacker cannot see them because they are encrypted. So this was kind of only a theoretical attack which didn't really work on a real TLS connection. But then there was a later paper which made this attack practical by measuring the timing difference from these different kinds of errors. And this allowed practical decryption of TLS traffic. Then in later versions of TLS this was fixed or kind of fixed. But there's a warning in the standard which says, so this is right from the standard text.  If you read something like that, it sounds maybe suspicious, maybe dangerous. And actually in 2013 there was the so-called Lucky 13 attack where a team of researchers actually managed to exploit that small timing side channel that the designers of the standard believed was not large enough to be exploitable. And it is in theory possible to implement TLS in a way that is safe from these timing attacks. But it adds a lot of complexity to the code. If you just look at when Lucky 13 was fixed it just made the code much longer and much harder to understand. Then there was another panning oracle which was called Poodle which was in the old version SSL 3. And this was kind of by design. So the protocol was built in a way that you could not avoid this panning oracle. Then it turned out that there was also kind of a TLS variation of this Poodle attack. And the reason here was that the only major change between SSL version 3 and TLS version 1 was that the panning was fixed to a specific value where in the past it could have any value. And it turned out that there were TLS implementations that were not checking that enabling this Poodle attack also in TLS. Then there was the so called Lucky Microseconds attack which was basically one of the people who has found the Lucky 13 attack looked at implementations and saw if they have fixed Lucky 13 properly and they looked at an S2N which is an SSL library from Amazon and they found okay they tried to make counter measures against this attack but these counter measures didn't really work and they had still a timing attack that they could perform. Then there was a bug in OpenSSL which was kind of funny because when OpenSSL tried to fix this Lucky 13 attack they introduced another panning oracle attack which was actually much easier to exploit. So yeah we had plenty of panning oracles but if you remember back what I said for the very first attack that this didn't really work in practice in TLS because these errors are encrypted. But theoretically you could imagine that someone creates an implementation that sends errors that are not encrypted. For example you can send a TCP error or just cut the connection or have any kind of different behavior because the whole attack just relies on the fact that you can distinguish these two kinds of errors. And yeah you can find implementations out there doing that. So yeah panning oracles are still an issue. Then I want to look at another attack which is so called Bleichenbacher attacks and they targeted the RSA encryption and that is kind of the asymmetric encryption which we use at the beginning of a connection to establish a shared key. This attack was found in 1998 by Daniel Bleichenbacher and if you look at the RSA encryption before we encrypt something with RSA we do some preparations and the way this is done in old TLS versions is the so called PKCS 11.5 standard and how this looks is it starts with 0002 then we have some random data which is just again a padding to fill up space. Then we have zero which marks the end of the padding and then we have a version number 0303 which stands for TLS 1.2. It's totally obvious right? I'll get to version numbers later and then we have the secret data. Now the but the relevant thing for this attack is mostly the 0002 at the beginning so we know each correct encrypted block if we decrypted it starts with 0002. So we may wonder if we implement a TLS server and it decrypts some data from the client and then it doesn't start with 0002 what shall it do? And the naive thing would be yeah of course we just send an error message because something is obviously wrong here. Now this turns out to be not such a good idea because if we do this we will tell the attacker something we will tell him that the decrypted data does not start with 0002. So the attacker learns something about the interval in which the decrypted data is either it starts with 0002 or it doesn't. And this is it turns out to be enough to if you send enough queries and modify the cipher text you can learn enough information to decrypt data. The whole algorithm is a bit more complicated but it's not that complicated it's relatively straightforward it's a bit of math and I didn't want to put on any formulas but yeah. Now as I said it was discovered in 1998 so TLS 1.0 introduced some counter measures and the general idea here is that if you decrypt something and it is wrong then you're supposed to replace it with a random value and use that random value as your secret and pretend nothing has happened and then continue and then the handshake will fail later on because you don't have the same key. This prevents the attacker from learning whether your data is valid or not. In 2003 a research team figured out that the counter measures how they were described in TLS 1.0 were incomplete and also not entirely it was not entirely clear how to implement them because there's this version thing and it was not exactly described how to handle that if only the version is wrong. So they were able to create an attack that still worked despite these counter measures. So more counter measures were proposed and in 2014 there was a paper that Java was still vulnerable to blind buffer attacks in a special way because they used some kind of decoding that raised an exception and the exception was long enough that you could measure the timing difference and there was also still a small issue in open SSL although that was not practically exploitable. In 2016 there was the so-called drown attack and the drown attack was a Bleichenbacher attack in SSL version 2. Now you may wonder SSL version 2 is this very, very old version from 1995. Is this a problem? But it actually is because you can use encrypted data from a modern TLS version TLS 1.2 and decrypt it with a server that still supports SSL version 2. So that was the drown attack and then last year I thought maybe someone should check if they are still servers vulnerable to these blind buffer attacks. So I wrote a small scan tool and started scanning and scanned the Alexa top 1 million. The first hit was Facebook com was vulnerable and it turned out from the top 100 pages roughly a third were vulnerable and in the end we found like 15 different implementations that are vulnerable. Probably more but these were the ones we know about. Yeah. And just I think a month ago there was another paper that you can use cache side channels which is mostly interesting if you have cloud infrastructure where multiple servers are running on the same hardware which you can also use to perform these Bleichenbacher attacks. Now what I want to show you here you cannot read this because it's too small but this is the chapters in the TLS data that describe the counter measures to these Bleichenbacher attacks. So we knew about them since before TLS 1.0 so there was a small chapter what you should do to prevent these attacks and then they figured out okay that's not enough we need to have more counter measures and even more. So what you can clearly see here it's getting more and more complicated to prevent these attacks. So with every new TLS version we had more complexity to prevent these Bleichenbacher attacks. These were just two examples. There were a lot more attacks on TLS 1.2 and earlier that were due to poor design choices. I've named a few here sloth which was against three caches, freak which kind of attacked issues in the handshake and compatibility with old versions, sweet 32 which attacks some block ciphers that have a small block size triple handshake which is a very complicated interaction of different handshakes. The general trend here was that in TLS 1.2 and earlier if there was a security bug, if there was a vulnerability in the cryptography, what people did was we need to work around for the security issue and then if this work around doesn't work, it's not sufficient, we need more work around and also we create more secure modes but we still keep the old ones and then people can choose. We have this algorithm agility. You can choose, there's the secure algorithm, there's a less secure algorithm, take whatever you want. Which in practice meant very often still the insecure modes were used because like for all of these things, there were modes available in TLS 1.2 that didn't have these vulnerabilities but they were optional. But I think that is the major change that came with TLS 1.3 was a mindset change that people said okay, if something has vulnerabilities, if it's insecure and if we have something better, then we just remove the thing that is vulnerable, that is problematic. So the main change in TLS 1.3 was that a lot of things were deprecated. So we no longer have these CVCIL modes. We no longer have RC4, which is another cypher which was problematic. We no longer have triple desks which has these small block sizes. We still use GCM but we no longer use it with an explicit non-switch also turned out to be problematic. We completely remove RSA encryption. We still use RSA but only for signatures. We remove hash functions that turned out to be insecure. We removed Diffie-Hulman with custom parameters which turned out to be very problematic and we removed elliptic curves that kind of looked not so secure. But also there was something that some academics looked at TLS with the more scientific view. They tried to formally understand the security protocol, properties of this protocol and to analyze and to see if they can prove some kind of security properties of the protocol. And many vulnerabilities that I mentioned earlier were found by these researchers trying to formally analyze the protocol. But also these analysis have contributed to design TLS 1.3 to make it more robust to attacks. So this is I think also a big change. There was a much better collaboration between scientists who were looking at the protocol and the people who were actually writing the protocol. But you may say all the security is nice but what we really care about or maybe some people really care about is speed. We want our internet to be fast. We want to open our browser and immediately get the page loaded. And TLS 1.3 also brings improved speed and I'm showing here the handshake and this is very simplified. I've kind of only added the things that matter to make this point but if you look on the left if we do a handshake with an old TLS version it starts that this client sends a client hello and some information what version it supports what encryption modes it supports then the server sends back which encryption modes it wants to use and the key exchange. And then the client sends his part of the key exchange and the so-called finished message and then the server sends a finished message and then the client can start sending data. In TLS 1.3 we have compressed this all a bit. The client sends his client hello and immediately sends the key exchange message. And then the server answers with his key exchange message and a few more things that I left out for simplicity but the important thing is that with the second message the client can already send data. And this is the situation for a fresh handshake like we have not communicated before I want to make a new connection to a server and it goes one time back and forth and then I can send data which and in the earlier version I had two times back and forth. So I can send data much faster. So yeah we remove one round trip from a fresh handshake. There's also security improvements to this handshake so this is nice we have more security and more speed. And particularly we have better security on so-called session resumption which means we're reconnecting using a key from a previous section. And we also protect more data which may avoid some attacks where an attacker may fiddle with the handshake. These were more or less theoretic attacks but these are also prevented in TLS 1.3. So TLS has a more secure and a faster handshake and if you want to have more details about this handshake there was a talk two years ago at this congress which goes into this in much more detail so if this particularly interests you you should watch that talk. I've put a link here and I will put the slides online so there's also something called a zero round trip handshake and this is even faster we can send data right away. Now how can we do that? This is kind of cheating because what we need here is we need to have a previous connection and then we have a key from a previous connection can create a new key from that and use that to send data right away. So yeah we need a so-called pre-shared key which we have from previous connection and then we can send data without any round ships. So even more speeds that's nice right. But this zero RTT mode does not come for free. There is a problem here with so-called replay attacks which means an attacker could record the data that we're sending and then send it again and the server may think okay now this request came twice so I'm doing twice what this request was supposed to do. So there's some caveats with zero RTT and the standard says yeah you should only use if it's safe it says something like you should only use it if you have a profile how to use it safely. Now what does that mean? Let's look at HDTPS which is the protocol we're using usually. If you look into the HDTPS standard it says something that a GET request has to be idempotent and a POST request does not have to be idempotent. Now what does that mean? It more or less means if you send a request twice it shouldn't do anything different from just sending it once. So in theory we could say yeah GET requests are idempotent that means they are safe for zero round trip connections. The question is do web developer, sorry, you can do a little experiment if you meet someone who's a web developer ask them if they know what idempotent means and when they can use idempotent requests and when they cannot. So in an ideal situation where web developers do know that we can use zero RTT safely with TLS 1.3. Zero RTT also does not have as strong forward secrecy as a normal handshake so there's kind of a trade off here because this pre-shared key is encrypted with a key on the server and if that key gets compromised that might compromise our connection even if the key is only leaked later on. So this looks a bit problematic and many speculate that the future attacks we'll see on TLS 1.3 that at least some of them will focus on the zero RTT mode because it looks like one of the more fragile parts of the protocol but it gives us more speed so people want it to have it. Maybe the good news is this is entirely optional we don't have to use it and if we think this looks too problematic we can switch it off. So if it turns out that there are too many attacks involving zero RTT mode we could disable it again and use it without it. It will still be faster but not as fast as it could be with this. Yeah. Okay. Deployment. Now if we have this nice new protocol we not only have to make sure it's secure and fast and everything but we also have to deploy it and we have to deploy it on the internet. On the real internet like the one we have out there not some theoretical internet where there are no bugs and everyone knows how to implement protocols but the real internet with lots of IoT devices and enterprise firewalls and all these kinds of things. And now I want to get back to this version number. This may sound like a trivial thing but TLS 1.3 has a new version number for the protocol version. Here's a wire shark dump from a TLS 1.3 handshake. And if you're trying to look for the version number you will find multiple version numbers. And in case you cannot see it I have made it a bit larger. So at the top you see version TLS 1.0 encoded as 0301. Okay that looks strange. Then a few lines later you have a version TLS 1.2 0303. But we thought this was TLS 1.3. I mean it says here at the top but somehow there are these other versions. And then if you scroll further down you will see extension supported versions and then here it lists TLS 1.3 which is encoded as 0304. So what's going on here? This looks strange. So the first thing to realize is why do we encode these versions in such a strange way? Why are we not using a 1.0 for TLS 1.0? TLS 1.0 came after SSL version 3 which kind of makes it version 3.1. And that's how we encode it. Like TLS 1.0 is really just SSL version 3.1. TLS 1.1 is SSL version 3.2 and so on. And for TLS 1.3 it's complicated. So the very first version you saw earlier in this wire shark dump was the so called record layer and this is kind of a protocol inside the TLS protocol which has its own version number which is totally meaningless but it's just there. And it turned out for compatibility reasons it's best to just let this on the version of TLS 1.0 and then we have the least problems. And this record layer protocol is kind of the encoding of the TLS packages. Now if we have a new TLS version we cannot just tell everyone tomorrow we will use TLS 1.3 and everyone has to update because we know many people won't and so we somehow need to be able to deploy this new version and still be compatible with devices that only speak the old version. So let's assume we have a client that supports TLS 1.0 and we have a server that only supports TLS 1.0. How does that work? There's an extremely complicated mechanism here. So the client connects and says yeah hello I speak TLS 1.2. Server says okay I don't know TLS 1.2 but what's the highest version I support it's TLS 1.0 so he sent that back. And then they can speak TLS 1.0 and in case the client still supports that and we have a connection. This is very simple I would think so. So to illustrate how you would program something like that you would say yeah if client max version is smaller than server max version then we use the client max version otherwise we use the server max version. So you would think that there's no way anyone could possibly not get that right right I mean it's very simple. But I was saying earlier we were talking about the real internet so and on the real internet we have enterprise products. In case you don't know that an enterprise product is something that's very expensive and it's buggy. So yeah we will have web pages that run with firewall from Cisco or we will have people using IBM Domino web server and all these kind of things. And this is the TLS version negotiation in the enterprise edition. So a client says yeah I want to connect with TLS 1.2 and the server says oh I don't support this very new version it's from 2008 I mean that's 10 years in enterprise years it's very long. So yeah so the server just sends an error if the client connects with the TLS version that it doesn't know. It doesn't implement this version negotiation correctly. And this is called version intolerance and this has happened every time there was a new TLS version. Every time we have devices that had this problem if you try to connect with the new TLS version they would just fail they would send an error or they would just cut the connection or have a time out or crash.  So browsers needed to handle this somehow. So what the browsers did is okay we try it with the latest TLS version we support and if we get an error we try it again with one version lower and again one version lower and eventually we may succeed to connect. So here we have a browser and we have an enterprise server that supports TLS 1.0 and we will eventually get a connection. Now do you remember Poodle I mentioned earlier there was this padding oracle in SSL version 3 which was discovered in 2014. So you may wonder SSL version 3 which is from 1996 so that's really old. Who uses that in 2014? It was deprecated for 16 years I mean who uses that? Okay Windows Phone 7 used it but on these Nokia phones they also never got an update but okay but like normal browsers and servers at least used TLS 1.0 I mean they maybe didn't use TLS 1.2 but they used TLS 1.0 but we have these browsers that are trying to reconnect if there's an error and so what an attacker could do is that the attacker wants to exploit SSL version 3 so he just blocks all connections with the newer TLS version and therefore forces the client to go into SSL version 3 and then he can exploit this attack that only works on SSL version 3. So browsers say okay these downgrades are causing security issues what do we do now? We could add another workaround so there was a standard called SDSV which basically gives the server a way to tell the client that it's not broken. Like it says hey I have this special extension or it is a kind of special cypher suite which tells the client hey if you did these strange downgrades here please don't do that I'm a well behaving server. So yeah we had a workaround for broken servers and then we needed another workaround for the security issues caused by those workarounds but at some points even enterprise servers mostly had fixed these version intolerance issues and browsers stopped doing these downgrades so attacks like Poodle no longer worked. Have I just said they fixed it? No of course they have not fixed it I mean they fixed it for TLS 1.2 but of course they did not fix it for future TLS versions because they were not around yet so with TLS 1.3 we would get version intolerance again and breaking servers and would have to introduce downgrades again and all the nice security would not be very helpful. So the TLS working group realized that and redesigned the handshake and it was redesigned in a way that the old version feels still set that we're connecting with TLS 1.2 and then we introduced an extension supported versions which signals the support for all the TLS versions we can speak and which signals support for TLS 1.3 and possibly for future versions. Now at this point you may wonder if we'll have version intolerance with this new extension once TLS 1.4 gets out because the server may be implemented that it sends an error if it sees an unknown version in this new version extension and David Benjamin from Google thought about this and said yeah we have to do something about that we have to improve the future compatibility for future TLS versions and he invented this grease mechanism and the idea here is okay a server should just ignore unknown versions in this extension he gets a list of TLS versions and if there's one in there that he doesn't know about he should just ignore it and then connect with one of the versions he knows about. So we could kind of try to train servers to actually do that and the idea here is we're just sending random bogus TLS versions that are reserved values that will never be used for a real TLS version but we can just randomly add them to this extension in order to make sure that if a server implements this incorrectly they will hopefully recognize that early because there will be connection failures with normal browsers. So the hope here is if enterprise vendors will implement a broken version negotiation they will hopefully notice that before they ship the product and then it can no longer be updated because that's how the internet works. Okay so we have this new version negotiation mechanism we no longer need these downgrades and we have this grease mechanism to make it future proof so now we can ship TLS 1.3 right. Then there was this middle box issue so sorry that's the wrong year it must be 2016 sorry in 2016 in summer TLS 1.3 was almost finished but then it took almost another year till it got sorry I mixed up the years now that's no it's correct so in 2017 the TLS 1.3 was almost finished but it took till 2018 till it was actually finished and the reason for that was that when browser vendors implemented a draft version of TLS 1.3 they noticed a lot of connection failures and the reason for these connection failures turned out were devices that were trying to analyze the traffic and trying to be smart and they thought okay this is something that looks very strange it doesn't look like a TLS package how we're used to it so let's just drop it yeah. So yeah this is a strange TLS package I don't know what to do with this I'll drop it. These were largely passive middle boxes so we're not talking about things like man in the middle devices that are intercepting a TLS connection but just something like a router where you would expect it just forwards traffic but it tries to be smart it tries to do advanced security enterprise I don't know and they were dropping traffic that looked like TLS 1.3 and then the browser vendors proposed some changes to a TLS 1.3 so it looks more like TLS 1.2 and the main thing was they introduced some bogus messages from TLS 1.2 that were just supposed to be ignored so one such message is the so-called change cypher spec message in TLS 1.2 which originally didn't exist in 1.3 due to this new handshake design and this message in 1.2 it signals that everything from now on is encrypted so the idea was okay if we send a bogus change cypher spec message early in the handshake and then maybe this will confuse those devices thinking everything after that is encrypted and they cannot analyze it so yeah and it turned out this worked a lot of this reduced the connection failures a lot so and there was a few other things and then eventually the failure rates got low enough that browser thought okay now we can deploy this. There were a few more issues this is a PIXMA printer from Canon these things have an HTTPS server they have network support and we have to talk about these people here so if you remember the Snowden relations one of the things that got highlighted there was that there's a random number generator called dual EC DRBG and that has a vector and basically these days everyone believes this is a vector by the NSA and they have some secret keys so they can predict what random values this random number generator will output and also what was in the Snowden documents was that at some point the NSA offered 10 million dollars to RSA security so they implement this random number generator and then there's a there was a proposal a draft for a TLS extension called extended random that adds some extra random numbers to the TLS handshake why it wasn't really clear like it was just yeah we can do this it was just a proposal I mean every one can write a proposal for a new extension it was never finalized but it was out there and in 2014 a research team looked closer at this dual EC random number generator and figured out that if you use this extended random extension then it's much easier to exploit this vector in this random number generator and coincidentally RSA's TLS library BeSafe also contained support for that extension but it was switched off so and they didn't find any implementations that actually used it so it was sort of okay this was no big deal right but actually it seems these these cannon printers they had enabled this extension and they they used this RSA BeSafe library and enabled this extended random extension which was only a draft and so as extended random was only a draft it had no official extension number so such a TLS extension has a number so that the server knows what kind of extension this is and for this implementation they just used the next available number and it turned out that this number collided with one of the mandatory extensions that TLS 1.3 introduced so so these these cannon printers could not interpret that new extension they thought this is this extended random and it didn't make any sense and so you had connection failures yeah eventually so they the then the in the TLS protocol they just gave this extension a new number and then this no longer happened yeah there were many more such issues and they continue to show up for example recently from Java which is like also very popular in enterprise environments it now ships with the TLS 1.3 support but it doesn't really work so you have connection failures there yeah now with all these deployment issues what about future TLS versions will we have all that again and we have this grease mechanism and it helps a bit like it prevents these tolerance issues but it doesn't prevent these more complicated middle box issues there was a proposal from David Benjamin from Google who said yeah maybe we should just every few months like every two or three months ship a new temporary TLS version which we will use for three months and then we will deprecate it again just constantly change the protocol so that the internet gets used to the fact that new protocols get introduced my prediction here is that these deployment issues are going to get worse I mean we know now that they exist and we kind of have some ideas how to prevent them but if you go to enterprise security conferences you will know that the latest trend in enterprise security is this thing called artificial intelligence we use machine learning and fancy algorithms to detect bad stuff and that worries me and here's a blog post from Cisco where they want to use machine learning to detect bad TLS traffic because they see all this traffic is encrypted and we can no longer analyze it we don't know if malware is in there so let's use some machine learning it will detect bad traffic so what I'm very worried that will happen here is that the next generation of TLS deployment issues will be AI supported TLS intolerance issues and it may be much harder to fix and analyze speaking of enterprise environments one of the very early changes in TLS 1.3 was that it removed the RSA encryption handshake one reason was that it doesn't have forward secrecy the other was these all these Bleichenbacher attacks that I talked about earlier and then they came and emailed to the TLS working group from the banking industry and I quote I recently learned of a proposed change that would affect many of my organization's member institutions the deprecation of the RSA key exchange deprecation of the RSA key exchange in TLS 1.3 will cause significant problems for financial institutions almost all of whom are running TLS internally and have significant security critical investments in out of band TLS decryption what it basically means is they are using TLS for some connection they have some some device in the middle that is decrypting the traffic and analyzing it somehow which if they do it internally it's okay but this no longer works with TLS 1.3 because we always negotiate a new key for each connection and it's no longer possible to have this static decryption there was an answer from Kenny Patterson is a professor from London said my view concerning your request no rational we're trying to build a more secure internet you're a bit late to the party we're metaphorically speaking at the stage of emptying the ashtrays and hunting for not quite empty beer cans more exactly where draft 15 and RSA key transport disappeared from the spec almost about a dozen drafts ago I know the banking industry is usually a bit slow off the mark but this takes a bit okay there were proposals then to add a visibility mode to TRS 1.3 which would in another way allow these connections that could be passively observed and decrypted but they were all rejected and the general opinion in the TLS working group what that the goal of monitoring traffic content is just fundamentally not the goal of TLS the goal of TLS is to have an encrypted channel that no one else can read the industry eventually went to Etsy which is the European technology standardization organization and they recently published something called enterprise TLS which modifies TLS 1.3 in a way that it would allow these decryptions the ITF protested against that and primarily because of the they use the name TLS because it sounds like this is some addition to TLS or something and apparently Etsy has previously promised to them that they would not use the name TLS and then they named it enterprise TLS okay but yeah yeah TLS 1.3 is finished you can start using it you should update your servers so that they use it your browser probably already supports it yeah so in summary TLS 1.3 duplicates many insecure constructions it's faster and deploying new things on the internet is a mess so yeah yeah that's it and I think we have a few minutes for questions all right yeah as Hano management we have like six minutes or so for questions we have five microphones in the room so if you want to ask a question hurry up to one of the microphones and please make sure to ask a short concise question so we can get as many in as we possibly can maybe you just go ahead over there at mic too the question is if there's a way to prevent the use of that enterprise TLS yes there is because the basic idea is that they will use a static Diffie Herman key exchange and if you just connect twice and see that they are using the same again then you might reject that although the problem is some servers may also use it for optimization so there are longer discussions on this question so yeah I cannot fully answer it but there are more or less there are options all right before we go to the next question a quick request for all the people leaving the room please do so as quietly as possible so we can finish this Q&A in peace and don't have all these noise going on mic 3 please hi I was wondering about the replay attacks why didn't they implement something like sequence numbers into the TLS protocol there is something like that in there the problem is you sometimes have a situation where you have multiple TLS termination points for example if you have a CDN network that is internationally distributed and you may not be able to keep state across all of them all right then let's take a question from our viewers in the internet the signal angel please binary strike asks with regards to TLS more than 3 in the enterprise shouldn't we move away from perimeter interception devices towards putting the controls on the endpoint like we would have a zero stress just in so in my opinion yes but there are many people in the enterprise security industry who think that this is not feasible but I mean discussion about network design that would be a whole other talk all right then let's take a question from mic 4 please yeah it's also related to the enterprise TLS the browser can connect to an enterprise TLS server without any problems yeah so it's built that it's compatible with the existing TLS protocol thanks thanks and the reason like whether you can avoid that or not that's really a more complicated discussion that would kind of be a whole sub talk so I cannot answer this in a minute but come to me later if you're interested in details all right then let's take another question from the interwebs I mean that that's what I said what is done that's actually what browsers are doing and I think this is a good idea I just think that this only covers a small fraction of these deployment issues okay we still have plenty of time so let's go to mic 2 please yeah as you said we have still a lot of dirty work around concerning TLS 1.3 and all the implementations in the browsers and so on is there a way to make like a requirement for the TLS 1.3 or 1.4 compliance to meet some compliance to the standard so you have like a test you can perform a self-test or something like that and if you pass that you are allowed to use the TLS 1.3 logo or 1.4 logo you can do that in theory the problem is you you don't really want to have a certification regime that people like have to ask for a logo to be able to be allowed to implement TLS and that's kind of one of the downsides of the open architecture of the internet right we allow everyone to put devices on the internet so we kind of have to live with that and there's no TLS police so we kind of have no way of preventing people to use broken TLS implementations even and I mean people won't care if they have a logo for it or not right all right let's go to mic 5 all the way in the back there okay I have a question about Shor's algorithm and TLS 1.3 because since quantum computing is getting very popular lately and there are a lot of improvement in the industries so what's the current situation regarding TLS 1.3 and all those quantum based algorithm break the complexity into polynomial times yeah there's no major change here so with TLS 1.3 you still are using algorithms that can be broken with quantum computers if you have a quantum computer which currently you don't but you may have in the future there is work done on standardizing future algorithms that are safe from quantum attacks but that's kind of in an early stage and there was an experiment by Google to introduce a quantum safe handshake but they only ran it for a few months and but I think we will see extensions within the next few years that will introduce quantum safe algorithms but right now there's no change from TLS 1.2 to 1.3 both are can be attacked with quantum computers okay so I think we are getting to our last or second to last question so let's go to Mike 3 I think you've been waiting the longest okay in all the versions of TLS there was a problem for smaller devices such as IOT and industrial devices has there been a change in 1.3 to allow them to participate I mean I'm not sure what entirely you mean with the problem I mean TLS needs some the performance issues of TLS have usually been overstated so even in a relatively low-powered device you can implement the crypto the I mean the the whole protocol is relatively complex and you need to implement it somehow but I don't think that such a big issue anymore because even IOT devices have relatively powerful processors these days okay all right that concludes our Q&A unfortunately we are out of time so please give a huge round of applause for this great talk