What's going on, everyone? Sam here, late in sports cards. We're up in 2020-21. Pretty prism basketball, multi-sello, or multi-packed solo for box break number 31, random team style. There's a look again at your random results. As always, you can find these on the website under the results tab, as well as the link that's in the chat. So good luck here, everybody. Let's do it again. 14 to go on 10 box Tuesday basketball. The only group break tonight, still with spots remaining. Donnie dropped me that link once he stopped picking his nose over there. Come on. I don't even tell me that's what the situation's going to be here. Oh my god. Okay, never mind. I thought they were all like fused to the outside pack with the inner packs, but I don't think so. I'm just going to the first one. 14 to go on that one again, guys. There is a box of 21-22. I'm going to get that four up there, legal. Touching isn't planning right now. I'm giving myself a COVID test, honestly. No, but anyway, back to seriousness. There's a box of 21-22 NT basketball, 2020-21 iMac, and 2012-13 iMac. So a lot of big really not a lot of undesirable teams in that. A ton of stuff in there, a bunch of different years, which is really cool. So definitely check that out if you like your high-end basketball breaks. All the base can be stuck together now, isn't it? Kira Lewis Jr. Silver, Green Clay, Green Killian Hayes. There's a little mellow rookie, nice. Rubio, Tyrell Terry. Silver Van Vleet, Green Timmy Duncan. Base. Oh yeah, it's been probably a couple months since we've done one of these. Yeah, we don't, I mean, we got a decent amount of it still left. It's like a case in three-quarters, but yeah, we'll slowly keep doing them. Silver Cody Zeller, Green Mlbamba, Miles Ramsey. That's really got you abused. That was good. That was like probably the funniest thing that the legals ever said. Joshua, I already am, so I mean, we're ready there. Alex Caruso, Green Yolkich, nice one there. What's up, Richard? How you doing, buddy? I was going to say, yeah, Richard hit a Black Finite DAC out of Prism. Oh, nice. Green Onyeka Okangwu, big double up. Tyrell Maladon, James Johnson. He's lucky. Danucci went to XFL, otherwise, you know. Oh yeah, it'd be a real competition. Competition. Ben Nanucci. All Danucci did was Josh Gordon and that Pearson guy. Yeah, true. It's all I needed. Silver Zion. Very true. Always a good day when a one-on-one comes. Again, guys, just 14 to go on 10 Box Tuesday. Last group break we need to fill up tonight, so check that out for sure. It's going to be a fun one. Silver or Peyton Prichard, Green Devante Graham, Denny Biaf. It's the last basketball break of the night, as you know it usually is. And guys, we will finish behind tonight. Do apologize. Silver Lebron tribute, nice one there. Renato Porter. I do apologize, Embiid. I have a lot of technical difficulties, Devon Vaselle Rookie. A lot of technical difficulties on Shopify's side, so it's been tough for people to get on the site. And he had some breaks to sell out as well. Sam doesn't like technology, so I don't like him. Someday I do not. I don't know what I did to two technology, but Silver Xavier Tillman Rookie, Green Gary Harris. He's going to be the first one the robots come from when they take off. Ah dude, I'm always saying what's up to Nightbot. Nightbot. Or Stream Elements. Stream Elements will have my back. They think it's sarcasm, they don't know that. They know it's sincere. Patrick Williams. Let's go, Sandro. Mama Clushabilly. Remember the first time we opened, I was top-loading for Kenzie when we opened Revolution, where Sandro's first, there's Chris Dunn-Silver. Siddiq Bay Green, nice one there. Lana Hawks. I don't know if we're talking about the mirrors yet. A little bit of both. I was top-loading for Revolution when it first came out. That was Sandro Mama Clushabilly's first card. And Kenzie's like, I'm just going to call this guy Philly. But yeah, that's probably good. All right, who's, give me the starting lineup for the Spurs. Green Kuzma, Hampton, and 8-0 Stoppin, Obi-Toppin. Random Sandro, Bates Chop. Is that not Romeo Langford, right? Or is that Romeo Langford that's also starting? Kita Bates Chop. Ruth Cameron Thomas. Spurs Legend Cameron Thomas. Yeah. We're going to do the only rookie card. Romeo Langford, wow. Celtic Legend, Indiana Hoosier Legend, Romeo Langford. Oh, here's part of the Derek White trade, so that makes sense. There, right? There's an Ant-Man, nice one there for the Tipper Wolves on the red, white, and blue. Drop you guys this link again. 14-2-go. Pulled a Donnie there. Just typing in V. Oh, come on, and the link didn't go through. Geez, man, a rough guy here.   There's Patrick Williams. I did just get jingled. I got big time jingled by the... You jingled yourself. What's up, Jonathan? What's up, Jonathan? Jalen Stix Smith, Malachi Flint, LeBron Tribute, Yannis, and the most underrated guy in this clash, Jaden McDaniels, for sure. That's our guy? No, he's actually most underrated. I wholeheartedly believe that. I think... Vaughn, do you agree? Yes, no, on Jaden McDaniels being the most underrated guy from this class, Rodney Hood on the error card. Or at least there's that you can see an argument there to be made there. And base. All right, box number two. He's really, he is really good. Does he play a different position on his words, Yeah, he's like, he's a forward. I don't know, actually. Jaden McDaniels on the Timberwolves. Yeah, he's like a 3 and D wing. Really good defender. Really good defender. That's why he's underrated. He's not flashy. Yeah. Well, let's go. Got the brew crew stash. Yeah, it is really cool. The red Hedbert Brez is awesome. Let's go, Jonathan. UW alum. 13 to go now. We took a spot. Who's getting thanked? Adam K. Thanks, Adam. And guys, everything is going to be behind tonight. Just going to keep saying that. So there's no surprises. Everything will be slightly behind tonight. Probably will not finish group breaks till about one. Then we will do as many personals as we could fit as well. Appreciate you, Adam. Green Kasha Stanley. Robert Woodard base.  Yeah, uh, no. That's what we were making that joke. They were like, yeah, we'll just see Forrest in the morning. Lebron tribute for the Lakers for RJ Barrett, Matthew Delvedova, Zeke Najee. Late in after dark with Donnie. Get me as far away from that as possible. If you just want to stream where I'm just sleeping, then. Green Elijah Hughes. Oh, God. Which we can't be weird. So. Killian Hayes. Probably just going to kill that idea. And that before it gets escalated. Yeah. Oh, how bad can it go, Joshua? Do you really need to ask that question? At some point I'd probably lose my filter and I'd probably get fired. So. Same. Tigers, Halliburton, Green. Nice one there. Tray Jones. Oh yeah, I see that all the time on like TikTok. People always do that. Doing ASMR. Donnie does that on his own Twitch stream. Yeah, I was going to have a microphone right next to a gaming controller and I'll play a game while you're there. There you go. Frank.  You just got jingled. That's all right. You jingled yourself. I did. I did jingle myself earlier. That's legit jingling. So. Yeah, I'm shooting. Fudge won't get you fired. Grant Railer, Nick Richards. I'm going to mess up one of those words and it's probably the latter. Yeah. Manual quickly. Who was it? Ah, thanks. Was it a Stuart? Okamado? Or Okamado? Probably. Pan's good, dude. Silver Onyaka Akangu, big double O. Desmond Bain rookie. Four of the Grids. Oh yeah, 100%. Pitching is the issue. Silver Sidique Bay. He can break so far. What's wrong with Freeland? He's not even giving up. He should not even be on it. Like if we had all of our, if like, so say every single one of the best players at the position played, Kyle Freeland would probably be like the 100th guy on the roster, on the pitching roster. He's not bad. He's just not like that good. Who is he playing for? Matthew Sidique Bay. Is he Rockies, I think? Sidique Bay? Where's Kyle Freeland? He's not. Is he on the Rockies or like, am I thinking the Ranger? He's not going to be on the Ranger. Of course. Obi Toppin. Where's Ohtani? Yeah. I'm the only guy I know in this game with Ohtani. You don't know Mike Trout. Why don't you? I'm not excited for Trout. Silver, Dylan Brooks, Green, Jared Jackson, Brandon Carey, Cole Anthony. Still the Rockies, gotcha. All right. Red, white, and blues now. Could be about halfway through after this. Josh Green rookie. Jordan Noir. Down to 12 to go, guys. 12 on 10 box Tuesday. Let's go. Thank you so much. That's awesome. Manual quickly. Beef stew. Drop you guys that link. Thank you, Donnie. There it grows. D-Rose. Notice how I didn't put an equal sign next to the H. True. Very true. Just put down. Down to D. Yeah. Malachi Flynn rookie for the Raptors. Nick Richards. He was jealous. You can't hit a J from penalty. It's Kenyon Martin Jr. Rockets on the rookie. A lot of rookies in this. Not bad. Trey Jumps. Oh, Trout's going up. Go, baby. I don't know if there are any bets. That's rookie bets. That's a really good one. Like, that needs to produce a run right there. What if it doesn't? No, it's going to be a pit. It's a waste, then. It's a waste if it doesn't produce a run. Really self-produce a run. Definitely should. I guess my thing with baseball is I feel like it's just all locked if it gets to be a home run or not. Not really.  Very difficult to do. I mean, they make it seem like it's pretty easy. Donnie, it's not. I'm just saying. I know. I couldn't do it, but they seem to be, yeah. True. It's probably going to pay millions. Nice. Silver Antman. Nice one there for the Timberwolves. Got a red, white, and blue, and a silver now. The base. Green Precious Achooa. The Wrong Hornets. Silver Jada McDaniels. Nice one there. Timberwolves having a good break here. Woodard. Green Devon Vaselle. Harris Maxi Rookie. Obi-Toppin Rookie. There's Achooa Rookie. Jalen Sticks Smith. Silver Rookie for the Suns. A bunch of base there. Jahn Manion. Tyler Hero.  Ooh, Rookie got out. They're challenging it. Are they? That's good. They overturn that. Silver J-J-Varela. There's a Lamello Rookie. Nice one there. Warrant's Ricky Rubio. A mile. What terrible one. I know. Boo. Boo. Hiss. Hiss? Yeah. It's Ramsey DeMarco. Yeah, that's safe by a mile. For sure. Good challenge. Good challenge, US. Good challenge. Vaselle Rookie. Torrey Giles, man. What a sad story that is. He's like the number one recruit in high school. He went to Duke. He's supposed to be like the guy. Torrey Laceo. He's never really the same. There's a manual quickly. Instant impact. He didn't play in college, I don't think, and still got drafted in the first round. But just went to the Kings. They can't develop anybody. I'm not going to say that now. They can now. They used to not be able to develop anyone. In the Harry Giles years, they were not known for developing players. There's Tyrell Terry Rookie. The maps. I think that's a relatively fair assessment to make too. Let's go fishing. Let's go fishing, baby. My, it's Ramsey. Red, white, and blue. Rockets legend DeMarco. Nice one here. Lamello. Red, white, and blue. Nice one there. Hornets. It's on Yucca Kongwoo. Is that his first name? I'm confused. What? No, Jake just said Ola. No, I haven't got that message yet. There's RJ Hampton. There's like a kind of a funny story behind that I'll tell you in between breaks. Just remind me of why him and I were like laughing at it the entire Friday morning shift. Yeah, you might have been there. I don't know if you know the story, but if you don't, I will give you the load. I probably don't or more likely. Really weird, but really funny. So you streamed me and you don't. Got him. How is that a got him? It's got him. It's called re-streamed dumb. Showed him who's boss. So it just completely skipped Jake's message and went to illegal annoying. And guys, 12 to go still on 10 box Tuesday, breaking relatively soon. Couple more basketball breaks in between it, but 10 box Tuesday is coming up. It's going to be a good time. Good time. The show. Then we got what, four football breaks today too. I think so, just two prisms. Legal's bugging out right now. Mix in a water illegal. Mix in a water buddy. Then with Jake, Jake, mix in a water. What's the fun of the minute? Silver, Elijah Hughes. Ant-Man. Lamello rookie, another one. Silver, Tyrese, Maxie. Nice one there for the Sixers. Devon Vissell. All right, fair. Mergent, Tyrese, Maxie. I would say legal must be pumped with the trade turner signing for sure. No, no, we got a while. We got a, we got hours before unpackable. Yeah, we're still on basketball. No, not yet. And we are behind on everything. So probably won't finish until about one, one 30 with group breaks had a bunch of technical difficulty with the site, site today before I came in. Site was down for about an hour. So, sorry, Sal Berton rookie. Patrick Williams rookie. We have, we have like an IT person, Ty. Yeah, we got like an IT guy that works for us. That handles all that kind of stuff. But it was like a Shopify issue. Like Shopify had it down. What's up, Chris? Josh Green. Yeah, Shopify was having issues and then it just wouldn't come back. Like, and then it kept coming back and dropping again. So like nobody could get on the site for like a solid like hour or so before we went live. So we had a ton of group breaks we had to fill up. Jay McDaniels, Jaylen Smith, and an ant man, which happens. I mean, it's not the, yeah, Donnie went in and chewed all the wires, get notified. Went inside and gnawed on all the wires in the shop. Nice copper. He's knuckled deep. Now, Jake's a Marlins fan. Jake's a Marlins fan. Those Marlins. Oh yeah. Always wearing Marlins shirt jerseys. Yeah. The bit, the bittering spray doesn't work on Donnie. Donnie still finds his way to the wires, him and all the raccoons. It's because you live close to Tampa, Jamais Ramsey.   You have been. You're always like, your favorite person is Marlins man. Like you're a big Marlins man. No, it's not Jake Vellacy. That's Lamella Ball. Whatever he says, it's not. Right? Doesn't he? Robert Woodard. That's what honestly what I'm saying, Chris. Tail melada. Last pack. Got no recap on this one, guys. There is nothing to recap. So thanks again for the fill. Next up we got Elite.


