The House of Squibb, manufacturing chemist to the medical profession since 1858, brings you Academy Award. The pictures, the players, the techniques and skills which have won or been nominated for, the coveted awards granted each year by the Academy of Motion Picture Arts and Sciences, to each in his field for outstanding achievement. The House of Squibb, makers of the great family of Squibb medicinal products, today brings you two distinguished stars, Pat O'Brien and Annoff Mongeau, in the famous story of newspaper life, Front Page, which was nominated as Best Production of the Year for the 1931 Academy Award. Mr. O'Brien and Mr. Mongeau will play the same roles they created for the screen, and in which Mr. Mongeau was also nominated as Best Actor of the Year for the 1931 Academy Award. This is the story of the Fourth Estate, which will prove that man didn't know when he was well off and only had three estates. This is the story of a good newspaper man who wanted to get married and go to New York, of his tyrannical and resourceful managing editor who wanted him to stay being a newspaper man. And of other assorted matters pertaining to the case, including a guy who was to get hanged in the morning. Juffie, Jamal, did you find Johnson? No, Mr. Burns, not yet. We've tried all the saloons and other places that you and Mr. Johnson usually go to, but the word is not go to, it is frequent. We frequent places. Frequently. But I will get Hilted Johnson or else get your laundry out of your desk and get out of the city room. I'll put another man on. In you have, Juffie.  And Hilted Johnson's the only man on the staff that I can trust, and I've got to have somebody yet to hang in there. We've got to have Johnson. Hello, Juffie. What? What do you mean he's getting married? Who's getting married? Johnson. Well, he can't do that to me. Where is he? Okay. Where is he in some church? Now, it's alone. Good, good. He's getting up his courage. He's still got a chance. I'll get over there right away. Okay, boss. Well, Hilted, so you're leaving me for marriage. Why? Not your business. Well, how did it happen, Hilted? Tell Papa Burns. There was a moon. Oh, I guess that lets me out. Well, I'll give you a farewell party. Thanks, Waller. But it hurts, Hilted. You're not telling a fellow. After all I've done for you. You mean after all you've done to me.  Get a home, wife. That's right, Hilted. I was never big enough to let a nice girl reform me so I could stay in a two-room love nest at night and walk the floor with a crying kid and the fellas were out having a lot of fun. Marriage does make a respectable citizen out of a man that must be grand. You never have to worry about a place to go. You always know you're going home. None of this jumping around at all hours, having to be on the inside of all the crazy excitement in this town. The 515 out to some suburb. A home cooked dinner at exactly 7.30 every night and in bed by 10. Unless after the tapioca your friends drop in for a neighbor to chat. I don't blame you, Hilted. It sounds great. Yeah. Excuse me, Waller. I just thought of something. Two more, Mr. Burns. Yes, Mike. Fill them up. Well, that fixes Hilted Johnson's wagon all right. No woman's going to steal the best man I've got. Mr. Burns. Yes, Mike. Mr. Johnson said to tell you you should put that line on a Victoria record and play it for some country boy. He's getting married.  Give me my hat! Press room, criminal court building. No, no, Mabel isn't here. Endicott speaking. Oh, hello, Mr. Burns. Why, no, no, we haven't seen him. Hiya, slaves. Hiya, big shot. Just a minute, Mr. Burns, somebody just came in. Hilted, hey, Hilted Johnson. What? Listen, Hilted, will you do me a personal favor and talk to Waller? He's called up about nine million times. What's the matter, Hilted? Are you scared of him? I'll talk to that maniac with pleasure. Hello, Mr. Burns. Why, your language is shocking, Mr. Burns.  Get a pencil and paper and take this down. Get it straight because it's important. It's the Hilted Johnson curse. The next time I see you, no matter where I am or what I'm doing, I'm going to walk right up to you and hammer on that monkey skull of yours till it rings like a Chinese garb. Oh, boy. Tell it him. Listen to us. Listen, listen, Waller. No, I ain't going to cover the hanging. I wouldn't cover Washington Cross in the Delaware if he did it all over again. Never mind the hair oil.  Oh, I didn't tell you that, did I? And if you know what's good for you, you'll stay west of Gary, Indiana because the Johnson's never forget. And that boys is known as what is telling off the managing editor. Hey, why'd you quit, Hilted? I'm getting married. See these railroad tickets be to New York tonight. Tonight? What do you mean, three? Me and my girl in her darling mom. Ha! He's in love. Tutsi-wutsy. Hey, does Burns know you're getting married? Does he know? He shook hands like a pal over to throw me a farewell dinner. Oh, that's his favorite joke, farewell dinner. Sure, he poisons people at him. Oh, hello, honey. Uh, Kenny Tucker, 216, William.  Oh, hello, Peg. Uh, I know, but I, uh... Oh, you bet I resigned. Yep, on the 11-18 tonight. Huh? Oh, the press room. I just dropped in to say goodbye and I'll be... No, I'm not a chance, honey. Got a taxi waiting. Ten minutes. All right. See you guys in a few minutes. I gotta make the rounds and say my farewells. Well, there goes a good guy straight but, anyway, I hear he's got a contract with an advertising agent. What doing, writing poems about ladies' girdles? Who dumped this out of the window on me just now? We promise not to tell. Ah, Sheriff, it's only a spittoon. It was Hildy Johnson, wasn't it? All right, I got a good notion to take this press room away from you. That would be a break.   But how does it look when there's somebody in the death house? Honey, I suppose he feels listening to all this revelry. What you'll care, Sheriff, how he feels? We're doing everything we can to... Now get your whole ticket re-elected next week. Well, when Earl Williams drops through that trap tomorrow, it's a million votes. Can we help it if the people rise to support this administration's stand against corruption? First son of fight by Mr. Earl Williams? Ah, a guy who loses a job he's held for 14 years. Joins a parade of the unemployed. Because he's goofy from lack of food, waves a red undershirt. Williams is a dangerous radical. And he killed a policeman. Now, wait a minute. Once and for all, Sheriff, will you hang this guy at 5 a.m. instead of 7? It won't hurt you when we can make a city addition. Oh, now, Roy, you can't hang a fellow in his sleep. Just to please the newspaper. No, no, no. But you can keep postponing the hanging, so it'll come just before the election. With this new alien is coming in, how do we know there'll be a hanging? Yeah. What if the professor finds he's insane or something? He won't find he's insane because he ain't. He's as sane as I am. Sainer. Now, here's a resume of the situation. The newspapers have got to put their shoulders to the wheel. Impressed on the radicals that a death warrant for Earl Williams is a death warrant for every bomb-flowing foreigner in this town. Hello, give me the desk. Hey, get this. The sheriff just put 200 more relatives on a payroll to protect the city against the Redcoats. Praise my better darned. Okay, baby, give me the desk. Hello. The sheriff just received four more letters threatening his life, which he is going to answer by a series of raids. And to prove it's on the square, he's going to write himself four more letters threatening his life. Yeah, I know he wrote them on account of the misspelling. Desk, please. This is McHugh, Joe. More on the Williams hanging. You ready? The condemned man ate a hearty dinner. Mock turtle soup, chicken pot pie, hash brown potatoes, combination salad, and pie a la mode. Yeah, baby, you better get the rest of this. The condemned man ate a hearty dinner, as follows. Noodle soup, roast beef, sweet potatoes, cranberry sauce, big hunk of pastrami. Yeah, and make mine the same. Come on, come on, who opened it? I did. Cut up and give out the cards. How many? Five. Well, all set to go, boys. Except to say goodbye to you, bums. I got a dumb brother who went into the advertising business, Hildy. Got seven kids, belongs to a country club.  Yeah? Listen, if you want to know something, you'll all end up in the copy desk, gray-headed, humpback, slob, dodging, guaranteed for your 90. And you'll be out in the street the minute your contract's up. Not me, my girl's uncle owns the business. Has he got a lot of jack? Let's choke on him. Look, he gave us 500 in cash for a wedding present. There it is, less than what it cost to get the tickets to New York.  Here, what goes on? William, broke out of the death house. Here, let me get that phone. Hurry up, sister. This is important. Hello, Jimmy Rawlings. Come on, give me that. Oh, I might have known buying them tickets was bad luck. Hello. Hello, morning post. Give me Waller Burns. Burns has an STINK. Waller, Billy Johnson, Earl Williams just slammed out of the death house at the county jail. Yeah, yeah, don't worry, Wall. I got the whole thing. Got it from Jacoby. Sure, it's exclusive. It's a pep. Only get this. It cost me 260 bucks to bribe the guy. But oh, my girl gave me to get us to New York. Okay, all right, all right. But don't forget to send that dough. Look, this is the jailbreak of your dreams. This profound thinker. The alien that stayed hard to examine, Williams. Yeah, the one from Vienna. Yeah, well, he decided to make Williams reenact the crime.  He had to have a gun to reenact it with. And who do you suppose supplied the gun? The sheriff. The sheriff gave his gun to the professor. The professor gave it an earl and earl. Shot the professor right in the stomach. The professor's in the hospital. Williams is evaporated and the sheriff's gone nuts. Ain't it perfect? All the phone while I'm not finished yet. Send that dough over right now. I just did it as a personal favor. I'm leaving town. No, don't. I don't get married. Tell the guy to hurry with it. I'll wait here. Oh, hello, Peggy. And what was that? Nothing. I was just telling Brenda. That's all. Hello, darling. Oh, now, Hildy.  No, no. Then I think I'd better take care of it from now on. Now, sweetheart, it's going to be perfectly all right. Oh, then you haven't got it. No, no, not this minute, but he's sending it right over.  Walter? Oh, Hildy, that man makes you do everything he wants.  Oh, baby, listen. I was just here by accident. If something happened, I had to use some of our money to get information. I'll get it back. Look, Hildy, mother's downstairs in a taxi cab. I'm just ashamed to face her. If she knew about that money, well, it's all we've got in the world, Hildy. We haven't even got a place to sleep except the train. I'll tell you what. You and mother go over to the station and get the baggage checked. Here's the tickets. You mean you're not coming? Oh, of course I'm coming. I'll meet you both at the information booth. Who would throw that Walter Burns? You simply can't resist him. Come on, Hildy. Keep on William's hideout. We go with the riot squad. Well, this is okay. Wait, wait. Oh, you're not going with them. Well, Peggy, wait for me at the information booth. Oh, we'll watch downstairs first. You see, you don't go anywhere with the riot squad. Oh, come on, baby. I'll just finish up there for a few minutes and meet you under the clock. All right, Hildy. But if you don't come, I'll never trust you again. So there. Oh, I have to get married on a day like this. This is the press room. I'm looking for the sheriff. I'm the sheriff. He is certainly a hard fellow to find. Well, what do you want? I'm the mayor. Well, I'm Pinkers, a messenger from the state house. This is from the governor. What's from the governor? The reprieve for Earl Williams. For who? Wait a minute. Who else knows about this? They were all standing around when he wrote it. It was after they got back from fishing. Get the governor on the phone. Ain't got a phone. They're duck shooting now. Oh, a lot of blasted Nimrod. Pure politic. We've got to think fast before those lying reporters get hold of this. What'll we tell them? Tell them the party is through in this state on account of you. Here, you. What's your name? Pinkers. You never arrive with this, whatever it is. Get that? Yes, I did. How much do you make a week? $40. How would you like a job for $350 a month? Me?  Here, go to this address. It's a nice homey little place. Tell her, tell her a friend sent you. Listen, Burns, I'm waiting here. Where's the guy with my doll? If you try to double-cross me, I'll... I'll... Holy mackerel, I'm seeing ghosts. Earl Williams just crawled through the window. Hang up. Hang up. I'll call you right back. Williams, I saw you when that searchlight went past the window. Drop that gun. It ain't loaded. I fired all the bullets already. I surrender. I couldn't hang onto that roof any longer. You know, I...  I was telling the fella that when he handed me the gun.  I locked that door. Waking me up in the middle of the night. Talking to me about things they don't understand. Calling me a radical. I'm an anarchist. It's got nothing to do with bombs. It's the philosophy that guarantees every man freedom. Yeah, yeah, yeah, yeah. All those poor people being crushed by the system. All those boys that was killed in the war and in the slums. All of those slaves to a crust of bread. I can hear them crying.  Go on. Take me back. Hang me. I've done my best. Kill me! Kill me!  No, not you, Peggy. Get me the managing editor. Get me Waller Burns, but quick. Don't, Peggy, for... Oh, Waller, something big has happened. I captured Earl Williams in the press room. Get over here right away! In just a moment, you will hear the second part of the Academy Award. When you ask for a tube of squib dental cream, you're really asking for a tube of pure refreshment. There's refreshment in the flavor of squib dental cream. It's so cool and tangy, like the taste of tendered green mint. There's refreshment in the brisk action of the squib dental cream. It wakes up your mouth, leaves teeth and gums feeling delightfully clean. But that isn't all. You can taste, feel and see the refreshing difference when you use squib dental cream. It helps to bring out the natural sparkle of your smile because the special polishing agent in this quality dentist is one of the safest, softest, yet most effective known to dental science. In every way, squib dental cream lives up to the famous standard of perfection that distinguishes all the great family of squib products. Try squib dental cream. Taste, feel and see the refreshing difference. Before we bring you Part 2 of Front Page, we want to thank the writers of this picture, Ben Hecht and Charles McArthur for making the story available. And now the House of Squib presents Part 2 of Academy Award, starring Paddle Brian and Adolf Mongeau in Front Page. All right, Hildy. Where's your Williams? Do you bring my money? You'll get your money. Where is he? In that desk. Let me out. I can't stand it.   For the love of Mike Mother. What's the matter here? Okay. It's Mike's mother. What are you doing?   You're doing something wrong. What's in there? Oh, Louie. Louie, come in here. Yeah, boss.  See that she doesn't talk to anyone on the way. What's that? Okay. Oh, Waller, you can't do that. Tell them it's the case of delirium treatment. Listen, Waller, this will get me in a terrific jam. Don't worry, Mother. This is only temporary. Hey, what do you think you're going? Let go of me. I got to get my girl. Your girl? Why, in time of war, you could be shot for what you're trying to do. Don't nuts. There's your story in that desk. Story. We got the city hall where we want them. We're going to crucify those jerks. We'll keep Williams undercover until morning so the morning post can break the story exclusive. Then we'll let the governor in on the capture. He can share the glory. Why you sap? They'll be naming streets after you over this. Yeah. Yeah, but we can't leave Williams here. No, we'll get the boys to move him in that desk over to our office.  Start pounding out a lead. Come on. Snap into it. How much do you want, Waller? Hello. This is Burns. Put Duffy on. Snap into it. What? Hildy, give me all the words you got. Hello, Duffy. I want ten huskies over here at the press room right away. Now, listen, Duffy, I want you to tear out the whole front page. That's what I said, the whole front page out. Hildy Johnson's writing the lead. Hildy.  Hildy. What? You can't get him in here, miss. Get out. Listen, darling. Where's Mother? I don't care if there's a million dead. Duffy, make room for this story. Peggy, I gotta ask you to do something of big favor. You're not coming.  Hold it down. You're doing this to him. He was going and you stopped him. Get out of here. Peggy, I can explain.  Hello, Duffy. What? I don't care. Jump to Louis Kahn, controversy.  Oh, you never did love me or you couldn't talk to me that way. I can't stand it in here. I'm smothering to death.  Not you, Duffy. Put Butch on. Oh, this is the end. I don't give a... Keep it coming, Hildy boy. Get the story out. Hello, Butch. Never mind the audition for the mail train. Hold it up. Stop the presses. Listen, you're not working for the advertising department. Keep on this wire. The patrol wagon, it was on the wrong side of the street. Where's Mother? I should know. She beat it someplace, I guess. So they took her to the morgue.  Didn't you even lock her up someplace? I couldn't, boss. I told you we hit a patsy wagon and I'm that way with the cops just now. Oh, she's dead. Dead. That finishes me. I killed her. I'll let you send her away. Now how can I face Peggy? If it was my own mother, I'd carry on for the paper. You gotta get me out of this desk. I'm joking.  It's better than hanging.  All right. All right. Wise guys. Thought you were going to get away with something, didn't you? We know you got Williams. You can't hide them yet. Double-cross and heal. Let go of me.  Who do you think you are? Busting it here like this. You can't bluff me, Burns. I don't care who you are or what paper you're editor of. Let go of me, Sheriff, or buy it. Let me go. Let go of me, you pox. Hey, he's got a gun. Give me that. I gotta write the carry. I've got it. I want it. Not this gun. This happens to be the gun that Earl Williams shot his way out with. You're under arrest, Johnson. You two, Burns. Who's under arrest? You pinhead. You realize what you're doing? Yep. Same for the mayor, boys. I won't make up with him, mother. Who did it, madam? That man there, officer. Mother, are you all right, mother? What's the idea? What are you cops doing in here? This name says she was kidnapped. That man was in charge of everything. He told them to kidnap me. Are you referring to me, madam? Ah, kidnapping, eh? And I'll tell you something more. I'll tell you why they did it. Please, mother. Come on, Hildy. We gotta get bail. I was in here and they had some kind of a murderer. They were hiding him. They were what? What? Stop.  I'm smothered. I give up. Let me out. Ah-ha, harboring a fugitive from justice. That's him. That's... Oh, you gray-haired old Judas. So you got him, eh, Sheriff? Good work. Good work. Yep, mayor. There they are. Look kind of natural, don't they, with those handcuffs on. Sheriff, you're going to wish you'd never been born. Ha-ha-ha. A sight for sore eyes. Well, it looks like you boys bit off more than you can chew. Yep. Looks like about ten years of peace for them.  These guys are going to be in office about two days more than we're pulling their noses out of the feed bag. I sent for the district attorney. You know what you smart boys will be doing, making brooms at the state pen. I want a lawyer. I got a right to have a lawyer. He'll decal my lawyer. No lawyers are going to be able to help you, Burns. This is the morning post you were talking to. Ha-ha-ha. Yeah. The power of the prep. Sheriff in here? Yeah.  That's your man. Here's your reprieve, Sheriff. Get out of here! You can't bribe me. What's this?  I won't. Here's your reprieve. What? I won't take their graft or their bribes. I'm a family man. Who was bribing you? They were. They wouldn't take the governor's reprieve for Williams. This is a frame-up! Oh, murder, huh? You were going to murder Williams.  A really great man. Now, just step right over to this phone and dictate your true story of how the mayor and the sheriff defied an order of the governor of this state, and were going to go ahead and hang a man that had been reprieved just so they could make a little character before the election. Step right over here, Mr. Pincus. Now, wait a minute, boys. Wait a minute. Maybe we've been too hasty. Let's talk this thing over.  Yes, sir. Right over this way, Mr. Pincus. If you were going to print my story in the paper, maybe you'd like this picture of my wife. Why, Mr. Pincus? How thoughtful of you. A very, very handsome woman. Thank you. Hildy, get on that phone. Hello, Duffy. Listen, tear out that whole front page. Yeah, tear it out again. Hildy, are we really going to New York this time? You know we are, darling. Why, I wouldn't let him stay. Go on, Hildy. Before I make you city editor. Hurry up, Peggy. Try to get that train. He means it. Any objections to my kissing the bride? No. Go ahead. Kiss the guy. Mrs. Johnson, I wish there was time to get you a little wedding present, but wait a minute. This watch of mine. Oh, no, Walter, you make me feel like the bride.  It was a present from the big boss himself. If you look inside, you'll find a little inscription to the best newspaper man I know. When you get to New York, Hildy, you can scratch out my name and put yours in its place if you want it. Oh, you know I wouldn't do that. Oh, go on, Hildy. If Mr. Burns wants you to, you don't want to hurt his feelings. Well, this is the first and last thing I ever got from the newspaper. Well, goodbye, Mr. Burns.   But you're all right. Underneath, I mean. I think you're a peach. So are you.   Goodbye. Hello, Duffy. What's the first stop of the 1240 to New York? That's right. I want you to send a wire to the chief of police. Tell them to meet that train and arrest Hildy Johnson and bring him back here. Wire them a full description.  A little more than a generation ago, drugists had to compound many doctors' prescriptions from natural products purchased in such crude forms as roots, bark, leaves, and seeds. There was no other way. But today, your pharmacist starts his work with drugs which have already been scientifically purified and refined for him. First to produce many such drugs, the House of Squibb has played a vital part in the swift development of the profession of pharmacy. And so today, the uniformity, purity, and efficacy of many prescribed medicines can be traced to the uniformity, purity, and efficacy of the Squibb products used in their making. Your pharmacist, like your doctor, knows from daily experience how much Squibb's standards of quality mean to the cause of human health. He knows that every product bearing the Squibb name is the result of a quest for perfection that never ceases. That's why Squibb is a name you can trust. Next week, another great picture. The House of Squibb will present Academy Awards starring Frederick Marge in A Star is Born. Today's performance of front page was written for radio by Frank Wilson with an original musical score composed and conducted by Leed Stevens. Our producer-director is D. Anglebach. Pato Bryan, whose performance you enjoy today is Hildi Johnson, is soon to be seen in RKO's production Crack Up. Adolf Monju, who played the part of Walter Byrne, may currently be seen in Sam Woods' RKO production Heartbeat. This is Hugh Grundy, fitting you goodnight until next week at the same time when you're invited to listen again to Academy Awards, presented by the House of Squibb, a name you can trust. This is C.D.M. from Columbia, Washington District.


Welcome back to our lecture series Math 1220, characters two for students at Southern Utah University. As usual, I will be your professor today, Dr. Andrew Missildine. In lecture 19, we'll be talking about the idea of improper integrals. This can be found in section 7.8 of Jane Stewart's calculus textbook here. What does it mean for an integral to be improper? Imagine we have some continuous function f, and we're interested in integrals of the following form. Let's find the area under the curve from some fixed finite value a, but we go off towards infinity, right? Visually, we're thinking of something like the following. We have our function. He does something like this, and maybe because the function's asymptotic to the x-axis, we might be interested, well, if we allow this region to go off towards infinity, could it be possible that this is a finite area? Well, it turns out with the right function, it can be, and sometimes it's not, right? What we mean here is we take the integral from a to infinity. Really, this is a limit calculation. Whenever you're working with infinity, really, we're taking the limit of some kind. We're taking the limit as the upper bound of the integral goes off towards infinity. That's what a to the infinity means for an integral. Similarly, we can define the integral from negative infinity to b, right? Again, this really is just shorthand for a limit. Take the limit as the lower bound a goes towards negative infinity, and we compute that right there. In some situations, we actually want a double infinity, right? We could have a situation of a graph, maybe it looks something like the following. It's asymptotic on the right to the x-axis. It's asymptotic on the left. This is like your standard bell curve we see in statistics and probability. Could the area under the entire function be finite? Well, in the case of the normal distribution, the area under the curve is equal to one. In this situation, if you're going from negative infinity to infinity, what you do is you just break this up into two integrals themselves. You go from negative infinity to c, which is defined by this rule, and then you also take the integral from c to infinity, which is defined by this rule right here. Typically, you take c to be zero because that's a good simple choice, but it could be any number you want to. These are examples of improper integrals. Now, as improper integrals are defined using limits, if this limit exists, we say that the integral is convergent. Now, if this limit does not exist, which also includes like maybe the limit does not exist, or if the limit itself is infinity, we'd still say the limit doesn't exist because infinity is not a real number, then we say that the improper integral is divergent. So you'll hear this language, the function or the integral is convergent or divergent. Now, this is describing the integral, not the function themselves. The function might converge towards the x-axis like you see in this picture right here, but the area of the curve could still be infinite and therefore the integral is divergent. Let's see some examples of such things, right? So let's take the integral from one to infinity of x to the negative three halves over, the negative three halves power. Now, by definition, an improper integral is the limit as b approaches infinity of the integral one to b, x and negative three halves here. The reason why we put so much emphasis on the limit here is that the fundamental theorem of calculus does not apply in this setting where you're going off towards infinity. The fundamental theorem of calculus only applies to proper integrals for which this is right here, now a proper integral because b is a finite number, it gets bigger, bigger, bigger, but it's a finite number that the fundamental theorem of calculus applies here. Now, this is a subtlety that's sometimes lost on beginners to calculus, but it is an important distinction here. We can apply the fundamental theorem of calculus in this setting, right? For which as an anti-derivative, we're gonna raise the power of x by one, so it becomes negative one half. We divide by negative one half. Well, of course, this is the same thing as times by negative two, and we're going to evaluate from one to b. So we end up with the limit as x approaches, or sorry, as b approaches infinity of negative two x to the negative one half power. And I'm actually gonna write this as negative two over the square root of x as you go from one to b here. And so when you plug these, notice there's a negative sign, so I'm gonna switch the order. So we get the limit as b goes to infinity of two over the square root of x as you go from b to one. And so then this will look like, because when you plug in the one, you're gonna get two over the square root of one. You don't need a limit for that. You're gonna track the limit as b goes to infinity of two over the square root of b right here. And so now calculating that limit there, square root of one is one, two over one is two, so you get two minus. Well, you're gonna get something that looks like two over the square root of infinity. Now some people will get really scared right now because doing arithmetic with infinity is sort of the mathematical equivalent of doing black magic, right? You know, if we had a chemistry professor that was teaching us alchemy in our chemistry labs, we'd be really concerned about that. Well, this is sort of like a dark numerology that we're doing right now at arithmetic with infinity. But with that, we still get a little bit of a comfort with this. When you divide by infinity, that's gonna give you zero. So two minus zero gives you two. The improper integral is gonna add up, this improper integral is two. The area under this curve as you go from one to infinity is two. It's quite fascinating that even though the length of the interval is infinite, the area under the curve is still a finite value. And we get this two right here. Now, some things I do wanna mention about this is that properly, if you're gonna be a proper improper integral, you should be using this limit notation. But frankly speaking, if most people are gonna feel more comfortable with the following, we're gonna do an improper improper integral. We sort of recognize that, oh, when there's an infinity, that means we take a limit, even if we don't write that. Looks like what do we define this notation to mean? It means take a limit, okay? So many of us are just gonna jump straight to the anti-derivative. We get negative two x to the negative one half as you go from one to infinity. Some people have a spaz attack right now when they see this is like, what are you doing with infinity, right? What does that mean? Well, it means a limit. It means a limit, just like it did here. Why can't we do it there as well? In which case, then the next step looks like negative two x, sorry, negative infinity to the negative one half plus two times one to the negative one half right there. And so again, that people are still panicking like, oh no, what's going on? You can't do arithmetic with infinity. Well, we kind of did already. We were used to doing that. And yes, what it means is this right here. So if we wanna be completely proper, we're taking limits and this is just supposed to be an abbreviation of a limit. So please chillax, take a chill pill, right? In which case then you end up with zero plus two which gives you two as well. So as we go through these calculations, I'm gonna try this more simplified notation but recognize like in this one, you integrate from negative infinity to negative two here. This means we're taking the limit as a approaches negative infinity here of the integral a to negative two one over x squared dx. That's what it means, but that full blown out notation isn't really gonna make much of a difference for us. We can, we're gonna prefer to use the abbreviation that I mentioned earlier. So if we integrate from negative infinity to negative two, well, let's look for an anti-derivative. I'm gonna prefer to write this as a power x and negative two to make it a little bit easier. In which case then the anti-derivative will look like negative x and negative one as you go from negative infinity to negative two. Or if you prefer, we can write this as negative one over x as your anti-derivative as you go from negative infinity to negative two. Like so plugging in the numbers, you're gonna get negative one over negative two plus one over negative infinity. Like we saw before, if you divide by infinity, I cannot draw infinity right now. When you divide by infinity, this is gonna go to zero. And so we're left with what looks like, which looks like a one half, right? So we get one half as our final result right here. As a third example, what happens if you wanna go from negative infinity to infinity? In this situation, it really is important that you break this thing up. Go from negative infinity to zero, one over one plus x squared dx plus the integral from zero to infinity, one over one plus x squared, like so. You do need to break it up because the thing is if you're too careless with the limit notation here, you can actually get something that looks convergent that's truly divergent. So one has to be very careful about this. Now it is the same function in both situations, one over one plus x squared. The anti-derivative is gonna be arc tangent, arc tangent of x, as you go from negative infinity to zero, and you add to that arc tangent as you go from zero to infinity. Arc tangent of zero is itself zero as arc tangent of infinity. What does one mean by that? Well, we're really looking for the horizontal asymptote as x approaches infinity on the right side of the graph. And then you're going to subtract from this arc tangent of negative infinity, like so. And the horizontal asymptote for arc tangent is gonna be a pi over two. And then you're gonna, on the other side it's gonna be a negative pi over two. And so this adds up to be pi, which is kind of fun, right? The area under the curve here is pi. Now one thing I noticed is that as I proposed the slides, there's actually an example I skipped by mistake. I don't know how I did that. I didn't prep it beforehand, but I do wanna, this is an important example to see here. Let's do, this will be example D. Let's do the integral from one to infinity of dx over x. So the important thing to recognize here is we wanna integrate from one to infinity. It's an improper integral, right? So we have one over x dx. The anti-derivative one over x is the natural log. As you go one to infinity. But what happens this time as we plug in infinity? You get the natural log of infinity minus the natural log of one, which the natural log of one is itself zero. So that'll disappear. So the area under this curve is whatever the natural log infinity means, which as we mentioned before, the natural log infinity really means we're taking the limit as x approaches infinity of the natural log of x. So what happens to the natural log as x gets bigger, bigger, bigger, bigger, bigger? This thing is gonna go off towards infinity. So therefore this is an example of a divergent, a divergent improper integral. The other three examples that we saw were examples of convergent integrals because we ended up with a positive number when we were done. Divergence is a possibility and do be aware that if your integral turns out to be infinity, these improper integrals often turn out to be infinity. It is an example of a divergent integral because it doesn't converge towards a number. The area under the curve is in fact finite.