The day's play takes you along for a walk in the lushness of the Almeda Botanical Gardens here in Gibraltar. I'm international master Tanya Sachdev, bringing you insights from the trade-wise Gibraltar chess festival. Welcome back! The final round and eight players in the lead. With match-ups against each other, this is their shot at the big finish. A tie is highly likely, in which case playoffs will decide the big winner. The Muzichuk sisters and Yulia Shweger are in a half-point lead for the women's top prize. But the army of players right behind them makes it equally unpredictable. The day's play caught up with our leaders. To this game, I was so lucky. I think my opening or middle game, he played very, very well. But only when it's taken. After that, I think he missed something and he won't quick draw. So that's why he played B5. I think this move was very, very bad. After that, I was so lucky I found some way and he missed something. So finally I win. I think he looked at my games obviously and he came up with a new plan. The bishops got very powerful and the centre ponds on D4 and D5 are extremely dangerous. I just escaped with a draw but of course it wasn't good position. It's a round to go and it's an intense fight for top finishes. The leaderboard is still a party of many impressive players. It's anyone's tournament. We've seen them in action and with their play-to-slay attitude, it's tough to predict what's about to happen. We speak to our trust experts, the dynamic duo Elizabeth Bytes and Grandmaster Simon Williams on who to watch out for. Well, at the moment we have four players, so in first I've been very impressed with Bacrow. He's a French player. If you take Maxime, he's done a very good job here because he's in the world's lead as well. But he is taking more risks in his chest and of course he's leading the competition at the moment. But a great chance for the final two games to go. One of our favourite guys we have to admit is, this is Richard Rapport from Hungary. He's always a very enthusiastic and cheerful player, especially with his age porn. There's a big love. I will of course cross my fingers for Harry Krishna because he's one of my best friends. And he's like one of the guys with six and a half out of eight plus. You have all the strong female players here and again they bring a lot of dimensions and a lot of great chest at the tournament. I mean we have right now some girls I think with five and a half out of eight like Maria Mutsuschuk, for guys like Nakamura are much much harder here to actually beat Grandmasters who are supposed to be much weaker when they actually done all their homeworks and that's probably one of the reasons why we resolved with four players up. I love to see Maxime win. He's a lovely guy. He's done this master class really easy to speak to. So Maxime's my bet. When it comes to opening repertoire and home preparation then I mean it's not a surprise that we have here a lot of players very tight to compete for the first place.  Don't forget to tune into our final round on the live broadcast. See you very soon. Bye for now.