Hello. I'm Mike Rappaport. I work for IBM Research in Haifa, Israel. And I investigate the ways to make containers more secure in general. And particularly the last project I worked on is to allow, is to say how we can checkpoint restore containers or processes that run in an environment with enabled shadow stack. So we are going to talk today about the overview of hardware protections against ROP attacks. And let's start. So historical overview, there has always been a stack overflow, buffer overflow. And according to Wikipedia, it's the oldest and more reliable, one of the oldest and more reliable methods for attackers to gain unauthorized access to a computer. So back in the old days, main security was less of a concern. Stacks were writable and executable. So the only thing that an attacker needed to do was to inject their own code into the stack and make the program, make the processor somehow jump to that code. And they had all the control of the system, of the program. And if it was a privileged program, then all the control of the system. So this is an oversimplified example. We have a function main that has some temporary variable. And it calls the function full and passes to it a string that came from the standard input as a program arguments. What function full does, it copies the string it received as its parameter to another string, which is a buffer allocated on stack. And then it prints the result. Obviously, it's not a real-life example, but it makes it much easier to demonstrate how the things work. So the stack on the upper corner is an example of how stack would look for these two calls. Stack grows towards up in the picture. We have a lower frame for the main function with TMP and it goes beyond below the picture. Then we have CPU pushing the return address from the place full was called. And then there are local variables of the function full. Now if the argument for main was a bit longer than 16 characters, it will overrun into the stack where the return address and the frame of main was stored. And essentially, if an attacker puts a string that will contain a return address to another place, for instance, to the stack itself, and then a string that contains binary code for the attacker wants to execute, as that's what we get on the lower picture. There will be return address to 4F0s and there we'll see, for instance, call to system. It's not a complete example. You need arguments and so on, but in general, it illustrates pretty well that with writable executable stack, you can inject your own code directly onto the stack, make it executable, and from there, you could execute whatever code you'd like to. As time passed, there were much more awareness about security and people started to use all kinds of protections like stack counter is, stacks are not executable anymore, and that is not executable anymore. There is writable executable protection so that writable data is not executable and so on. There is also indemnization of virtual memory layout of the processes. And doing this is quite impossible in the modern world. So to overcome this, bad people found really good way, which is largely called return oriented programming or code chaining or return to library. There are lots of names that refer in general to this thing, to the same paradigm that you inject return, that you find chunks of code you would like to execute in the existing programs. For instance, libc has really a lot of code, so it's easy to find appropriate binary code that will serve the purpose of an attacker. And then all you need to do is to inject a return address to stack so that return address will point to a sequence of code that you would like to execute. And then the sequence, this sequence is called gadget and gadget will end in return instruction. And then it returns back to the original frame and so it goes. So for instance, we have four pointers for different gadgets and they give them the root access. So what happens? The first gadget puts a return address of the first junk of the code. That code runs and prepares arguments, for instance. Then it returns back to the stack. There is a red instruction. Red instruction fetches the address of gadget two. It jumps to the second piece of the code. And in the end, we get essentially the same. Move something to RDI and call system. It will, supposing this address of 40, 40, 40 is string binbush, so we're kind of done. The system is ours. We have a shell kit ready. One of the, and then the researchers worked hard to see how this can be overcome. And one of the things considered one of the fundamental research studies about preventing a rope and similar attacks is a control flow integrity. So as the regional paper stated, the execution must follow a path of a control flow graph determined ahead of time and if there is violation of that path, we should be able to detect it and this prevent execution further. So in a sense, it means if there is a control flow graph, you're executing call instruction, red instruction, and there is no way you should be able to jump into the middle of the function. They have several assumptions like non-executable code and non-executable data and non-writeable code, which is WXRX. And with this assumption, they suggested to validate all indirect jumps and calls by labeling sources of jumps and call, jumps and returns and calls and destinations. And adding instrumentation to each program that will check that whenever jump is executed, it matches the label compiler thought it should jump to. So for instance, if we call bar from foo at the call site at foo, we have to compare that actual target of the call is L1. And when we return from bar to foo, we have to compare at the call site of red that the actual return address will be L2. And, oops, sorry about that. And since instrumentation is a certain overhead and there are more instructions to execute, hardware vendors started to add a special hardware to assist performing control flow integrity. So there is a course green forwardage detection probably I should have mentioned that call is usually called the forwardage and red is usually called backwardage. So there are several CPU vendors that implement a course green forwardage detection. They do some kind of labeling for the call targets. There is an ability in some CPUs to check for backwardage integrity. And these are risk CPUs that have special instructions which we'll cover a bit later. And there is a shadow stack that is a fine grade protection against backwardage attacks. So course green forwardage protection is implemented in ARM64 and in x86. There is special BTI instruction in ARM64 and similar NBR instruction in x86. The compiler has to post these instructions at every target of an indirect call and then CPU can verify that the branch is actually meant to be taken. And if there is no such instruction in the target of a branch that CPU currently executes, CPU will fault and the program will be stopped. This is pretty course green because an attacker can chain several executions of function entries and still find enough gadgets to compromise the system. For instance passing a wrong argument to a function and then returning and then going back. I have to admit I'm not security researcher proper so I might not know some things. But it is considered relatively weak protection and usually it should be combined with back edge protection as well. So how IBT works I pretty much explained it already. So if you have a gadget on the stack that tries to call that using some memory corruption technique a call address was amended by an attacker and it tries to call the code that would do some bad things. The code here starts with that instruction and NBR instruction and the CPU will detect that and it will cause a control protection fault on x86. Now a bit of risk I'll start with power because I understand it's assembly a bit more than arm but this is an example of function call on a risk machine for non-leaf function. For leaf function risks usually use a register to pass the return address. It's called link register. But non-leaf function anyway have to store the return address from the previous frame on the stack and then call the branch linked with the contents of the return address in the link register and then restore everything and move on. So the first instruction here actually takes the link register from the previous frame and saves it on the stack. First two instructions actually then there is a function call which is a BL. And then after the function as a leaf function returns we fetch the return address from stack and put into the link register and return from the original function. Now the stack is apparently vulnerable. There are memory corruptions and attacker can possibly override the return address and gain the control of the system and cause it to execute changes of unneeded functions. So what the CPU can do is to use special instructions that protect the return address with the crypto calculated hash. There is a hash key instruction that generates a hash, it generates key for cryptography, it generates a unique key for every process in the system. And then there is hash store and hash check that assists storing the return address on stack and then verify that return address is correct when the function returns. So the call becomes, we have two instructions added. We store the return address on stack then we add hash st that also pushes the cryptographically computed hash onto the stack. And then after we return from the function, we load, we return from the leaf function, we load the link register value from the stack and then we can verify that it matches what we expected to match. So even if there was a corruption of a link address in the stack, the hash check will guarantee that the program will not continue or it will continue the way it was intended to. A very similar mechanism is implemented on ARM 64. It's called pointer authentication. There are a few differences in how cryptography is handled and where exactly the hash is stored. But on the bright side, ARM 64 has way better supporting Linux than a PowerPC does these days. So aside from generating the key and adding instrumentation to the programs to store and verify the key, there is also ptrace interface on ARM 64 that allows debuggers to access, to change the flow of the program and to jump from one frame to another without being considered an attacker. So this one I didn't understand what STPD and LDP do, but presumed that they also store a link address to the stack and then restore it. And there is special instructions. I have no idea how to read it. The PakiSP and AutiSP that do pretty much similar things what PowerPC instructions did. They create a record, they create a hash that authenticate a point center and then they verify AutiSP verifies that the record for that pointer is authentic.  The idea is to create another stack that only contains return addresses of the functions being called. So whenever there is a call instruction, it pushes the return address to two different places, to the normal program stack and to another place that's called shadow stack that stores only the return addresses. Whenever there is a red instruction, hardware verifies that return addresses in both stacks match and then if anything goes wrong, hardware generates control protection fault. So for example, if we have a stack like that and with return addresses 45570 and 40 and so on, there will be another piece of memory that's called shadow stack and it will contain the return addresses. And in case of an exploit attempt and overwritten return address on the normal program stack, at the time of execution of red instruction, CPU will detect that the new address that the attacker put there doesn't match the original address and it will cause control protection fault and it will essentially stop the program. Shadow stack is not yet enabled in Linux. I think it was like two years of discussion about that. And for now, I think the last RFC was sent about February and this is pretty much summarizes what the last RFC suggested to enable shadow stack for user space. Any program that has a special field in Elf header that generates the generated by GCC or LLVM is known to support shadow stacks so kernel enables shadow stack for that program at loading time. There are features of shadow stacks that are controlled by G-LiP-C so it's possible to override the shadow stack enablement with G-LiP-C tunables so you can say, okay, I do know that this program can support shadow stack but I don't want it today so there is an environment variable you can pass to G-LiP-C to ask for that. Control protection fault is supposed to generate 6x so the program will have to act accordingly and there is new signal code to differentiate the segmentation fault because of, I don't know, other on access from the protection fault. The long jump and the whole family of these calls that also change frames in different ways and function calls, this is all handled by G-LiP-C patches. And there is special handling of SIG return and assumption that only G-LiP-C uses SIG return and for the G-LiP-C flow there is some code in kernel that takes care of it but if your application calls SIG return directly you are going to run into troubles. So this is the link to last RFC into FolkSend. Now for the low level users like G-LiP-C for example or other Lipsy there is a new system call that creates the shadow stack memory area and allocates virtual address space and reserves the memory for it and it also set up the hardware to know where the shadow stack is and then there is an arch PRCTL that allows disabling or enabling a shadow stack on per project process basis and it allows enabling or disabling rights to shadow stack that should be done using a special instruction and what it also does and there is a possibility to say okay to lock the state of these features. So for example I've enabled shadow stack, I disabled rights to shadow stack and then I do lock for the features and then the program from then on cannot change the state of enable or disable for right shadow stack or disable or enable shadow, re-disable shadow stack again. So shadow stack is nice and good if your program doesn't do weird things or if you don't want to debug it with GDP. GDP needs to switch frames in random, might need to switch frames in random order so when you go up and down several frames and then continue execution the contents of the stack and the shadow stack will be different. So what people suggested is to use the ptrace interfaces to adjust the contents of the shadow stack like normal data, that's what usually debuggers do is ptrace.pog data and then there is a special API for ptrace that allows to modify the shadow stack pointer and the hardware registers associated with the shadow stack machinery. So if let's say with GDP you go down three stack frames, GDP will also rewind the shadow stack to the point where it matches this normal stack of the program. Now I also happen to be one of the crew commentators and I actually came to this when somebody on the thread about shadow stack said, okay, we generally break crew and they do. Crew does really weird things with the programs. It tries to checkpoint and restore so we use Sig return extensively. We need a way to restore shadow stack exactly at the same place where it was because we have to restore the process the same as it was before we checkpointed it. After I implemented the first POC with the standalone test program I discovered that I also need to take care of the feature locks that JLPC does because I found myself in a state that I have no control of re-enabling already disabled shadow stack and I'll talk about it a bit later. So a brief sideway overview of crew. What crew does is during the checkpoint we stop task with speed trace, we inject parasite code into the victim pretty much like any virus do to extract essential process state that is needed. After the process state is extracted and serialized to disk most probably we call Sig return with the frame crafted so that the victim will return to normal execution. And on the restore site we clone the task from the crew controller program. We restore the task state from the saved state on the disk. Then we clone all the threads that were originally present in the program. And each thread calls Sig return to return to the normal execution. Again with the crafted stack frame which wouldn't match the shadow stack in any rate. So the first thing we had to do is to be able to do Sig return. Otherwise the crew would stack and there is control protection fault and nothing to do about it. So with the interfaces that GDB is ought to use we were able to achieve pretty much the same functionality. The stack on the right is the stack of the victim. And then the lower part is the stack of the program itself. And the upper part is the stack of the parasite code that we inject. So the code that is injected is not called with call. We just jump there. And we jump there using set rex with Petris. So there is no shadow stack indication that we are going to call these functions. The upper part of the stack is reflected on shadow stack. But the first function we called with the set rex will never be there. So we used Petris to inject this new frame into the shadow stack. And that allowed us to continue using Sig return as previously without doing too much intrusive things in crew itself. So essentially when we stop the victim with Petris, pretty much one of the first things we do, we inject the shadow stack frame to the shadow stack. The next challenge was to be able to restore shadow stack exactly as it was before the checkpoint. What I needed was to extend my shadow stack function call with functionality similar to MUP fixed so that shadow stack will be allocated at exact address. And then there is a lot of hoops I had to jump to be able to use that WRSS instruction to write to shadow stack. But it was pretty much technicalities. But so what crew does for program with shadow stack enabled, we do MUP shadow stack. We use memory aside to store all the contents of the shadow stack that was check pointed originally. We enable shadow stack to be able to use special shadow stack instructions. And then we copy the shadow stack contents from the stash to the shadow stack memory. And then we update the shadow stack pointer using again special instructions CPU provides. And the last things that I found pretty late in the process that I also have to deal with the feature enable, disable controls.  Whenever you see what shadow stack enabled program, it locks the features on the state shadow stack enabled, writes shadow stack disabled. And it still worked with the original model where we enable shadow stack at some point. But the problem, it didn't work the other way because whenever on JLip see lots of programs that doesn't have shadow stack health field in the health header, it locks shadow stack on disabled. And then there is no way crew could re-enable shadow stack. And for that, the current discussion was that we need the new Ptrace APIs to get and set the state of process shadow stack controls. I did something for my POC out of everything. I hope that Intel folks that work on the shadow stack will come up probably with better API that will be more useful. And we'll see in the near future. So it remains to be seen when and how shadow stack and in the upstream kernel eventually, I don't know what it will feel like the next patch that will be just accepted. So it's more work to do. Afterwards we'll need to refine and complete crew implementation. And we also started to look into how to use shadow stack hardware for kernel itself. Looks like it's a lot of mess. And truly it won't be easy. But we keep our hopes high. And I'm sorry, I couldn't connect to internet so I had links to crew and kernel patches I have at the moment in the more updated presentation. So I'll post it on the open source summit website. And that's more or less all what I have. So I noticed one of the things you pointed out in the presentation was being able to disable processes from using like the WRSS instruction. Can you repeat? I noticed one thing you pointed out in the presentation was that there was a way to disable processes from using like the WRSS instruction. Doesn't that restrict the functionality? A lot of them like it would break the ability to use long jump and things like that. Then would it be something you wanted to do? I don't know how exactly G-Lipsy hands long jump. I just trust until they do. But if you can allow writing shadow stacks, so essentially you've done nothing. Because at the same time as injecting, you can find a gadget that writes to shadow stack, right? And at the same time that you inject something to the normal stack, you would find a way to execute that gadget. So allowing shadow stack writes weakens significantly the shadow stack mechanism in general. Thank you so much.


How are you? Nice to see you. How are you? Good to see you. Good to see you. Later? Thank you. Just one. I want to go to get a half an angel. I have. Well, I think before I do this again, I want to say that once again Jim Brady has been the catalyst for writing a wrong for inspiring and improved a lot of others. I'm pleased to be able to sign this bill today that leaves restrictions on aid to officials hurt during events such as the one of the hill in the year I saw ago. March 30th. Jim's ordeal in the year that's passed is focused. I appreciate that. I appreciate that. That's your mungage, I mean. Yes. Yep. We've got to get it around television. Programming. I think that's a good way to do it. One more. I'm going to mention Larry. In June, the second to right. How are you doing? Good to see you. I certainly do. It's been a while. Nice to see you, sir. How are you? Good to see you. Good to see you. I'm sure. Oh, I'm looking forward to it. The painting stuff. Hello, Elvis. Well, I I'm good to see you, David. Good to see you, sir. I think I'm home. I just want to say thank you. Thank you. I'm happy to see you. I'm happy to see you. I'm happy to see you. I'm happy to see you. I'm happy to see you. I thought you had a great time with your面. Yes? That was mainly work there? It was useful. Was it useful? Oh, yes. Yeah. I'mrah President. Elvis Mason from Dallas. Hello, David. Good to see you. Hi. President, on one level, my life's purpose has been for the building, so I'd be a delegation of bankers. Why does work with the President about hardly economic problems? Kind of addiction, I mean, not everybody hears a thing. I'm afraid that's true. David Racken and I were talking about the theory of addressing the issue on a longer-term basis when we make a constructive contribution. I told Bill, told him about the idea, and he encouraged us to go ahead. We've had three luxury meetings, busy group, everybody clear.