My name is Laura Giddelson, and I am running for school committee. I am a mom of two, a lawyer, a town meeting member, and an advocate for social justice. Thank you so much for the opportunity to introduce myself and tell you about my work with Arlington schools and why I'm running. I'm an active member of the Pierce PTO. I serve on the Pierce School Council, and I work as a substitute teacher. I'm also a member of the town's LGBTQIA plus rainbow commission where I work on the education working group. And I'm one of the leads of the Arlington chapter of mom's demand action for gunsense in America. I'm running for school committee because I know from my own experience as both a parent and a long-time advocate for social justice that when elected officials support policies and allocate resources in ways that make it easier for every child and adolescent to access education, they change lives for the better. In 2023, Arlington schools are well positioned for success. We have a relatively new superintendent, are close to finishing our beautiful new high school, and we are poised to launch a five-year strategic plan. That said, there is a lot of hard work ahead of us. We are likely to face challenging budget conditions, and we'll need to confront those with Arlington's long-standing commitment to fiscal responsibility. All the while maintaining our commitment to providing our kids with the best education possible. We're also still emerging from COVID-19 and must confront the inequities and access to learning laid bare by the pandemic. To do this, we must make thoughtful and responsible decisions about the allocation of resources. So programs, services and support are equitable across the district. We need to support the creation and implementation of high quality professional development for faculty and staff to ensure that they are equipped to welcome, support and educate the districts racially, linguistically, culturally, economically and ability diverse learners. And we need to support recruitment strategies to bring new educators to the district who reflect the racial and cultural diversity of Arlington students and families. We need to prioritize special education services for students who experience barriers to learning and advocate for APS to allocate more resources to special education to ensure that every learner can access the education to which they are entitled. It is no secret that Arlington does not pay its teachers competitively with the communities around us and those we like to compare ourselves to. Pay parity has to be a priority to ensure we attract and retain the best educators for our kids. I will advocate for competitive compensation that is commensurate with surrounding districts and support professional development and training opportunities and workplace culture improvements that nurture, sustain and retain talented teachers, administrators and staff. Like many of you, I watched the school committee meetings in the summer of 2020 anxiously waiting to know what the school year would look like. Amid that uncertainty, I was impressed at the collaborative nature of the school committee's work and I believe I have the experience and skills to be a productive part of that work. School committee members do not make decisions alone. I have seen firsthand how the ability of committee members to listen and learn from community members and one another directly affects the quality of their decisions. In 2021, I joined the civilian police advisory board study committee and was elected as the committee's co-chair in its first meeting. While leading that committee, I worked with multiple stakeholder groups throughout town, including residents from all walks of life, elected officials, union leaders and town employees at every level from rank and file to executive leadership. The work of our committee resulted in a recommendation to the town to create a permanent police civilian advisory commission that was overwhelmingly supported by the select board and town meeting. That experience gave me insight into how important it is for the town to have volunteer leaders who understand how the systems of town government work in practice and also understand what needs to be done to improve those systems for the people who work within them and the residents they serve. As a parent and town meeting member, I have seen how important it is to have a well functioning school committee and I am excited to play a part in that hard work. I have the experience needed to work collaboratively and effectively with my fellow school committee members to ensure that we support and champion policies that are in the best interest of all of Arlington's kids. I'm Laura Gettelsen and I am asking for one of your three votes for school committee. Thank you so much.