Let me get started. Hello and welcome to the introduction of 47 lining enterprise path a push fund deployment of the OSDU data platform available now on AWS Marketplace My name is Eric Putney and I lead the 47 lining enterprise path team This team is responsible for software as a service and consulting offerings that accelerate business value through adoption of the OSDU standard and data platform I am joined by Mick Bass. Mick leads the 47 lining team and serves as our forum focal point 47 lining is a boutique consultancy and software as a service development business within Atachi Vintara We help industrial customers transform their business through data platforms in the cloud We have been working alongside AWS and other forum member organizations since 2018 We worked directly with Shell to package and make their original STU contribution available to the OSDU forum And worked with Shell, AWS and others in a cross-forum tiger team to first demonstrate multi-vendor workflows atop the OSDU data platform Within the OSDU ecosystem we act as an OSDU data platform provider Our focus is on fulfilling, maintaining and supporting operational instances of the data platform in both software as a service and platform as a service models Making it cheaper and easier for you to evaluate and use it 47 lining Enterprise Pass makes OSDU adoption fast, easy and efficient 47 lining Enterprise Pass provides a push-button deployment of the latest release of the OSDU data platform within a matter of hours of your subscription Since we started working with the OSDU forum, we've put a lot of thought into the operational aspects of the OSDU data platform What are the best deployment mechanisms? What is my path to production with OSDU? What is the most efficient way to operate the data platform of this scale? Do I do I need to set up my own ops team and host it myself? How will I validate and roll out upgrades? With 47 lining Enterprise Pass We address these questions to help you along your journey by giving you easy access to on-demand instances of the OSDU data platform a consistent developer support channel and solution prototyping experts that specialize in upstream energy industry workflows At 47 lining we have experienced the inherent complexity that comes with the platform from of this scale and the resulting pain points For example, consider in installation and configuration of the platform so that developers can begin to use it This is by no means a trivial set of activities and in our experience It is easy to underestimate the sustained effort required to stay on top of it Our fully automated pass in SAS fulfillment models ensure the platform is reliably and consistently available to your developers So they have the tools they need to start using the OSDU data platform right away We include a developer support channel so your team can stay unblocked at critical junctures without wasting valuable time We understand these issues and been through them ourselves We want your team to be solving the hard problems related to your application and work flow workflow development Instead of getting bogged down with questions of how to host install and maintain the OSDU data platform We enable your team to stay focused on the value drivers within your organization 47 lining enterprise pass will allow your team to focus on your OSDU adoption strategies and best ways to include OSDU capabilities in your product development roadmaps 47 lining enterprise pass is available now in AWS marketplace It uses a SAS based subscription and fulfillment process to deploy an on-demand OSDU data platform instance Dedicated to your team within a matter of hours The 47 lining team will take on the responsibility of keeping up-to-date with the latest milestone releases offered by the OSDU forum We are continuously adding useful features to our deployments that enhance your OSDU experience From front end use from front end UI's to get you started documentation with example API requests to cost saving resource management features the 47 lining team strives to provide simple easy to establish cost-efficient supported maintained access to the OSDU data platform that provides a superior experience for developers and product owners We encourage you to discover us in AWS marketplace or reach out to us directly and we look forward to embarking with you along your OSDU journey Thank you for your time now. We'll play the introduction video that describes the OSDU adoption with 47 lining enterprise pass Afterwards, we should have some time first Q&A as well As oil and gas workflows are digitized operators and ISV's Recognize the need for industry interoperability across tools and cloud data platforms But using various digital tools will not work when everybody has their own file formats and storage locations in response The industry developed and launched the OSDU standard and open source data platform code base 47 lining enterprise pass aligned to the OSDU standard makes it easy to get started with the OSDU data platform Enterprise pass helps you demonstrate how your existing applications and workflows can create and consume data from the OSDU data platform And enable your developers to create new application and workflow releases that work reliably with it Enterprise pass also allows the roadmap for your applications and workflows to deliver more value through interoperability enabled by the OSDU data platform and easy access to a vibrant ecosystem of suppliers and customers at the same time Enterprise pass removes the burden of having to figure out the entire open source code base or Create a new operations team to install Maintain and support your OSDU data platform deployments by subscribing to 47 lining enterprise pass in AWS marketplace Your developers can begin working with OSDU data platform APIs for ingest search and store in less than a day This keeps them focused on learning about the APIs and refining your roadmap and development plans Once you have a clear definition for your target workflow You can use 47 lining enterprise pass to support your software development life cycle Streamline your release and customer support processes access more customers and keep them happy The 47 lining production foundation offering provides the capabilities enterprise developers need Including access to multiple OSDU data platform milestone releases support and sandbox environments By using a common data foundation digital tools can work together to answer your most important questions and Help make the entire ecosystem more efficient and profitable To get started subscribe to 47 lining enterprise pass in AWS marketplace


Linda asked a need help creating a calendar more like overlay, but on click, I want to display multiple events. For example, I have three departments and buttons for each calendar and click all shows all, and when I click one shows only one of the events. How could I do that? As always, thanks for your help. Thank you. I'm trying to work out, because I, in terms of displaying an event, because I mean a calendar is about all things. It's not about a specific event. Because when you go calendar. What comes to mind are the calendar overlays that were in classic SharePoint that they don't allow anymore, but they're not working the same way. The only way to roll together calendars now is using Outlook, and you have a group calendar in Outlook, and then be able to overlay them with the checkboxes. That's the only way I can think of. Yeah. When they're saying three departments, where are those calendars, where they live? Yeah. I mean you can create your calendar, if you're doing it through Outlook, creating your calendar group, and then you can do the, in your tick box where it ticks all of them on. But then that's pre-selecting your calendar. Hold down your control button, choose the dates that you want, then click on your calendar group, make sure it's in overlay mode, and they're all sitting there over the top of each other kind of stuff. But that's an Outlook functionality, not necessarily a SharePoint functionality to be able to show that. Yeah. Is there any? Thank you Microsoft for taking that. Yeah. Because that was something we used a lot. In fact, I wrote a chapter on that with 2010 for the 2010 book. Yeah. That was one of the topics I covered. Yeah. Yeah. Is there any way of doing that without a third-party tool in SharePoint today? Not that I know of. Not that I'm aware of. But I mean the only thing I would highlight, I would go ahead and defer to Christy if you want to say it. If you want to go over what you just said, and just say the only workaround that we know that I know of is in Outlook. The full desktop, because you can't do it in Teams, because you can't see other calendars into. You can only see your own in Teams, so it has to be Outlook as your application, then of choice to be able to do anything functionally with your calendar. Really. Yeah. Yeah. And they keep trying to take Outlook away. We'll storm the castle just like when they tried to take away one note. Who tries to take away? They keep saying they're going to give it out. Yeah, but Outlook's going away. You should be working in Teams 100% all the time. Who says that? I haven't heard that. Microsoft. Now, I'm calling the team people. Yeah, it's like the Yammer people said, we're going to kill Exchange. And we were like, yeah, how'd that work out? And I call the same bluff on the team's people if they're out there preaching that. If they sign that. Not going to happen. No, everything I always hear is Outlook is not going away because everyone keeps panicking that they're trying to push them into teams. And yeah. I put it in the same category as SharePoint on-prem. Like it's not going away. There's no roadmap for it as long as people want it. Look, if people stop buying and installing Outlook, then yeah, Microsoft will make a business decision, but we're nowhere close to that. No. It's still one of the top applications. Yeah, it's basically that external communication piece.