Hello everyone, this is Dr. Ushaal Kumar and today I will be speaking on an important disease abdominal tuberculosis, the great masquerader and USG to the rescue. Let's go in for some data first. In 2018, WHO reported 10.2 million cases of TB. The death figure was around 1.2 million. Interesting part is India has approximately one fourth of the disease burden as per 2018 data. So India is one of the leading countries affected by tuberculosis. Abdominal tuberculosis compounds to about 10 to 20 percent of total load. Objective of this presentation is to highlight the important role of ultrasound in diagnosing abdominal cox, which is a great masquerader. Many patients are often left undiagnosed due to the lack of proper diagnostic work up or follow. Tuberculosis is endemic in Asia and Africa and it is reemerging in the western world along with HIV AIDS. The rates are rising, are consistent with the overall trend. TB poses a diagnostic challenge because many a times features are non-specific, they can lead to diagnostic delays and can lead to multiple complications too. So a high index of suspicion is an important factor for early diagnosis. Abdominal involvement can occur in the GI tract, the peritoneum, the lymph nodes or the phallid wethera which is rare. The spread is further aided by poverty, overcrowding and drug resistance. So again early diagnosis is the key. Most patients which are diagnosed and are put on AKT respond very well and surgeries required in minority of the case only. One more telling ground reality in the Indian subcontinent is the lack of resources and affordability to carry out diagnostic tests. Therefore today in this scenario I propose the liberal use of ultrasound and ultrasound guided procedures as the first line of diagnostic repertoire. Ultrasound technology has moved from leaps and bounds, excellent high frequency linear probes and unparalleled resolution even at greater depths are now the USP of most machines. Good spatial resolution, cost effectiveness, reproducibility and being easily available even in the remotest areas gives ultrasound an edge. To maximize the ultrasound machine capability we have to just take care of these 4-5 factors. These are the transducer frequency, proper adjustment of the depth, focus, gain and the most important factor is spatial compounding. Most common abdominal symptom is abdominal pain, constipation, diarrhea, fever and aneroxia also are very important systemic complaints. Now classification of tuberculosis, I won't go into the details of these. I'll just go into the peritoneal classification. Peritoneal classification is divided into three types. The wet acetic type where there is copious amount of free fluid and can be loculated to. The fixed fibrotic type where you can get multiple plaques and you can also get loculations and septae. The dry and the plastic type where you get fibrotic strands which are irregular but there is no free fluid generally. I'll just go into 4-5 commonly seen types of abdominal tuberculosis at my clinic. Symmetrical thickening of the peritoneum and misentry, acitis which it can be clear, echogenic or loculated. Symmetrical bowel wall thickening, most commonly the IC junction involvement. Enlargement of lymph nodes with low attenuation that is hypoechoic and occasionally there can be multiple matted lymph nodes which can be seen as the hallmark of cox many a times. Multiple plaques or nodular lesions in the misentry can also be seen with complicated cox and rarely surface nodularity or visceral organ involvement mainly deliver. Misentric disease is an important manifestation of early stage of abdominal cox. Initially it is thickened with few discrete lymph nodes. In the latest stage however there could be irregular inflammatory masses with increased ecogenicity. Ultrasound offers a distinct advantage in demonstrating features with adequate visualization of the normal and disease misentry. Misentric lymph nodes generally show hypo attenuating features which could suggest areas of necrosis which are classic to granular matters disease but they are not specific because they can be seen in necrotic metastasis. The momentum involvement can also be cake like or nodular and may appear similar to peritoneal carcinomatosis which is one of the differential diagnosis. In the list of differential diagnosis of peritoneal disease things which come close to misentric cox can be misinus carcinomatosis, pseudomixoma peritoneal, peritoneal meds, misentric fibromatosis and sclerosis misentritis. I would not like to go into the details of all these. Whenever the gastrointestinal tract is involved, neural thickening of the IC junction is the most common sight that is a textbook picture we have learned all our lives. However, circumferential bowel wall thickening which can involve the ilium or the IC junction is not uncommon in cox and can mimic diseases like Crohn's disease which is common differential diagnosis. So, how would you like to differentiate the two? Mostly in cox there is multiple enlarged lymph nodes which can be necrotic, there is a mental involvement which can be a cogenic and thickened or cake like and there is a cytos. All these which are go in favor of cox and also IC junction involvement is more common in cox whereas, secom involvement is rare in Crohn's disease. Four figures which show the circumferential wall thickening of the terminal ilium and the secom. There is an atypical case case and routine where the secom as well as the proximal ascending colon was involved and the diagnosis was confirmed in colonoscopy to be cox. Mated lymph nodes with internal breakdown, this is case one. Here you can see multiple hypoechoic lymph nodes which are in close vicinity to each other and interspaced hyper echoic misentry suggestive of mated lymph nodes. Classic of cox. Here is case number two. In this case we can see there are multiple mated small bowel and as you can see there is copious amount of acitis and multiple small loculated areas of acitis with multiple septae also. The third case is an interesting case where you can see all the things which are common in cox. Echogenic misentry, abnormal nodes, thickened bowel loop which are inflamed and acitis. So all features of a cox in one case. This is very interesting case. If you can see there is minimal free fluid. However, the diagnosis which was clinched on this lining which was abnormal along the peritoneum, thickened peritoneum. We discussed cake like nodularity. This is one case where there was extreme amount of acitis and multiple areas of cake like echogenic areas arising from the misentry suggestive of omental nodularity seen with cox. We discussed iliocecal cox. Now this image is a panoramic view of a classic icy junction cox where we can see the thickened cecum the terminal ilium classic cox. These upper two images show sub hepatic and intra hepatic involvement in proven case of cox. The lower set of three images. The first two show hypo attenuating lymph nodes. The first one showing internal breakdowns of necrosis. The last image showing inflamed peritoneum also a feature of cox. These are two panoramic again panoramic images of diffuse ecogenic omental thickening seen in the entire abdomen in the space between the cell small bowel with associated free fluid. Both were proven case of cox. Two common differential diagnosis of ecogenic misentry are omental infarct appendicitis loike and divertic loites which is a very uncommon differential diagnosis. This is a case where there is focal ecogenic omentum in close proximity to the distal end of the descending colon. As it is seen very close to the colon diagnosis of appendicitis epiploic was suggested. There are no other signs of tuberculosis in the abdomen. This was a case of appendicitis epiploic close to the descending colon. The site is very important descending colon. Okay this case there is similar finding of ecogenic omentum but it is close to the liver and the right kidney. So it is in the right hypochondrium. It is a lady who is a 40-year-old lady with focal pain in the right hypochondrium. This is a classic case of omental infarct. There is no other differential diagnosis. So I had reviewed basically retrospectively 43 patients from January 2017 to July 2018 who had signs of abdominal cox who were diagnosed on ultrasound. Most of them were proven on ultrasound guided intervention or other biochemical or surgical tools. So this study showed definitive diagnosis was reached in 38 cases. There were five who were treated empirically. Common features in abdominal cox of these patients were free fluid omental thickening lymphodionopathy and omental flux. Okay, diagnosis was reached in most of these cases commonly by ascetic tapping, biopsy and FNA. Very few of them required either a colonoscopy, surgery or biochemistry. So being a real-time test, ultrasound guided procedures like ascetic tapping, nodal and omental biopsies can help in getting a tissue diagnosis. I will just show a few cases I have done. This is a case of abnormal ecogenic omentum with free fluid but true fluid was not tapable. So I did omental biopsies. Okay, you can see here the gun. This is the case where there is a very small pocket of fluid. So very acutely I took a spinal needle and tried to aspirate everything which was there in the pelvis. Came out to be cox. Okay, third case is interesting because though it's a simple cox node, it is in very close proximity to the right kidney. So had to be careful but ultimately could get a good chunk of the node and we could get to a diagnosis of cox. Okay, one important thing whenever we tap fluid from the pelvis and if there is omental thickening or the fluid is in the deep pocket, try using a spinal needle, put it entirely into the ascetic fluid, remove the distillate and try to aspirate. Now I'll just give you a small example. If there is a small pelvic collection, free fluid, omental plaque or omental disease or a peritoneal node, here a USG guided procedure would be more helpful and advisable than use of profession. So for example, a patient turns at 3 p.m. to do a USG. You had a clear cut free fluid, say free fluid in the pelvis. We call up the consultant. Please go ahead with the aspiration. You do a guided aspiration to get a result faster and it is cost effective. Okay, one note I would like to put here is whenever you do for elderly patients with comorbidities or biopsy or FNA, try getting the bleeding and clotting times first before you go to make it. One more important tip, if you are suspecting abdominal coughs and you might not get enough material from the abdominal for diagnosis, always scan the CP angles and the neck before you let the patient go. You might get a sizable effusion or a large node where you can get a sample from. To conclude, I would say ultrasound still remains the most robust initial modality of choice. Diagnose abdominal coughs including nodal and peritoneal disease. Its ubiquitous availability improved resolution as a cost effective tool in the primary diagnosis of abdominal coughs without overuse of cross-section. Advancement in probe technology has also given unparallel resolution in diagnosing equivocal cases with pinpoint accuracy.