These days to get attacked all we have to do is step foot off campus and tell anybody even a local Qantas club or a local church or even a group of elementary school kids that climate change is real and then the angry letters start to flood in. Typically the attacks are not really about the science. The attack on the science is a proxy for what is really an effort to discredit science that may prove inconvenient for certain special interests. That's when I started getting attacked and that was when life sort of changed it was a bit like you know going through the looking glass. I started getting hate email. What happened then was I mentioned to a couple of colleagues what was going on and one of my colleagues at Scripps at the Scripps Institution of Oceanography said to me you should talk to Ben Sander. Something sort of similar happened to him. I remember sitting in a bar in Madrid with Stephen Schneider at the late Stephen Schneider immediately after the final sentence had been agreed on in the 1995 report. A sentence that's forever engraved on my memory. The balance of evidence suggests a discernible human influence on global climate and here we are at this bar and Steve says to me this changes everything you know your life is going to be changed forever and I had no idea what he was talking about. I really didn't. There is definitely a pattern of what happens. Nasty emails, complaints to your university, requests for your emails and a lot of attacks online. Often it takes the form of an attack on individual scientists. There's a part of you know the strategy of ad hominem attack.  Make life miserable for them. I have received letters in the mail and that in one case contained a white powder that I had to actually report to the FBI. They had to come to my office and investigate this and send this off to a lab to make sure that you know it wasn't anthrax or some very dangerous substance that my entire department would have been subject to because of this. Then there's the power of the Internet which really was not available back in 1995 to harness your supporters to go after individual scientists, send them threatening emails or worse and let them know we're watching you and we don't like you, we don't like what you do. One of the tactics that you see in sort of climate change denialism is an effort to spin and misrepresent peer-reviewed scientific studies. So often studies that say one thing for example show that you know some aspect of climate change is you know even worse than we thought will somehow be spun by climate change deniers as if it you know doesn't provide evidence for concern. Clearly misrepresenting scientific information, cherry-picking scientific data. One egregious example that we talk about in the book is an early work by Jim Hansen that Bill Nirenberg, Bob Jastrow, and Fred Seitz take out of context and use it to argue that climate change is caused by the sun when in fact if you go back to the original paper Hansen is arguing exactly opposite. I think an additional weapon in the arsenal is freedom of information act requests which are being used not really to advance understanding or again shed light on complex scientific issues but as a tactic to threaten to intimidate to throw a spanner in the works to take up your time. They will bully editors to try to get them to retract articles that are a threat to their case, their case being that climate change isn't real it's not something to worry about. The weirdest day of my whole life practically was the day I got a phone call from a reporter in Tulsa, Oklahoma who said to me are you aware of the fact that Senator James Inhofe is attacking you? I was like at that time I honestly didn't even know who Senator Inhofe was in fact I think I'd been to Oklahoma maybe once but I mean so yeah and I said no I have no idea why I mean I first I thought he was making a mistake like this was some other well I have a very unusual name so it didn't seem plausible it was some other Naomi Oreskes you know yeah and then he had he read to me from the speech that this that Inhofe was making you know and it was part of what we all are very familiar with now that I was part of the global conspiracy the scientific conspiracy to bring down global capitalism and I remember thinking conspiracy scientists are not that organized. Hacking emails releasing them all of these things yeah the technology has moved on since 1995 but it's the same playbook don't really focus on the science and advancing understanding contributing but tear down destroy. What I think the best we can do is shield ourselves from the attacks and try not to dwell on them unless it's a safety issue in which case we take appropriate steps and try to move on focusing on what we want to achieve rather than what's trying to hold us back. So if you are a prominent scientist if you participate in the public discourse as I've often said you better develop a thick skin because you will be attacked personally. So my number one rule of thumb is do not Google myself I don't want to see my number two rule of thumb is do not read the comment section I don't want to know. One of the things that I think is really important is that by writing about these things and by documenting it and by writing about it in a scholarly way you know with high standards of documentation we can explain to our colleagues or institutions editors a journal and the public and the media what this is because this is not a scientific debate I mean if I have one message that's what this my message has been all along and it still is this is not a scientific debate it's a political debate but it's a political debate being made to look like a scientific debate. We now know why people do that because it's a very very effective strategy because if you can make people think it's a scientific debate then people think it's too soon to act but if people see the truth if they realize that this is certain if it's a political debate that it's related to people's ideologies to their values structures that gives a whole different cast so it's very very important for people to understand the character of what this thing is. Some things are worth fighting for and that perhaps was the most profound lesson for me back then that a clear public understanding of the science doing the kind of thing that you're doing here that was truly worth fighting for.


If I were to highlight what I would consider the most important message, the message is what I was just speaking to a bit, and that is each of us as human beings, we have such a deeper identity than most of us are typically aware of. And when we don't live from that more fundamental identity, then we live in a world of separation of me and you and us and then and so forth. When we begin to embrace the journey of consciousness development, of spiritual journey, to really understand our true nature, as people call it, sometimes it's called the true self or the capital S, then the prior perceptions of separation begin to dissolve away naturally because now we've come back into residing in that more whole, unitive nature of our existence and everything changes from there.