Hello, my name is Mike Halcro and I'm here with Eric Biggers, my colleague, and we're going to present on FS Verity. Now we're just presenting on this, but this is actually an effort that's being contributed to by multiple people, including Ted So and Victor, who's also here from the Android team, and so forth. So we've started out with some design work about a year ago, and I'd like to say any good parts of the design came from Ted, any questionable parts I'll take the fall for, personally. And then code-wise, anything that's good comes from Eric, and anything questionable you see in the code, again, I'll take the fall for that. And so just by way of background, I originally wrote eCrypt FS, some of you may have heard of it, and I apologize every opportunity I get for having done eCrypt FS, I'm sorry. And I've since also done FSCrypt, which is together again with Ted and other contributors. That's the native encryption capability in EXT4 and F2FS. Anyone else who's interested in integrating FSCrypt, of course, always interested in having a chat. So we're going to talk a little bit about taking measurements of contents of storage, DM Verity, and then doing integrity and authenticity in the file system. Then we're going to introduce some of the work that we've been doing with FS Verity and what some of the use cases are that we have in mind. So really at the core of all this, it's about taking hashes. And we take measurements of contents of storage in order to establish identity. And a hash is a trapdoor one-way function, and what that means is we take a preimage, which can be of arbitrary length, and you run it through this hash algorithm, and you end up getting just a few dozen bytes. And those dozen bytes can reliably uniquely identify the thing that you're taking the hash of. What you can do then is you can do verification of the root of trust, against a root of trust, for that few dozen bytes that you generate from the hash algorithm. When you take a hash of an object, you measure the entire thing prior to taking further action with that thing. There can be significant latency on initial access of it, especially if it's a large object, and if the computational resources of the platform are limited. If you take an initial measurement of this whole thing, you can validate it before you even begin access to that thing, which is a really nice security property, and oftentimes a requirement given what your security adversarial model looks like. However, there's no further revalidation of the contents coming from storage after that initial measurement. And so if you have a malicious data source, such as a file server or a disk or a controller firmware, which has been attacked in some way, then you can play games through this man in the disk, so to speak, and make changes after the initial measurement. There are firmware attacks. You can look up things like equation drug and gray fish and so forth. This is something that's been around for quite some time. And it is something you have to worry about in several contexts. So an alternative way to taking a measurement of the entire object all at once is to use an authenticated dictionary structure. Now, there are several different structures that exist, and they have various pros and cons depending upon what your usage requirements are. But one of the common ones is a merkle tree. And with a merkle tree, what you do is you segment what it is that you're measuring into chunks. You measure the individual chunks, and then you take the measurements of the measurements all the way up to some top level. And so what this allows you to do is to take a partial measurement while ensuring comprehensive validation. Because all you need to do is do a signature against the top level of the authenticated dictionary structure. And after you access some subset of the object, you can say, well, at least the part that I've looked at has been validated against a digital signature, which is done on the top of the data structure. When you first access the object, the time it takes latency-wise is a logarithm of the object size, because you don't have to read the entire object before you begin access to it. The trade-off with this, of course, is that IO errors are possible while you're processing the file. So this allows for an attacker to be creative by injecting faults in the middle of the file that you're accessing, and thus having some arbitrary manipulation of the execution of the process by virtue of the fact that you've gone a certain amount of computation. You've generated a certain number of side effects, you've impacted the environment, maybe sent out some network packets or what have you, and then, bam, you get an IO error, and you can select where that IO error occurs. And so that is a concern when you're taking this particular approach. So how many people who have Android devices, when you turn on your phones, how many of you get something that looks like this? Okay, surprising few. This is what you see because when you disable Android verified boot, and so this is a feature of Android where we take the system image and we've generated an authenticated dictionary structure against this system image and pushed it out. And then we have some keys which are in the secure environment on the platform that are used to validate the root of this authenticated dictionary structure, or Merkle Tree. And if you're unable to validate the authenticity of the system partition, then we give this warning saying, hey, look, we don't know what's on your phone, all bets are off. This is accomplished with DM Verity. And so this has been around for a little while. DM Verity sits in between the block device and the file system. And it protects all file system content plus the metadata. So the user-generated content or the contents of the individual files or inodes, those are protected. But in addition to that, everything associated with that with the file system, like the block mapping, the DN trees, and so forth, all of that is also protected, which is a very nice property to have. And it's something in general I recommend you have if your environment allows you to do so. As we're going to discuss, not every environment is amenable to that level of protection. So if you have, for example, a mobile platform like Android, you have an ecosystem, you have partners, you have different regions, different devices, and so forth. Every incremental update to the system partition requires regenerating the entire auth tree. You'd somehow have to pack that together, all of these updates, with system image updates. And then when you deal with this Cartesian explosion of devices and updates and versions and so forth, you end up getting something that's very unwieldy. It's intractable to be able to keep all of that authenticated in the way that we'd like. So we start looking at the file system as a way to address this issue. And what we talk about is partial disk authentication, where selected parts of the file system that is primarily the file contents are validated using these authenticated dictionary structures. And so this facilitates, you know, incremental updates of arbitrary subsets of the file system, and significantly reduces the complexity and deployment. Of course, the trade-off for this is that the file system made of data is unauthenticated. And so there could be opportunities for people who are more creative than I am to find ways to manipulate the block mappings or the de-entries, directory structures, and so forth in order to trick applications to behave in ways that they weren't intended to behave. I'm going to go ahead and turn this over to Eric, who will talk about some of the more technical details of FS Varity. OK, so now we get to FS Varity. FS Varity is basically DM Varity for individual read-only files. It's implemented at the file system level. Specifically, it's part of the file system, but also most of the code is separated out into its own module that is shared by multiple file systems. And so far, we've implemented EXE4 and F2FS support, but it could be supported by other file systems, too, in the future. And FS Varity is not yet upstream, but we are working on it, and I sent out the first version of the kernel patch set a few days ago, and anyone is welcome to re-view it. So the contents of a file using FS Varity look like this. There's the original file contents, then potentially a bit of padding. Then the Merkle Tree. The size of the Merkle Tree depends on the settings used, but with the defaults for large files, it's approximately the original file size, divided by 129. Small files do have more overhead due to the padding. Then after the Merkle Tree, there's a small structure called the FS Varity does have a descriptor, which contains some additional metadata files, like the hash algorithm and the black size used in the Merkle Tree. And similar to DEM Varity, all the FS Varity metadata, including the Merkle Tree, is written by user space ahead of time, and the kernel only reads it. We've written a user space tool which sets up this metadata. The simplest command is just FS Varity set up, and then the file path. That appends the metadata to the file using the default settings, which are the SHA-256 hash with a 4K black size, and without any signature included. But there are options to change these settings if you want to. Also like DEM Varity, you set a black size, usually 4,096 bytes, and all the hashing for the Merkle Tree is done over blacks of that size. Also the root level of the tree, which is always only one block is stored first in the file, and the leaf level, which we call level zero, is stored last in the file. The leaf level is the largest level since it gives the hashes of all of the data blocks. The other important metadata fields stored on disk include the black size, hash algorithm and the original file size. There's also a way to store variable length fields. Those include the root hash of the Merkle Tree, optionally a salt to salt hashes, and also optionally a PKCS7 formatted digital signature of the file measurement. So it turns out that the Merkle Tree root hash by itself is not sufficient to reliably identify the file contents because of the other metadata fields like the hash algorithm and the black size and the original file size. And because of the padding that's needed at the end of the original file contents. So what we actually do is we hash the root hash together with these other metadata fields. And that gives us another hash value, which we call the file measurement. And the file measurement is what FSFARITY actually reports as the hash of the file. As I mentioned, the FSFARITY metadata is written by user space. Afterwards, there's an IACTL to actually enable FSFARITY on the file by setting the FSFARITY bit in the inod. The user space command to do this is FSFARITY enable. And once FSFARITY is enabled, the file becomes read only and the Merkle Tree and other metadata becomes invisible to user space. So user space will only see the original file contents. Also file systems are allowed to move the metadata to some or else if they want to, like into a file stream if the file system supports that, but for EXE4 and F2FS, we're just keeping it past the end of the file contents. So to implement FSFARITY when reading data, we hook the file system's read pages function, which is the function that reads data from a file into that file's page cache. If the file is an FSFARITY file, when a read from disk completes, but before unlocking the pages, we have the file system submit the pages to a work queue, which calls into the FSFARITY module to verify the hashes of the pages. To do that, for each page, FSFARITY reads any needed hash pages from the file and verifies the hashes starting from the root node of the Merkle Tree and descending to the appropriate leaf node. And finally, it verifies the hash of the data page. And as an optimization, each hash page is also cached in the page cache with a bit saying whether it's been verified or not. So since there are many hashes per hash page for usual IEO patterns, most data pages get verified without having to read or hash any additional hash pages. And we do not allow direct IEO on verity files, since that would bypass the verification. But we do support encrypted files. In other words, files that use both FSFARITY and FSFARITY simultaneously. So FSFARITY is essentially a way to measure or hash a file in constant time, subject to the caveat that the verification against that hash happens on demand as data is read. And applications will receive an IEO error if they try to read from any corrupted part of the file. And FSFARITY file measurements are available in the kernel, but are also exposed to user space via an IOctl. And with the user space utility, FSFARITY measure just calls that IOctl and prints out what the kernel returned. So there are various use cases that can be supported or enabled by the FSFARITY mechanism. The simplest is integrity only to detect accidental corruption. And for that, all you have to do is turn FSFARITY on. There's also the auditing use case where you log the file measurement before doing something with the file, like executing it. And finally, there's the authenticity or appraisal use case where you have a known good file measurement either from a digital signature or from somewhere else, and you validate that the actual file measurement matches the expected one. And that detects both accidental and malicious changes to file contents. There's been some confusion about the relationship between FSFARITY and IMA, the integrity measurement architecture, which already exists in the kernel. The difference is that FSFARITY is a lower level thing, basically a way to hash a file, whereas IMA is focused more on higher level things, like what is the policy for which files are measured and what should be done with the measurements. So in general, FSFARITY is not replacing IMA, and in fact, we're planning to have IMA support getting its measurements through FSFARITY on files that use it. So that should allow IMA users to take advantage of FSFARITY, for example, for IMA audit or for IMA appraisal. However, we have found that some users find FSFARITY to be useful on its own without IMA, so it will also be supported to use FSFARITY on its own and just do things with the file measurements in user space via the I-Octol I mentioned. And we're also considering supporting a mode where you can configure FSFARITY to enforce that all file measurements are signed by a certificate that has been loaded into the kernel. That mode is maybe still up for debate, since it does overlap with IMA, but we do have a user who is asking for it. So in the IMA use case, this is a representation of what IMA does today. Essentially, when IMA needs to measure a file, for example, because if an open or an exec, it just hashes the entire file, which causes a long latency before the operation can proceed. And this is what IMA is planned to look like when it's used on FSFARITY files and configured to support them. It's the same as before, except the actual hashing of the file contents is replaced with just asking the file system for the FSFARITY measurement, which allows operations to proceed without waiting for the whole file to be hashed. So if you're interested in FSFARITY, you can try out the kernel patches and go to space, review TEL body, and help review the patches, which as I mentioned, I sent out a few days ago, and they add support for FSFARITY to EXE4 and F2FS, and we've also been working on tests as part of the EXE4FS test file system testing suite. So this concludes our presentation, and thank you for your attention. Question. Can you talk about performance impacts? So the performance for smaller files is going to be a little more impactful because the amount of space that we take for the tree structure is one block, which right now is fixed to the page size, which from most architectures are 4K. And so you're going to wind up amplifying the IO as a result. However, you also get some characteristics of storage that help mitigate that, such as read ahead. The person who's best equipped to give fine details about this is sitting right here, Ted So, and I'm sure he'll give a little more context on that. So in general, it's going to be no worse than DM Verity for large files. DM Verity also has some significant performance impacts if you're using it on hard drives simply because you're seeking a lot to read the Merkle tree. In practice, the root of the Merkle tree will probably always be cached, so that's not a big deal. But some of the intermediate nodes and the leaf nodes don't get used as often. And so they very often will be pulled into disk. In practice, this has not really been a problem on flash devices because on flash devices, random reads are much less of an issue. I think we've been a little bit more worried about the CPU impact of actually doing the hash, especially on some of the lower end Android devices that just simply have a CPU that doesn't have a whole lot of oomph. That's right. Yeah, so I think it's Goldmont is the Intel architecture that has the SHA-2 acceleration, and so that helps. Since we are targeting mobile platforms, we do expect that there's going to be additional power consumption as a result of the frequent hashing, which we anticipate is going to be a benefit because these trusted APKs for these privileged applications on the platform, they're currently measured at the time that the APKs are installed and validated. But then after a device reboot, they're not revalidated, so anything could have happened to storage. We expect that's going to be a good trade-off. So you mentioned earlier that one of the problems with having verification be done rather than on the entire file, but on individual blocks is that you can have EIO at basically an arbitrary point in the file and screw it up. Is there any mitigation for that that you have, or did I miss it? It kind of feels like the nature of the beast. If you're going to delay verification to the point of access, then there are tricks you might be able to play if you want to try to detect that there has been an offline attack against your storage. It may not necessarily be something that will be at all helpful for a man in the desk or you have a compromised controller that can fake the results arbitrarily at the time of access. But when you bring the platform back up, we've imagined scenarios where perhaps you could have something in the background that gradually reads the files and does nothing with the reads except just reads the files. Then you're just in a race condition and you're not necessarily getting security guarantees. The other thing to note here is that for the initial use case, we're using it for privileged APK files, which basically means the class loader is going to be loading a class at a time. And so if there is a failure, it will probably be as you are loading a class and not at any random point in program execution. And so that mitigates that somewhat for that particular use case. It's very much user-beware. You need to be aware of the benefits and trade-offs of using complete measurement of the file prior to the start of any access at all versus validation after you've begun access. So with DMVarity, we added forward error correction to prevent random bit flips from preventing your system from running. Are you doing the same thing for FSVarity or considering something like that? We've considered it. We haven't implemented that. That's going to be for a future version, I think. But it definitely is something that you want to consider doing so you can mitigate the incidental bit flips as opposed to the malicious bit flips. So how do you exactly protect against a man on the disk? As far as I understood, you're still storing the Merkle tree on the disk, so the man on the disk could modify that while system boot up to correlate to the bad changes in the file. Are you using some kind of cryptography and making sure to store the keys to that signature of the disk, or how does that work? Yeah, that's a great question. And so it has to do with what is the profile for the entire platform? This is your secure boot process, and how are you utilizing things like secure elements to get key material into the proper locations? And so you have to consider that in your adversarial model, and you have to make sure that you get your keys from the trusted source, the secure element of the platform. Then what FSVarity is actually doing is we're creating something called the Neffes Verity Measurement, which isn't just the contents of the files themselves, but it's also the metadata, including the tree. And so the root of the tree together with the descriptor, which is the metadata that describes the characteristics of the FSVarity file, all of that is captured in the root measurement, which is the thing to be validated against the key that you get from the secure element. Yeah, I mean, the other thing to say here is that measurement, again, for this initial use case, will be digitally signed, and the key to verify that will be in the system image, which is protected by DMVarity, and the key for DMVarity is in the kernel, and the kernel is protected by the trusted bootloader, and so for that initial use case, that's the chain. Yeah, in the next session we have a panel on hardware root of trust type issues. So one question I had was whether you had thought about attestation of that appraisal that you perform. We haven't thought about attestation. In general, attestation terrifies me, but yes. So you're talking about linking with the TPM and doing PCR measurements based on. Yeah, do extending the measurement off to be validated. Right, binding to PCR measurements and so forth. That's not a requirement for the Android platform. It's an interesting use case, and we'll consider that. So I think we might be able to get support for that. And when we add IMAs, how part? Mimi's nodding over there. IMA. Any more questions? OK, thanks.


There's no such thing in the Bible, no room given for theology that says just let go and let God. No theology of that in the Bible. There's nothing in the Bible that gives us any room to fall asleep on our duty, so to speak, in the Christian life, to work out our own salvation with fear and trembling. We have the living God through His Spirit working in you, believer, to accomplish His ends that He has determined before the foundation of the world for you, that you should be holy and without blame before Him in love.  It is that God at work in you to will and to do according to His good pleasure.