Hi everyone and welcome to the Stock Swoosh Play of the Day for July 11, 2016 presented by thestockswoosh.com and this is Paul Lang. Today's play I had the play today and it was on CHRW. This daily chart you're looking at is provided by eSignal, the beautiful charts that we use and the CHRW daily chart had an opening today that was gapping down to right there and that opening created a bearish scenario on our 26-point ranking system which allowed me to come in and look to short this on an intraday pattern. On the intraday pattern I saw, I'm going to go to a 1-minute chart now of CHRW, you can see this gap down in here and this CHRW 1-minute chart gave me exactly the pattern I needed to see in order to short and to capture that move down shorting up by that star up in there. It had a relatively tight stop for this type of a stock, it was a 37-cent stop which means that a 3,000 share amount ended up with a profit of 25.65 was taken on two exits down here as the stock dropped, one of them just off the low of the day at the time and I'm going a little bit lower later in the day as well. So overall nice play on CHRW, 1-minute chart. The little lesson today that I want to talk about is that you should know ahead of time exactly what it is that you're looking for in terms of the overall setup and in terms of your entry. Once I see this particular type of gap I know exactly the entry that I need to see in order to take this gap. You can't be chasing your entries, you can't be chasing plays, you have to let them come to you and you have to know ahead of time exactly what it is that you demand the stock do in order for you to take a position in it. For those of you interested in learning plays like this, this strategy is from the Golden Gap course. This is a golden gap and we teach this strategy in our course. The next class coming up is going to be Saturday and Sunday July 16th and 17th. This is a full two-day course where you can learn over the entire weekend. It's a unique course because it focuses on one and only one strategy to trade the market. It focuses on the first 30 minutes of the day. It uses a very specific 26-point checklist and allows you to ignore the market most of the time and also gives you time away because you are done trading early in the morning. You can call 929-3200 GAP or email Melissa at thestockswitch.com if you're interested in this course coming up this weekend.


Good morning. I'm Mary Ellen from the channel Mary Ellen after 60 I'm here today to chat a little to talk about what's new and to talk about some old products of mine that really made me happy. I Do want to say Jim and I are fine. We are both staying in the house and And not going out and about we are prudent, but we're not Panicked at all This is the first time both of us have thought of ourselves as the older generation And I am in good health and Jim does have some underlying conditions So I want to be especially careful and so does he any of you who have watched me for a while Won't be surprised that I always keep backups Not only of my skincare and some of my favorite makeup products, but for the kitchen and for the bathroom I've just always been that way before I open my last thing of laundry detergent. My backup is here I realize that a lot of people are going through things that I have no idea about. I do pray for our country for our nation But with me for me as long as I have God It is all good and one of the first things we learned in nursing school many many years ago The best way to not spread an infection is to wash your hands and and that skill applies I really wasn't sure if I was going to upload a video for this week and I was just thinking about all the things that make me happy and Most of the things that make me happy aren't tangible But I just want to share with you some makeup that I've had and a lot of this you can't buy So many times I come to you like today. I have on mascara and navy eyeliner in my upper water lines lipstick and Clear brow gel. I don't have any other makeup on just skin care and this is how I do it a lot I probably wear a full face of makeup Well, what I call a full face of makeup probably three or four times a week I want to mention a couple of weeks ago I filmed a video and I don't know if it will be up or if it won't be Yet, but it's for the IT cosmetics today special value and I also Reviewed the blend of all tauti's blend of all so if it's been posted I'll put it up here and if it's and if it hasn't been just watch out for it I know it will upload before March 30th But I never know for sure if they're gonna have a presale or not So I just kind of wanted to mention that until probably about Eight years ago. I never owned a brow product I would spray hairspray on a brow brush and that's what I did for my brows Well, I found this probably eight years ago. It was before I knew YouTube Videos existed and this came from Urban Decay and I still have it and it is brow powder I even still have the brush But there it is it makes me happy because it was perfect. It has I don't use it I could I would if I needed to but it has it has wax here I wouldn't use the wax, but if I needed to use a powder I would but it even came with a little brush I still have the brush and It just makes me happy and I will probably not ever throw this away So you seldom see me when I am dressed up go in someplace Especially if I'm going out at night you don't see me So there are some of the products that I have here that I use when I kind of Get more Glammed up this probably makes me happier than any Again before YouTube there was something that came out from bare bare minerals called the phenomenon And it was supposed to make your Iris of your eyes stand out more than any other eye shadows And I just couldn't wait to get him and I finally did and I've got the little Sponge applicator and those are the colors and I their shimmery They look fabulous on the lid and I've used them a lot And I know I've shared with you in the past that I always I don't take when I do my brush or sponge I go around the sides because my I don't like to hit pan. I really don't Something I do and it's not necessary, but I'm real particular around the eyes with anything that I use around my eyes So whenever I'm using a brush I just have this little tiny thing and any of my eye brushes that I use go in there And then when I leave my dressing room and go in the bathroom, I take them with me and I wash them That's maybe why I don't wear eyeshadow all the time because I don't have but it's never a problem Because they're so easy to clean if I clean them every day and I don't I don't use that many brushes I saw this duo on Amazon and it was just like Ridiculous, I think I had it in my Amazon store and took it out because it was just like super super expensive But I looked for about a year before I found this and I'm glad I did I love the oh Becca opal I liked it so much that when I saw that there was a mini size and that makes me happy when there's minis There was a duo and at the time I bought it. It was twenty five dollars. I think and it's for a kind of a liquid blush And then the mini opal and this looks so pretty on your cheekbones I'm not very good at swatching, but this is what it looks like and then when you share it out It just has a really pretty glimmer Really kind of a shimmer, but it's not chunky and it doesn't accentuate any fine lines But this makes me happy and it makes me happy when they make minis I have some full-size hourglass blushes that you know, I like well something. I love about hourglass You can buy minis and this is the mini and it is in the fused heat and it is a beautiful blush I like that and again. You don't see me in these. I love it when companies make minis. It makes me happy. I love tart blushes and I bought this beautiful palette from Tarte Probably a couple of years ago and what I like about it when number one I think Tarte makes great blushes, but I loved the shades and sometimes, you know You always see me in cooler colors But sometimes I wear something that I need to pull in just a little bit of warm I will run my brush over all of them and Shake it off and put them on my cheeks And and I just think it's beautiful and I've used it a ton and it still has the imprints on it a Dear friend bought me the fairy dust And it doesn't look like it would do anything but it is gorgeous. I've worn it down I don't want to hit pen, but I may I'll keep using it You can't get too much of it and it doesn't even look like it would do many do much But it does a lot and I love it. It makes me happy. Just look at I know you can't buy these But just look at all those little shimmers in there this eye shadow I purchased well before I went cruelty-free. It was probably Six years ago and it's from Elizabeth Arden and the shade is called rain and For me it is a perfect shade of gray and I use that a lot at night Don't really do very many day looks with it, but I just love it and I think it's beautiful and it makes me happy Now the balm eye shadows always make me happy. I used to have some of the balm The balm I'll type it up here. I used to have some of their blushes and they were wonderful My understanding you can either order from the bomb's website or Culls if you go in a culls they cover they carry the balm But they're just cute packaging and just look at these eyeshadows So anything from the balm makes me happy and the last thing I'm going to talk about is one lipstick And it's this lipstick right here from our class and I bought it a couple of years ago I have it on today. This is called if only I Like it so much. I have a backup and I have another shade They come like this you buy the refills and this is my icon is and I It is a beautiful blue red and and I like to have reds that have some blue Oranges in my color at all So I just love to carry this in my handbag. I like putting it on it It's just lovely. It really is and it makes me happy And if you're still here, this is going to be a giveaway and everything I purchased except for one thing And I'm going to go ahead and tell you why I purchased what I purchased I watched a video from Emily Noel and I watched all of Emily Noel's videos And she did an excellent video on magnetic eyelashes I'll either put a playlist or I'll put a link in below of The false eyelash videos I've done I've worn false eyelashes one time and I did it on camera put them on a camera Couldn't stand the way they felt and then I bought some magnetic Eyelashes that kind of clamped and I did a demonstration. I really like those. I lost a couple of them So when Emily did the video on magnetic lashes, I knew I wanted to order some of the magletic mag I knew I wanted to order some of the magnetic eyeliner So I ordered myself some and I ordered you guys order two for two of my winners But I want to show you what I did with mine. This is how they come packaged and I cut mine into I Saved the smaller side You see I cut a longer piece and a small piece and I had to cut it right next to the magnet because It really bothered me in here. So what I've done when I put on the eyeliner I just put it from like here over and use this shorter strip right here and They are very comfortable that way. I think maybe my eyes are just I mean I guess I'm just not used to anything on my eyelashes except for mascara I've got two of these in my giveaway and then I have two boxes of three of the Buxom lip gloss and I'll show you the size I love Buxom lip gloss. They're that size These I got when I subscribed to Fab Fit Fun. They're the wonder beauty the eye patches the baggage claim gold eye masks I've heard nothing but good things, but I don't want to start using masks That's just something else that I'll think I need to buy but I'm going to give them to you And then when Lisa J sent me the brushes, she sent me two of her sponges, and I don't use beauty sponges So each person is going to get eyelashes a beauty sponge to baggage claim eye masks and the false eyelashes Emily did such a great job Demonstrating on how to use these I'm going to link her video below She did a fabulous job So I thought why should I even try as always this is an international giveaway Since it is a giveaway, I cannot reply to the comments But you know if you go to any video even if it says I can't if it's at least a week old I can get back to you quickly to be in the giveaway You just have to be 18 years old or older be subscribed to my channel before this video goes live This giveaway will close in three days as usual So my subscribers can actually be the winners and all I need to know if you want to enter is in the comments section Just tell me something that makes you thankful and hopefully the other viewers will be able to read what you are thankful for And we'll be able to help each other along the way. It is all good It is even in these trying times It is all good. You all take care be careful and I will see you in my next video Bathroom I have a I have a And I'll wear it for me Jim is the first person It's it's


Good afternoon everyone. It's my great honor to share our work, HotBPF Plus Plus, which will provide more powerful memory protection than prior work, HotBPF presented last year. This is a joint work with Dr. Yue Qichen. Unfortunately, he cannot make it here today because he needs to attend a university commencement ceremony. I am Zicheng Wang, currently a PhD student at Nanjing University and visiting University of Colorado Boulder under the supervision of Dr. Yue Qichen. My research focuses on operating system security. Since we are in the Linux security summit, so there is no need to further emphasize the importance of Linux kernel security. The vulnerability lifecycle consists of mainly four steps. The vulnerability introduced, discovered and patched, merged and developed. There are various techniques available to protect the Linux kernel, for instance, on the left. Tools such as cell color and state analysis have been developed to discover kernel vulnerabilities. On the right, after a patch is available, vulnerabilities can be fixed. However, there is a time window of at least 66 days between the discovering of vulnerability and the patch availability. During which the kernel is left vulnerable and unable to protect itself. We haven't seen much practical protection during this period. This is where HubBPF++ came in. Our work is quite straightforward as HubBPF++ generates EBPF programs automatically to prevent triggering errors without the need for patches. Before we describe all the technical details of our work, let me first present its overview. The vulnerability on the error site is triggered by a malicious process through a system call. And after the attacker triggers the vulnerability, the entire system will be compromised. Our work HubBPF++ can prevent the vulnerability on the error site from being triggered by loading a BPI program in the kernel space. The BPI program will be executed every time before the error site. And check if the current context meets the triggering condition of the vulnerability. If not met, nothing happens, the kernel will keep functioning, but if the error condition is met, the BPI program will help kernel skip the error site and jump to the return of the function and send signal keel to stop the malicious process. After that, kernel will return to the normal condition and keep functioning because BPI++ focuses on the accurate error site rather than the entire kernel. So it's lightweight and efficiency. Before I dive deeper, I will introduce the input of HubBPF++, a report generated by SetColor. SetColor is the most widely used kernel father developed by Google, which constantly generates randomized new inputs to detect the crashes in the kernel. And the kernel is compiled with sanitizers. On the left is the SetColor dashboard. When a corruption is detected, the sanitizer collects the information about the error and reports it to the dashboard. We can observe that many types of bugs are reported. On the right is the SetColor report. The bug report input a list of information such as the type and the position of the bug, and the code tree that illustrates how the bug instruction was called. In addition to this information, there may also be the proof of concept and the kernel configurations to reproduce the crash. This data helps our work to identify the error site and construct the triggering condition. HubBPF++ is built on the EBPF, the extended Berkeley packet filter framework. It's an internal virtual machine that allows users with root privileges to load programs into the kernel space. The BPF framework also includes three essential components, the verifier, the JIT engine, and the help functions. The verifier is responsible for verifying the installed BPF bytecode and ensures the memory safety, determination, and information flow security. The JIT engine enables EBPF bytecode to be executed just in time for achieving native machine performance. And the help function provides expressive interface between EBPF programs and other kernel subsisms to extend the EBPF feature. EPF also provides hook mechanism based on the K-Probe, which enables HubBPF++ to attach arbitrary error site in the kernel without recompiling the kernel or rebooting. EPF++ leverage these powerful capabilities of the framework to detect and prevent the kernel vulnerability with high efficiency. Next, we'll introduce the workflow. HubBPF++ takes bug reports triggered in the Sinitizer kernel. We can see the laptop. As input and generate the error prevention EBPF program as output, and the workflow includes mainly five steps. The first step is to extract critical bug information from the report. And the second step is to map the error information from the Sinitizer binary to South Code because there is no direct mapping from the Sinitizer kernel binary to the runtime kernel binary, so we have to use the South Code line as a bridge. And the next step is to map the error information from the South Code to native binary. Where we will pull BPF program out and detect if the bug triggering condition is met. Both the translation process from Sinitizer to native and native to Sinitizer based on the kernel debug information, the wolf. And the fourth step is to construct triggering condition as a native kernel binary, such as check the one-bit related registers and memory address. Finally, HubBPF++ senses all the information about and generates the BPF prevention program. We will use the example to describe the workflow. This working example is a heap or a slab out of bound vulnerability that can lead to a serious security issue in the kernel security app armor module. The triggering condition for this vulnerability is shown in the line 645 where the length of the array ARGS is defined as size, but you see the index dark up from zero, so the last index can be written as size minus one. But in the line 645, the index size is written, so apparently there is one bit of overflow. Attackers can use this simple overflow to get the root privilege and crop the entire system. And HubBPF++ prevents this error from being triggered by checking if there is an overflow at line 645. If the triggering condition is met, the BPF program helps the kernel skip the line 645 and it jumps direct to the line 693. Returning the error code, this makes the kernel believe that the function has failed and it kills the error handler in the cost stack until return to the system call. Next, we will use this one bit to show how the BPF program generates how the BPF++ generates the BPF program from the bug report. To generate the program, we need to locate the error size in the runtime kernel binary where we can, as shown in the workflow on the laptop, also we have a report collected from the same time the kernel as I described in the technical background. There is no direct mapping between the same time the kernel and the native kernel binary. Therefore, we use the south code line to bridge the two banners. We can use regex to extract that the one bit is a slap out of bound error and triggered as the address of the function app-armor-set-proc attribute plus hex 116. We first locate the error site in the south code line using the same time the binary devolve info. Then we use debug information to locate the error instruction in the native kernel where we can check if the error condition is met. The results show the probe address is function app-armor-set-proc attribute plus hex 8f in native kernel and number 0 will be written to the address register RSI plus RDI times 1. After locating the error site in the runtime kernel binary the next step of hotbbs-plus is construct the triggering condition to detect if the vulnerability is triggered. For this case, the triggering condition is when the pointer address is out of the legit range of the object it refers to The pointer referred address is calculated using the register RSI plus RDI times 1 and the RSI is the base address of the pointer and the RDX is the opposite of the pointer. To get the legit range of the object we implement new bpf-helper function to get the start address and the length of the object when we have the base address stored in the register RSI. The last step is to synthesize all the information and generate the bpf-program The bpf-program is probed exactly on the app-armor-set-proc attribute plus hex 8f just the way presented and every time when the CPU is going to execute the instruction the bpf-program will be executed first to detect if the triggering condition is met. We present the sample code of the bpf-program First, the program obtains the object's runtime size and then check if the error condition is triggered and last, if the triggering condition is met the program skips the error site and returns error code to the caller set and sends a signal keel to the vulnerability user space Proof of concept program and we will show a demo how the bpf-platform solve this problem solve this vulnerability The demo is on 5.15 kernel version and the vulnerability CVE-20166187 is imported to the kernel because it's too old but it's still working First, we will run the proof of concept program on the sanitized kernel to corrupt the kernel as we presumed Is it start? Okay, it's start First, we run the proof of concept program on the sanitized kernel to corrupt the kernel as we presumed As we've shown here, it's a set of caller reports we build a sanitized compiler option on it and here is the error type and the triggering site also we can deduct the triggering condition Then we start the hubbvf++ to prevent the program from being triggered On the left side is the proof of concept and on the right side is the bpf-prevention program We start the right side bpf-program first and then we run the malicious process We can see in the left the malicious process is killed And on the right side, the bpf-program has detected the error is triggered After that, I run areas to check if the kernel is still keep functioning Yes, it is a simple demo and the kernel is still keep functioning So in conclusion, we think there are five advantages of the hubbvf++ system First is protect the kernel when the patches are unavailable and the hubbvf++ is end-to-end system The bpf-program is automatically generated from set of caller reports and it has no interrupt to the kernel execution The bpf-program can be installed at the runtime on the fly without recompiling and rebooting the kernel and it has negligible performance overhead and memory overhead This result we will show in the following slides and we have to say it is easy to be extended We can use it to support policies for other vulnerability types Next, we will show some technical details Our work hubbvf++ adopts a layered architecture including the underlying error-independent mechanisms and the overlay error-dependent prevention policies The underlying error-independent mechanisms provides tools and mechanisms to support policies It includes the report processor, the scientist to native mapper and the checkpoint restore and analyze First, let's talk about the infrastructural mechanisms because the report processor is very easy it's a passive script with regex We will start from the scientist mapper The key goal of scientist to native mapper is to translate the error site from the scientist binary to the native binary and through the south core line as we described earlier Normally, we can use the address tool line to map the binary address to the south core line and south core line to the binary address But address line is well known to be inaccurate as shown in these examples One address can often map more than one line of code and the one south core line can also map several instructions So the hubbvf++ only needs one specific address in the native binary The rest are false positives to block our work So we present our method to improve the accuracy of the transformation flow Our method is to use another translation flow for cross-checking Except the address to south core line and debug information also includes variables to register and register to variable mapping So only the instruction and the code line shares the same operands will be correct others are false positives as shown in the figure The variable ARGS is stored in the register RSI as this address range Similarly, the variable size is stored in the register RDX So only the line 465 matches among several options We have a statistic on more than 20 error size according to the result With our two flow cross-checking the false positive number will reduce from 2 to 0 per case So our method can feed the transformation flow The next component is online layer is checkpoint and restore How do you use this How do you use this component to skip the error size recover the register and kill the malicious process However, in the component we choose not to skip the error instruction because it may break the consistency of the register context As we can see the red red font marks the changed value The context of the registers between instructions are very complex as we can see in the line 645 But we found the easier case when skip a call instruction the only register changed to the call E is the REX and REX is used to store the return value So we choose jump to the return instruction and skip the entire function to keep the register context consistency We set up a checkpoint to require the register as the function entry and when the error condition is met How BPF++ will restore the register context as the function exit and assign error code to the REX and keep the register context consistency The rest of the function will treat the rest of the function in the cost stack will treat this function as an execution field and leverage their error handlers to keep the system functioning Except for the function skip there are also about 500 pairs of operations as the function entries that need to be recovered in the function exit such as spin lock, the locks the memory allocation the global memory modification device ready and so on So on the right side this function will unlock and allocate memory as the function entry and unlock and free as the exit So the BPF++ want to jump to the return We have to unlock the spin lock Otherwise the kernel will be dialog There are related work on the kernel status recovery so we don't see more details here Our work will temporarily focus on solving the lock problem Other pairs may not corrupt the kernel We also test the robustness of our solution the temporal solution and the kernel keep working on daily tasks for weeks and nothing serious happens the kernel will keep functioning After the mechanisms, let's talk about policies The overlay error dependent prevention policies are designed based on the triggering conditions of each type of vulnerability How BPF++ provides the templates of the BPF program for automatic generation I will show more technical details to help better understand how to extend BPF++ to other error types To extend new error types how BPF++ need to need templates of the triggering conditions for new error types and maybe some new BPF helper functions to support the template For example, we used autobahn error in the previous slide The triggering condition is autobahn mainly include two styles as we can see the triggering conditions in template 1 and 2 The first style is the pointer plus offset style It is the same type of the CVE we just showed before just showed previously The address has to be in the pointer's legit range And similarly, the second trigger in the template is memory copy style There is a destination, there is a source and there is a length Also include something like memory side as string copy string side To obtain the range we implement getBufferStart and length helper functions We obtain the legit range of slab body, Vimalock objects at runtime and for the rest conditions such as global static objects or arrays on the stack we can statically get them because their size is statically allocated as a function start and will not change in the runtime Extending to other types of errors adopt a similar method So we first need to design the template according to the triggering condition and also design related helper functions to support the template Now BPL++ can support these policies out-of-bound access as we just said and the use out of free, the integer overflow data-race, uninitialized memory web pointer access and user memory access For integer overflow we can simulate the calculation operations in 6-bit operands because most integer overflow we see now are 32-bit operands and the data-race we can use a PV operation to record the usage of the RISC data and once we find the data-race we may kill both RISC processes and for the unusual memory we can require the memory at the creation site and as a use set we will make it a comparison Next we will show a more complex policy the use out of free Although most cases are straightforward use out of free one bit is very complex than the out-of-bound and other error types because it has no three forward solutions It's a temporal memory corruption the triggering condition of use out free is that the pointer is a dangling pointer dangling pointer is a pointer referred to a freed object and the dangling pointer is dereferenced by the attacker to read and read the freed memory so we can use a quantity and sweeping method to prevent the dangling pointer from being triggered The policy is here first we quarantine the freed object until no pointer, dangling pointer exists we quarantine it by not freed but we quarantine it's address and we periodically sweep the entire physical memory for dangling pointers to confirm there is no dangling pointer exists we also design optimizations that how do you apply a plus sweeper can only sweep the certain slab catches because we have researched on several errors in most cases the dangling pointer will be stored in another slab object the rest of physical memory except the slab catches will not store the dangling pointers so this is the optimization after the technical details we will evaluate the performance our work has a good performance overhead because it is lightweight and only focusing on the specific error condition not the entire kernel so we designed experiment to make a full evaluation first we collect set color reports and CVEs especially for the CVEs we also need profile concept programs to reproduce the error condition report so we collect the profile concept program and write it in the same time as the kernel then we evaluate this task including the performance overhead the performance scalability and optimal physical memory sweeper sweeping period and range for the UAF sweeper this table shows the result compared to the vanilla kernel the result includes the slab out of bound the page stack global out of bound and the use of the free including two case the optimized sweeper and the full physical memory sweeper and an integer overflow the overhead is negligible result from minus 3% to about 4% and the benchmark section includes OS core primitives such as OS bench and the perf perf bench they calculate the overhead of system calls of networking and so on these core primitives and the CPU and the calculation intensive benchmarks including the open SSL the mp3 encoding and GIMP the L intensive workload including the circular light database the very very good stress for the networking L intensive the rest are common server tasks including git, kernel compile compression, Apache and NGX the average is shown in the circle I think the average overhead is acceptable only use after free is a little high because we have to write a sweeper periodically but overall it's practical next we also evaluate the scalability the scalability means the performance overhead when multiple BPI programs were executed at the same time in this figure we can see each line in the figure legend represents a benchmark overhead when we apply more than 20 BPI programs in most cases the worst overhead is less than 8% but there are special cases here it's about 20 or 30% it is because there is a vulnerability maybe it's a global it's a Wimlock out of bound it hooks on the NAPI interface NAPI pull interface of the network interface which is called very frankly under the high concurrency web server requests so high concurrency benchmark like Apache and NGX behave not so good but the rest benchmarks are still acceptable we also evaluate the optimal sweeping pure rate and range in use after free whole physical memory sweeper the range is from 128 MB to 512 MB and the pure rate is from 1 second per sweep to 8 seconds per sweep apparently we have circled the optimal performance the 256 MB every 4 seconds have the optimal overhead overall we are very honored to share our work to the community it's my first time to attend How BVIP Cloud Plus is a kernel protection before the patches are available and we have achieved such contributions we have achieved a set call report processor to extract debug information a setting type to native map to translate the error condition and error site a checkpoint restore analyzer to keep the kernel functioning and a set of policy templates and helper functions for various vulnerability types finally a thorough evaluation of the overhead and scalability I hope the community like our work like our contribution and also we designed this Q-logo generated by mid-journey AI that's all, too fast any questions, thank you Hi, you said you identified I don't remember how many it was but function pairs that need to be unwound but it sounds like you said you're only handling the lock-on-lock cases right now Yes and were you looking also at data structure invariance that might get violated halfway through a function or is that still also future work? Yes It's a little ad hoc here but it's not our main contribution Is there a way for users to modify the generated BPF programs or is there any support for that? Yes, we can We can say more guidance on this ad hoc checkpoint and restore Thank you This might be a similar question The example you gave in slide 8 with the string truncation going past the end can you add other other actions besides just the return for example in that case work has happened in a function and you get to a point and you're like I shouldn't do this but you've left the string unterminated can you, before the return this is sort of like unwinders right to the memory right and all to one below the size so you have a terminated string before you then return an error sort of like a custom return handler I guess Sorry, I'm not quite clear Do you mean here? Yeah, if you look at slide 8 Is that what you mean here? Yes, in slide 8 Hi So, yeah, here like some work has occurred before you return before you hit the args size equals null Are you able to add additional things in these types of cases where you say well what I want to do before I return an error is say args size minus one equals null and now return so you don't leave some potentially fragile thing in a bad state I mean it's similar to the unlock and all these other things so can that be done in an arbitrary fashion right now or is there work to be done there? I have understand that's a good idea for them to say but we want an automatic tool but it's about a little ad hoc I have tested if we just do nothing but return to the error return instruction and assign an error code it will still keep functioning but I think it's an ad hoc, it's temporal it's not a full recovery we have Right Hi In the slide you showed where you showed the actual output BPF code I believe you had a helper in there BPF setregs or something to actually set the return value If I'm wrong, that to my knowledge is not a standard helper do you have to load a kernel module to define that as a new helper? Sorry How do you actually set the return value do you use an existing BPF helper or do you have to define a new We have to define a new helper function BPF currently denotes about to modify the kernel very rapidly so I have to add a new helper function such as setregs and contacts to make it to assign an error code Okay, and you load a kernel module to do that take it or do you patch the kernel how do you do that exactly? No, we just direct it as a kernel Oh, you just directly patch the kernel, okay, gotcha Yes, BPF helper function cannot be extended through modules because you have to modify some kernel code in the BPF maybe the directory under the kernel directory Thank you Thank you for your great presentation I like your idea, but I have a question about your evaluation part So for I remember there are 16 errors and the overhead increase allowed So I wonder how you know figure out the root cause of those overhead Yes, let me make a simple explanation The error condition and the root cause of a one-bit are different The triggering condition is where the error triggers For example, integer overflow The trigger condition is the instruction that triggers the integer overflow but the actual root cause maybe is earlier in the call chain there is less lack of check and for your for your problem for your question, sorry The root cause here is we have sampled the execution of this BPF program by dumping the countries we have found it is called by through the API pool if you currently execute a high-concurrency network workload this function will be called very frequently So the case, the one-bit, the BPF program hook on this country so it also executed very frequently and cause the overhead Thank you So in light of some of the questions that people had earlier about you know, are there states that you could leave when doing the sort of checkpoint and restore approach Yes Have you all considered running syscaller on the patched version of the kernel see if additional crash circumstances come up from that? Yes, we have also make a similar evaluation of your questions We just modified a little of the proof of concept program so it will execute on the on the error side but the parameter will not trigger the error condition and there is nothing happens, everything good I've been thinking of like other conditions that might have now been turned into a potential crash or bug of some kind as a result of the hotfix We haven't seen we haven't had those cases maybe exist, thank you So if I understand correctly what you're basically trying to achieve is you're modifying the execution in runtime to like step over the issue have you considered since you know what end result you want to achieve so you know how the function should be executed in runtime there is certain instruction you want to jump to generate the modified function by copying that original function modifying instruction in the way you want and then using the live patch infrastructure to replace the old function so won't this give you better performance compared to doing the breakpoints with ebpf like replacing the old function Do you mean hotfix? So I understand the advantage of this compared to actually doing the patch is that you can automatically generate the ebpf program that jumps that fixes the bug but using the same infrastructure you can generate the updated function to do the same doesn't make sense to use live patch I know your question Here is a problem the hotpatch and the hotbpf++ works in a different period hotbpf++ work coming when no patches are available but the hotpatch you at least need a patch correct, but you essentially you can generate the patch using the same workflow that you have as I explained previous the triggering condition and the root cause is different if you need to fix the vulnerability you need to analyze the root cause and the root cause is very complex but if you just prevent the error condition it can be deducted through an automatic tool is it clear? Yes, but using the same automatic tool you can create the new function just instead of patching it instead of having the bpf breakpoint which may have extra overhead you can create a new function and replace the whole function I understand what you mean but there is a limitation on the bpf actually the original bpf merely supports only a little modification to the kernel actually it didn't support this it's not a Turing machine maybe I can modify the kernel data as much as I want so I cannot just implement a new function to fix this problem because the bpf program is running a virtual machine and is limited is it clear? Thank you so much


A film in three minutes. I'm telling you chief, I got something you gotta wanna print. All I needs is a week. Just seven days and you'll have the biggest scoop of your life. Or my name isn't Chuck Tatum. Star reporter of Billy Wilder's 1951 satirical drama Ace in the Hole. A tragic tale of one man's ego and the shady workings of the press that features Kirk Douglas in the lead role, who gives one of his finest contributions to the silver screen. Yet in Albuquerque, New Mexico, the story follows dishevelled and disgraced journalist Tatum, a reporter who has been fired by 11 previous big-name newspapers for unethical behavior and now works at a small rural outfit. After a year of struggling to find a big story that can propel him back to fame, Tatum by chance happens upon a remote gas station where a local man has become trapped within a dangerously unstable cliff dwelling. Sensing an opportunity to manipulate circumstances to best elevate the news, Tatum takes charge of the recovery operation, eventually convincing the local sheriff, construction engineers and the wife of the trapped man to bend to his will, prolonging the rescue, with the end result taking the unscrupulous paper man down a path of self-destruction. Acting as both a searing satire on the power of the press and a dark exploration of human desire, Ace in the Hole, or the big carnival as it was known after Paramount Pictures changed the title, contains many targets that the legendary author-director Wilder gleefully takes aim at. The relationship between journalists and their subjects, the gullibility of the general public, the corruptibility of people in positions of authority, and the cynical cutthroat business decisions news editors make when chasing a story are all slowly twisted into something almost absurd but equally believable once Tatum's star rises. As such, it's hard not to relish witnessing the at-first somber situation develop into a media frenzy, with thousands of curious spectators quickly gathering near the rescue site, turning the location into a grotesque circus, where well-meaning but credulous citizens hang on Tatum's every word, whilst also attempting to make a buck or two in the process. Douglas delivers a tour de force performance as the controlling deceitful journalist commanding vicious, even ruthless authority over every person he needs to to keep the story going, slowly mutating over each passing day into a tragic, pitiable creature totally oblivious to the personal cost his actions will eventually demand until it becomes too late. Upon release, the film was received coldly by critics and audiences for its darkly lurid depiction of American journalism, but Ace in the Hole has been recognised decades later for its savage lampooning of the American dream, even being selected for preservation by the Congressional National Film Registry. Not a bad end-note for Wilder, Douglas and a script whose morality tale will never truly be out of print.


Good afternoon. I'm Xenia, co-founder and CEO of Sly where our purpose is to empower wildfire resilience. So how does one get involved with the wildfire mitigation space and what is becoming known as fire tech? For me personally immediately before founding Sly I spent 10 years at BlackRock, world's largest asset manager, well-recognized leader in decarbonization finance. For a significant part of my career I engaged in conversations with some of the most sophisticated institutional investors globally about the role of private capital and private enterprise in driving meaningful impact on climate change.  What started as a benign spark during routine land maintenance activities got picked up by an unusually strong wind and obliterated the entire landscape in front of us including dozens of olive trees and citrus trees. This personally tragic experience was in a way an inspiration for us to develop a technology tool to protect and monitor our land. And it was a couple of years later that we realized that this solution can be scaled to address several critical gaps in detecting wildfires and optimizing response. But we'll come back to this later. For now let's look at the huge and complex problem of wildfires. Here's a couple of numbers. Each year it's about 23 million acres that gets devastated by wildfires. This is approximately the size of England. Slightly lesser known fact or lesser talked about fact is that wildfires are also one of the top contributors to CO2 emissions among all industrial activities. As a matter of fact there is a troubling connection between climate change and wildfires. As seasons become drier and hotter there is more wildfires they're becoming more frequent more devastating in turn releasing additional CO2 which is further exacerbating climate change. This last point is further supported by the numbers here. As a matter of fact over the last or eight out of ten largest mega fires ever occurred in the last decade. So what can humanity do to diffuse this ticking time bomb of wildfires? I classify available solutions in three building blocks. Resilient communities, land stewardship and innovative technologies. So under community resilience we talk about use of wildfire proof building materials. We talk about vegetation management. We talk about fire corridors. Under land stewardship we talk about vegetation management and the need for prescribed burns. Unfortunately society's focus on suppression over the last couple of decades has led to significant vegetation overgrowth. In reality however fires have always been part of the natural ecosystem cycle and it is in fact better safer and healthier to allow those low intensity fires to occur. And finally innovative technologies is almost by definition a little bit more controversial. What I found remarkable is that the problem of wildfires has attracted attention of the esteemed X price challenge. Thinking back to the early 2000s the challenge of X price foundation was directed towards solving for commercial space travel. Outcome of this challenge was in many ways the foundation of companies such as SpaceX and Virgin Galactic. This year X price newly announced and destructive wildfires challenge invited teams from across the globe to compete in one or both of two tracks. First being ultra fast detection and second being ultra fast response or mitigation. And this approach across two tracks makes a ton of sense because as you look at statistics behind wildfires we find out that it is in fact just 1% of all fires globally that contributes to more than 50% of all destruction, all devastation. So stated differently the purpose of the X price challenge is to be able to detect all fires very quickly but then also drive ample response resources to those most dangerous fires and contain them before they spread. The underlying thread across both of these tracks of X price challenge is speed which is paramount. If you think about the most high risk wildfire days that are characterized by hot dry and windy conditions if we can't get fire response resources to the site of fire very quickly containment becomes almost unlikely. Response generally speaking is a fairly well understood is visible part of the wildfire management cycle. However what enables response to be effective the first step the step that ties everything together is in fact detection. For detection to be impactful for detection to be effective it has to be done quickly it has to work in all conditions and it has to work across all sites. Imagine having a digital nervous system that covers all of the high wildfire risk areas that detects and senses everything very quickly and communicates those insights in real time. In addition to communicating those highly granular data points in real time the system also augments those data points with predictive insights around probability of spread of each and every fire that it detects. And this is our reality today with technology and research we are in fact able to cover vast and remote areas and detect all fires and predict those most dangerous 1% that are most likely to spread. How is this done? Well there is a couple of technologies that are already deployed in the field such as satellite based imagery which is terrific at showing the damage of wildfires after they occurred. It's a little bit more challenged in the field of early detection. Cameras on the other side are excellent at detecting fires very quickly but they have challenge in terms of scalability particularly around cost and connectivity issues. At Sly and this is the third image here and thanks to advancements in the fields of edge AI micro computing and satellite communication we're pushing the boundary by being able to cover vast and remote areas with our on the ground sensing technology and ensure that those deployments are done at economical points. So in summary being able to detect all fires very quickly and everywhere enables us to differentiate between good fires and bad fires, high intensity fires and low intensity fires. Reality is that we need more low intensity fires to rejuvenate our forests. At the same time we also need to know which of those high intensity fires are likely to spread and contain them in time. Thank you.


Well, why don't we go ahead and get started? I'm Patricia Cruz, Jeff Bilder. We'll introduce ourselves again in a little minute. We're very excited to be here. This is a little bit of, I would dare to say, a kickoff meeting for us thinking about organizational identifiers and really moving this conversation forward and producing and implementing something downstream. So what we're going to do today is kind of hopefully set the stage for you all about what the future of organizational identifiers are. And then Jeff is going to have a flashback. And he's going to share with you some of his experience with CNI and hopefully put it in context and give you an idea of how we can move the idea of organizational identifiers forward. We're going to take a look at the problem statement for organizational identifiers and then look at some of what the community initiatives are that are out there. And then think a little bit about why, particularly Crossref and Orchid and Datasite are interested in this space and why we feel we're the people to move this forward. And then look about at why now and think about the work that has been done and share with this group about what's next. What is our path to move forward on organizational identifiers? And then comes the fun part where we're going to look at the requirements themselves that we've talked about, but really at a high level and then hopefully get some feedback from this group about what our thinking is, whether we're crazy or we're on target or not. Oh, hi, Laurie. So one of our presenters, Laurie, is right there. She is a, unfortunately, she sprained her ankle and is not able to join us today. But she's online on Jeff's phone and she'll be asking questions and listening to all of you as we move through the presentation. So I am going to hand it over. Oh, Jeff, you. So Jeff and I have not rehearsed this. So it's going to be a little bit of everything. Right, so well, we rehearsed it to the degree that we had to modify the slides in order to divide them amongst two people as opposed to three. But we promise that we'd introduce ourselves. I'm Jeffrey Builder. I'm the director of strategic initiatives at Crossref, which is a DOI registration agency. And Patricia is? I'm the executive director of Datasite. And Laurie is the director of ORCID. And you'll see that little Thor thing over there. Just I want to give you a really brief information about what Thor is and why it's there crowding our logos. And Thor is a project that's funded by the European Commission. It's a 30-month project where we're looking at the identifier community and thinking how we can integrate those identifiers across our platforms. Crossref is not officially a part of the project, but all of our organizations work very, very closely with each other. And so we feel like that is the best way that we can get a lot of return on our investment. So that's the Thor project in a nutshell. And speaking of the sort of the fact that we work together very closely, this is the time for the flashback. We work together so closely, in fact, that when ORCID was started, I was seconded from Crossref to ORCID as their interim CTO at the very beginning when they were just building it, when they were just proving it out. And the flashback is this. The last time I was at CNI was in fact when we were just building out ORCID. We were just prototyping it. We were just coming up with the concepts. And one of the things that we did that was very useful at the time was come to CNI, get feedback, and to get input from the community, from other stakeholders. Crossref, we have very good connections with publishers and some connections with researchers, but not so much the library and archiving community. So it was a tremendously useful exercise at the time. And what you see here was, I think, like three days earlier, we had just managed to get the first ORCID code to boot on a server locally. And it was kind of working.  But the good news is that since then, ORCID is a fantastic, thriving, and much better designed application.  And it's just gratifying to see this latest bit of scholarly identifier infrastructure really take hold. Recently, as you've seen, they've passed the 2 million registered ORCIDs mark, which is a gigantic achievement. We just goes way beyond what we, at the very early days of ORCID, expected as far as uptake. And so it's really moving quickly. And likewise, I think the other thing that's just really taking off is data site. Right. And so for those of you that aren't familiar with data site, we're a nonprofit global organization. We have 30 members worldwide. And those members work with nearly 700 data centers. And to date, we've minted over 7.4 million DOIs, predominantly for data sets. But we also have a lot of text documents, et cetera. And over 6 million resolutions a month. So we're kind of the baby in this ORCID and cross-ref group. Sort of. She's just feeling intimidated by that, I think, which is. So we've been around a bit longer. We are also a nonprofit organization. And we assign DOIs primarily, historically, to things like journal articles and proceedings, but also to data sets and books and software and all sorts of other content. We've just blown by the 80 million registered DOI mark, which is fantastic. And but I think the really cool thing about all three of these efforts is that they are so now closely integrated. And this was always the vision from the start. But it's nice to see it start happening. If you're a researcher now and you have an ORCID and you go to one of the publishers who's supporting ORCID at Manuscript Submission, that ORCID will now travel with the metadata and get deposited either to data site or to cross-ref, depending on what the content is. And then data site or cross-ref will automatically update the ORCID profile of the researcher. So they don't have to think about this anymore. They don't have to worry about, oh my gosh, I've got to go and collect this information about my publications because a research assessment program is coming up and I have to go and scramble and find this out. The whole idea behind the establishment of ORCID and the integration of ORCID and data site and cross-ref was to ultimately save researchers' effort to enable them to not have to worry about collecting this information in their profiles. And this is just coming online and you're just beginning to see ORCID profiles getting updated automatically. And so this, we think, has been a victory. The feedback that we're getting from researchers on this functionality is tremendous. But clearly we're here and we're talking to you again. And that's indicative of the fact that we think that perhaps all is not right, that there's still something missing that will really build on the workflows and make the workflows for tracking research and assessment exercises a lot more efficient. But we still have a problem. And the problem as we see it and we sort of debated about how to talk about this is that we've got this stool. And if you notice, it's kind of missing a bit or possibly missing a bit. And that's one of the things that we're trying to explore. We certainly have two legs of the stool, which are really important. We have content identifiers that Datasight and Crossref are providing. And now we have contributor identifiers that ORCID is providing. And this alone sort of enables a ton of functionality. It means that an institution that knows that ORCIDs of its researchers can look in the Datasight or Crossref metadata to see when new content comes out with that ORCID attached to it. And if it comes out, they can download it and archive it and do all sorts of other things. It means that funders who know that they've given a grant to somebody with a particular ORCID can go in and see the research outputs that are being delivered from that funding trench. And these are all hugely useful things. But there's something that would really truly make this whole stool stand up and really function. And that's organization identifiers. To be able to have an institution say, I want to be able to reliably determine that what publications have come out with people affiliated with my institution so that I can track them. This would just enable a whole host of new applications and enable, we think, the entire community, publishers, institutions, funders, researchers to automate a lot of otherwise tedious workflow. And the question we have here is this. There are a lot of players in this space at the moment of one form or another. But I'm going to ask you a question. How many people in here think the organization identifier issue is a solved issue to the degree that content identifiers and ORCID identifiers are? Anybody think this is, my guess is that if you thought it was, you wouldn't be here. So it's a pretty easy, it was a pretty easy guess to make. So this is the problem, right? We kind of have maybe a wobbly leg, not quite the third leg of the stool that we need. And I don't think we're the only ones that think so. There have been a number of studies. We've commissioned internal studies or cells, but also some public ones, notably a just-casurate study that just talked about what a nightmare organizational identifiers are. Our own Martin Fenner has added to this occasionally. And I can just say that talking to the community, this is always a thing. It's like, when are we going to get this? I know that Cliff, sitting in the back, I've talked to him in the past about organizational identifiers and what a horrible, gnarly, and difficult problem it could be. But yet, here we are. There's a documented need for these things. And here are some critical aspects of it, right? Just like the identifiers that exist for content and for contributors, we want these systems to be comprehensive, open, and accessible, right? These are sort of some ground rules for identifiers that are going to be fundamental to the infrastructure of scholarly communication. Right, and I think, Jeff, one thing to note about this is the organizational identifier infrastructure doesn't only imply the technology. It implies the organization as well that supports that technology and the community. And this is something that we'll probably harp on until you're sick of it. But now, as we've noted, there's a lot of excellent work. There are people in this space, but there's this gap. And it's a gap that has just affected each of our organizations a lot. It's something that's constantly tripping us up. And so the big question you might be asking is why are we doing this? And I think there are a few reasons, but we all need them. And we need them in so many different use cases and so many different roles. And one of the complications, I think, that we have, and one of the reasons we're going out to the community, is to figure out which use cases and which particular areas we want to focus on. Because I think that the organizational identifier problem has a lot of characteristics that we experience with the researcher or the contributor ID problem, which is that when we started out and we talked about contributor IDs, everybody had an idea about why they were important. And all of those ideas focused on different kinds of use cases. So you had one group of people who was focusing on things having to do with authentication and authorization. And you had another group of people who was focusing on issues involved around discovery and things like that. And those use cases, some of them were really complicated and some of them were easier to deal with. And so one of the big things we had to do at the beginning of the ORCID process was determine in which of those problems are tractable, which ones were reasonable for us to try and deal with, and which ones would we either ignore or postpone. And that was one of the biggest. Making those decisions was one of the things that got us the most momentum in ORCID. But we have experiences. We need these. We have experience in the identifier space. Each of us, I think, represents a broad community of stakeholders. And clearly, each of these communities has different use cases. And we have to understand the full gamut of them. And this is a critical thing. At the moment, we're willing to take it on. I mean, we've just sat here and dithered about this for quite a long time. And I know, and I'll talk about this later, when we were working on ORCID, people would come up to us and say, why aren't you tackling the organizational identifier problem too? And we're like, holy, we're trying to deal with one big thing. It's way too complicated for us to do that. And besides, we thought at the time that there were other entities who looked like they were going to tackle it and maybe solve the problem. But that brings us to this point. One thing to really note is why we think that we're poised to work on this is that Crossref, Datasite, and ORCID, saying that we all represent different communities and we work globally. And scholarship is global. And I think Crossref works with publishers. We work with a lot of national libraries and data centers and ORCID working directly with researchers. You bring that whole package together, we really have a good idea about that broad stakeholder community. So I think that's really important to note. Yeah, and I'll build on that. We talk a little bit about it later as well. But one of the anti-patterns that we keep trying to sort of get beyond is the idea that scholarly infrastructure is country focused or institution focused or discipline focused. Increasingly research is international. It always transcends institutions. Almost everybody is collaborating with people outside of their institution. And so any kind of infrastructure that we build has to accommodate that. It can't be an infrastructure for physicists in the US. And all of our organizations have really taken that to heart. We built systems that we want to work globally across disciplines and across institutions, which brings us to why now the community really is keeps coming to us and saying, you've got to do something. We think we have a good understanding of the requirements. And again, I think that this depends on the use cases. There are some requirements that are quite fuzzy, but there are others where I think we have a much better sense. So for instance, just so that I don't sound like I'm being coy, just as with ORCID you might have authentication issues and discovery issues, you have something similar with organizational identifiers. You could have an authentication focused view of organizational identifiers, or you could have a discovery focused view of organizational identifiers. And as I'll illustrate later on, those two don't necessarily match. You're still using identifiers. You're talking about organizations. But there can be some disconnects there. And those are some of the things that we want to explore. Do you have any? Yeah. So what's been done so far, we three, besides getting together and saying, we've got to do something, we've been doing a lot of background research looking at past reports that have analyzed the identifier structure, trying to itemize the use cases and requirements from those, and build some of these things. We're going to point you a little later on to a document where we've been collecting some of these things and we're going to encourage you to add observations and things like that. And we've developed a long list of requirements. And again, I'm going to emphasize that it's a long list, right? Because part of the reason, I think, that a lot of people have been reluctant to tackle this is that they get that long list of requirements and they think, if we don't solve them all, we can't do it. And we actually, at the moment, think that there are probably parts that can be carved off and done sooner and then other bits that may need to be postponed and other bits that really are so gnarly that maybe they're things that we don't want to even touch. And this brings us to what next. We want to expand the list of use cases. And again, this is why we're coming to you. And then we want to go and prioritize the requirements. What do we think we can do? What do we think is a tractable problem in the shorter term? And then, and this is the process that we're through. This is the first of at least two meetings that we have scheduled now to talk about the issue with the community. The next one is actually going to be a workshop at Forest 2016 in Portland. And if anybody's going to be at that, we encourage you to be there. We're really going to try and hash through some of the things that we gather here and that we gather between now and then. And then we're going to create some groups to explore some of the particular issues that we identify within that. And we're really hoping that we have a pretty clear direction of where we want to go in the fall. And again, based on our experience setting up other things like orchid and stuff like that, this seems like a reasonable schedule to us. But we'll see. We'll see what kind of feedback we get. What's happening today? Well, we'd like to point you at this list of requirements that we've put together up here. We'll make these slides available. If you can get down to this short URL, you can see the list as we have it at the moment. We'd love to discuss some of the issues that we've come up with and get your feedback on that and then also incorporate that into the document. Yeah, and part of that is also supplying your use cases and sharing with us some of those things so we can make sure that our requirements are on the right track with that. And which brings us to this. And one of the things that we're trying to do is we're trying to break down the requirements that we consider to be primarily organizational and those that are more technical. And again, Patricia alluded to this at the very beginning, one of the things that concerns us all in this space is if we are planning on building infrastructure, we think that that infrastructure has to be governed and has to be organized in a way, it's not just about technology, it's about an organization that keeps running this technology that's sustainable, that's accountable and that people are ultimately going to trust. And this is a very big issue. Trust is, we have this sort of reflexive and understandable worry whenever we see a big chunk of critical infrastructure get centralized. Because clearly that could be a single point of failure. It could, we've had experiences of organizations that have started out as community organizations and then have sort of parted ways of the community and gone their own way and become unaccountable and unreachable and unungovernable. So a lot of people have some very big concerns about what an organization that's gonna be responsible for so much infrastructure is gonna look like. And this again is something that we encountered in the very, very early days of working. And one of the first things we did, and I seriously was the first thing the board did, is they had to adopt some principles that governed the operation of the Orchid Board and the Orchid Organization. And this was the first thing they did when the board was formed was pass these principles. And we have at least, I think, one ex Orchid Board member in the audience back there. I saw Craig come in. So he remembers this. This was a really important point in Orchid's history because once we adopted these 10 principles which committed the organization to be sort of open and transparent and that the data was gonna be open and that the business models were not going to be based on and closing the data, that had a profound effect on how people perceive the organization, whether or not they were likely to trust it with such vital institutional or infrastructural role. And so I, since the drafting of those principles, I've been working with some other colleagues. You may know Cameron Nailin and Jennifer Lynn and we've been spending a lot of time talking about what the characteristics need to be and these are aspirational. I have to, I will add very quickly that I don't think Orchid meets them yet. I don't think Datasite meets them yet. I don't think Crossref meets them yet. But we've come up with a set of aspirational sort of description of what needs to happen with an organization for it to be a trusted, trustworthy, sorry, infrastructure in scholarly communication. And those things that we talk about cover things like coverage, like for instance, I mentioned that infrastructure ideally transcends disciplines, nations, institutions and things like that. Governments, that is who is the organization open to? How is it actually operated? Is it for profit, not for profit? Which gets us to sustainability because clearly if we're running infrastructure it would be very irritating if that infrastructure disappeared on grand cycles. I mean imagine if lights and plumbing were funded on a grand cycle and every time you ran out of money your lights went out. That would be a pretty frustrating infrastructure to deal with. So we're very concerned about sustainability. And lastly we're talking off a lot about the insurance. That is how if all else goes wrong how can you still feel some know that you're gonna be able to at least extract yourself from the system. And so there are all sorts of governance issues and we don't wanna go into them in huge detail there but if you wanna say the kinds of stuff we're talking about and thinking about there's this article that we wrote which was grounded very much on our experience in running things like Crossref and Founding Orchid and DataSite. And I think it's pretty important in our conception of any solution to this problem of organizational identifiers as well. And this brings us to the technical thing which is what most people focus on immediately when they're thinking about infrastructure. And as I sort of alluded to earlier when we were dealing with orchid in the early days we had a lot of people come up to us and say but aren't organizational identifiers easier than identifiers for people? And I've got a cute laughter, right? Because anybody who thinks about it for three seconds realizes that organizations have all sorts of irritating habits like they do things like merge and split and have aliases and die and are reborn and people, identifiers, that's difficult but I don't know of any person who has sub-people. And I haven't seen a reborn person yet. And so, I mean the problem's really associated with what I'm trying to establish is we're not naive about this, right? We know that this is a bigger problem and it has some complications that are quite different to the ones having to do with contributor items.  The rose-tinted glasses view of organizational identifiers is this should be easy, right? Harvard University, clearly this is something that nobody is gonna doubt. Everybody has the same view, this is Harvard University. But of course, that depends. Are you looking at from the point of view with subscription glasses on, right? Where you might actually be talking about your relationship with a library at Harvard. Or even more specifically, IP ranges for subscriptions, right? And if you're looking at it with membership glasses on, yeah, it might be Harvard University. But go off and look up Harvard University to legal entity, you know? And it's presidents and fellows of Harvard College. Now imagine for a second that you're trying to populate a list that was designed to allow a researcher to pick their affiliation and you put that up, right? That wouldn't work too well. So it's really important for us to figure out which of these sort of perspectives we want. And then affiliation might be something as far more precise. And so, you know, I think one of the things that we're exploring here is that all of those perspectives, all of those different views of what an organization are, are clearly all important. And some of them are just unbelievable rats nests. And some of them are probably a little easier to do. But even doing the easier ones might make the rats nests ones easier to do in the longer term. And I know, again, this is, because I've had brief conversations with Cliff about this in the past and particularly talking about things like subscriptions and IP ranges and so on and so forth. We know this is a big issue, right? But we also know that this is a horribly messy issue. And so one of the things we're trying to decide is we look at all these use cases which things can we take off and do more easily and which ones are harder. And maybe there are harder things that we don't want to touch but that we want to at least enable somebody else to do it more easily, right? So you can make an argument that even if we attached, decided to focus our energy on, you know, organizations from an affiliation point of view, right? That that might ultimately make somebody's life easier if they were trying to account for organizations from a subscription point of view. And again, this is all the kind of stuff that we're sort of churning through, trying to understand, trying to get a picture of. But I'll say upfront that I think a lot of the driver for all of us focusing on this issue now has a lot to do with affiliations, right? And in turn, the driver for that is a changing environment in research where it is becoming increasingly important for funders, for institutions, for researchers to keep track of all of their research outputs in a comprehensive way, a systemic way. And that this is occurring at an industrial scale now. Whereas before you might have had to put together a list of your publications when you were up for promotion or tenure, now you have to do it every X years. And it has to be complete. And it has to be, you know, and everybody, not just everybody in this institution has to do it, but everybody in every institution in a country has to do it at the same time. And so the old mechanisms, whereby you could just write a note to somebody and say, could you send me an acceptance, a letter confirming that you've accepted my paper and such and such, those don't scale anymore for this kind of stuff. And we know that institutions are struggling trying to keep track of this information and they have to keep track of it. We know that funders are struggling to do this. And we know that publishers want to be able to make it easier for their researchers to provide this information. And so at the moment, you know, one of the sweet spots that we're looking at that where we think we could provide, you know, a great deal of value for a subset of the organizational identifier problem, overall problem, is affiliation. But again, that's a working hypothesis and that's why we're here and that's why we're talking to people. It's no whether we can usefully hide that part off and focus on it in a way that makes sense and that's useful in the short term. So, you know, again, I think one of the big messages we want to get across is that this is a group effort. We all have skin in this game. We all need to solve the problem. And so we're collaborating in a way that's even more sort of, you know, more intensive than we have even in the past because we think that this is a big enough problem that it's gonna take all of our efforts to really solve it and to reach all the communities that matter. And we're at that stage that I was at when I came to CNI the last time talking about ORCID where we're trying to get more community input so that we're pretty sure that we understand the problem and so that we can move forward. So again, I think there are two places where you can provide immediate feedback. One is if anybody's gonna be involved in 416, we encourage you to come to this session where we're gonna be talking about a lot of the stuff we think in a lot more detail. And then also look at this draft that we've put together which is sort of a, as we say it's a long list. It's a mix of things. We struggled with should we release this now or should we fix it up and make it lovely and organized and neat and we decided to get it out there as early as possible so that we can start getting feedback and we'll neat it up and organize it as we go. And then lastly, of course, you can get in touch with any of us if you have ideas about this or if you wanna talk about particular use cases that you think are being ignored or not being talked about, you can address all of us immediately. And then lastly, because, and I know that I hope, I hope Lori's still there, she's still there. Lori was concerned that we might not leave room for us to get feedback and so I'm happy to say that we've actually got quite a bit of time for us to get people to get people's feedback on what kinds of issues they'd like to see and to test our ideas about affiliation data versus subscription data and things like that. So I think, yes, the floor's open. Thanks a lot, everyone. Thanks everybody.


You got the bid folks in a big way here, gold, gold up $14 trading at $18.45, you get silver up $0.70, $21.72 an ounce, a light sweet crude up $79 at $83.10, notes and bonds. It's a 10-year note, down $15, tick-straight and $106.26, the 30-year down $36 at $110.15 and King Dollar. King Dollar, this is the first time that we've been down three days in a row after being up down $281 since July 14th, that is, $106.054, the euros at $105, the ends at $149, the British pound is at $122 to $1 US dollar. Now let me show you the dollar first, because the dollar is going to need one more day of this. I thought one good day of this would break that trend, but it's not. You can see it's right on the line now, okay? Because when you attach four, I get five days attached, which is a good attachment, it's actually six days. So you can see what's happening here though in a monster way. Now check out the market though. This is a monster sign of strength. We take a look at the spy bottom line. You already have 78 million shares traded. You're up $590, this baby's going. The queues are leading the charge. Take a look at the queues, which you have inside the queues, you have that volume inside the queues, man. The queues are $58 million. So the queues, they've already broken the downtrend, we're at, what, $365? That's already broken the downtrend from $378. And now here's the kick up. Prices and bonds, if you remember folks, when interest rates were at zero, right? The market itself, basically the 10-year and the 30-year start moving down in price higher in yield before the Fed moved. My take on this, the exact same thing's going to happen here. You hear everyone out there that the rates are going up again, this is about as devious to get. Well, guess what? The market's going to start moving these. We have a test of the lows out here today on the 10 as well as the 30. That's saying we are off. And this is going to get really intriguing, man, because the market, you know, it's like who's wagging the tail? That's the bottom line. And it's the market. The market is always, you know, bottom line, the market forces the, the market forced the Fed's hands on the way down, on the way up on yields, and now it's going to just be the opposite. We take a look at gold, gold, that's the fourth time we've rejected lower price out here, but 1845, stay right there folks, come right back.


Mr. Speaker, once again this week we have seen evidence that the Liberal government is prepared to say literally anything to try to hang on to power. In recent days, the Premier's claims that our proposal to phase out their cap and trade program and replace it with a carbon pricing program in line with what the Trudeau government is requiring and which would return all of the revenues to Ontarians would cost more and would not be as effective in reducing carbon emissions were shown to be patently false by the respected National Magazine, McLean's. In fact, the McLean's article demonstrated that the people's guarantee will do the opposite. The study by economist Trevor Tomb suggests our plan would in time leave Ontario households better off than what the Liberals say and reduce emissions more in Ontario than under their cap and trade program. This leads to another important environmental issue. That being our responsibility to protect and preserve our groundwater today and for future generations. Over and over again, I have repeated my position on this issue, including my view that we need to do more to improve the recycling rates of empty water bottles and other single-use plastic beverage containers. How is this best achieved? It appears that each province has its own approach with varying degrees of success. I'm told that the province of Manitoba's recycle everywhere program has been impressive in dramatically improving recycling rates. It deserves a good hard look in the context of stewardship on Ontario's ongoing consultation with the Blue Brocks program. I'm also aware that the Town of Irans Public Space Recycling Project, Town Council and staff deserve credit for working with the Canadian Beverage Association and I know with the enthusiastic support of the people of Wellington-Halton Hill. This effort will lead to success as an example for the rest of the province. I stand you sit. Remember from Niagara Falls. Thank you Mr. Speaker. And my member's statements on gas prices, I'd like to talk about something in this house that has been bothering me for a long time. Something I've spoken out against and new Democrats are working to put an end to. The issue of people getting gouged at gas pumps across the Ontario. Mr. Speaker, it's not hard to see why residents feel they're being gouged. They're paying around $1.17 for gas in Niagara Falls right now and you usually go to St. Catharines and it's $0.10 cheaper. We also see that gas prices continue to rise even when the barrel of gas remains relatively low. We know that the price of oil crashed and yet we never saw the same reduction in the price of gasoline. New Democrats are going to do something about this. We put forward a bill to try and deal with these prices and this gouging has to stop once and for all. I hope the Liberals and the PCs will support our bill and finally offer some relief for residents. I have said many times the fuel industry needs transparency and one possible consistency yet we don't see that. Instead we see big companies doing whatever they can to make a profit off the good people of Ontario. My message is clear to the Premier. As families begin to travel during the Christmas holidays, give them a gift they can all enjoy. Support our bill and stop the gouging of Ontarians at the pump. Thank you Mr. Speaker. Thank you Speaker. I'm proud to be part of a government that is supporting cycling and cycling infrastructure. Our government knows that hopping on your bike is great for your health, for congestion, on roads and for the environment. My riding of Davenport has the second most commuter cyclist in the city who use their bikes for commuting and for fun. But yet it doesn't have enough infrastructure in place. That's why I was so pleased when earlier this week the Minister of Transportation and the Minister of Tourism, Culture and Support joined me in my riding of Davenport to announce the recipients of funding from the Ontario Municipal Commuter Cycling Program and that our government is more than doubling the program's funding. To help my riding of Davenport, the City of Toronto alone is receiving 25.6 million dollars that will be used to help deliver their 10-year cycle network plan and to expand the bike share Toronto system with up to 300 new bikes, share location and 3,000 bikes and 6,000 dogs. This will mean that people in Davenport will benefit from more bikes, bike lanes and safer cycling infrastructure to get where they need to go all across the city. More cycling infrastructure and expansion of the bike share program will encourage people to cycle more often, improve safety and provide more travel options. I'm also hopeful that this money and that the City of Toronto will update their project list to include the much-desire bridge to Earl's Court Park. By kicking our funding into high gear, we will continue to keep our province to make cycling a safer, more attractive option for people in Davenport. Thank you. Further member Samus, the member from Whitby, Oswald. Thank you, Speaker. Their opportunity is an organization based in the Oswald part of my riding and provides low-income families within the region of Durham with the financial means to enroll their children in local sports programs. Through their involvement, Speaker, in these programs, young men and women can develop the confidence, social skills and healthy lifestyle attainable through sport. And getting involved in these activities encourages social interaction and contributing to a greater sense of community identity and social cohesion. Through the programming and financial system provided by their opportunity is meeting the needs, Speaker, of children, youth and the broader community and contributing overall towards continuing to ensure that the region of Durham is a safe, active and caring community. Speaker, I'm proud that their opportunity is providing the leadership, opportunity to increase positive role models and programs that improve young people's quality of life and as a result, increasing their chances for achievement and success. And I'd like to commend the board and Randy Gill for all their outstanding work and the opportunity that they're providing young men and women in the region of Durham. Thank you, Speaker. Thank you, Speaker. Thank you. Further member Status, the member from Nicobel. Thank you, Speaker. Since winter arrived, the good people of Gogama and Metagome First Nation in my riding have been faced with almost daily power outages. Last weekend, the power went off and on about 30 times. Monday night, power goes off at 9.20 p.m., gets back on during the night at 1.30. Tuesday, the power goes off at 5.45 p.m., is restored at 10, but only for four short hours because Wednesday morning at 2 a.m., the power goes off.  Our liaison at HydroOne sends me pictures of snow and trees, as if this is somewhat unusual in Northern Ontario. Speaker, electricity is not a luxury. Many people in Gogama and Metagome do not have a wood stove to heat their house. They do not have a power generator to power up their furnace. Some residents are on oxygen concentrators to breathe. They worry that their backup oxygen will actually run out because they have been out of power for so many times. They are frightened. For them, it's a life in that situation. What happens to the meat in your freezer when you've had a successful hunt, but your freezer keeps thawing out? How are you supposed to cook your fruit cakes? Are you Turtiaya when there's no reliable power? How let alone get ready for Christmas? Our electricity system is not reliable. Thank for nothing, HydroOne. The residents are fed up. They are frustrated. They are angry. All they want for Christmas, Speaker, is a reliable energy system. Thank you. Thank you, Mr. Speaker. I just wanted to thank the Minister of Finance for including protection for victims of domestic violence in his Budget Measures Act, Bill 177. He is doing that in this legislation by ensuring that innocent co-insured are not penalized because their spouse committed an illegal act. And I've been trying to help three women in Ontario whose husbands, sadly, burned down their homes, and yet they couldn't collect insurance. And I hope that this measure gets passed in this Bill 177 so that we will stop penalizing abused women twice because they were victims of this loophole and that their husbands who were in three cases all criminally found guilty of arson and assault, yet the spouse could not collect insurance. So this will close that loophole once and for all and ensure that this practice of discrimination against abused women stops in Ontario. Thank you, Mr. Speaker. Thank you. There are members' statements. The member from Scarborough, Rouge River. Thank you, Mr. Speaker. Mr. Speaker, education is one of the most important services that the province provides its residents. During the past few months, I attended several community meetings with the World 8 Toronto Catholic District School Board Trustee Gary Tanwan and TCDSB Parent Council leaders on their discussion regarding school closure. Specifically, the three schools in my writing of Scarborough, Rouge River that are on the review, St. Gabriel Lahneman, St. René Goupal and the Divine Infant Schools. The frustration, anger expressed by the parents and students of these schools were enormous. The last thing that the parents want to have their local school closed and move their children to a school outside the community. The uncertainty surrounding the future of the school is further exacerbating the situation when frustrated parents uncertain of the future of their local schools are making the drastic move and finding alternate to the Catholic schools. Mr. Speaker, I'm very happy to report on the November 16th, I, along with the many parents' students, deputed at the TCDSB and convincing them to save the three schools from chopping block. I want to thank the school trustee, Gary Tanwan, all the parents and students who worked hard to save our school. Thank you, Mr. Speaker. Thank you. Who is the member to save us, ma'am, from Trinity Spadina? Thank you, Speaker. I rise today in the House to celebrate our second annual Trinity Spadina Outstanding Business Award. Many writings in Ontario have one or two business improvement areas or BIAs. My writing of Trinity Spadina has 18 very active BIAs. My family had a small business and where I worked as a part-time staffer during my school years and I know the challenge and the hard work putting by business owners. Businesses like Wartsman Art Supply in Chinatown have been supporting artists and students alike for over 60 years. The Horseshoe Tavern, a landmark for live music in Toronto, celebrated 70th anniversary this week and it was recognized by CBC, Toronto Star, Toronto Sun and the Cableballs 2-4. Mayzak Quesadilla in Liberty Village recently won the Premier's Award recognizing their dedication to sustainable farming. The CN Tower, Resta Pasta and 17 other businesses in total received the Trinity Spadina Outstanding Business Award. Businesses are community hubs. They provide opportunities for Ontarians to grow and thrive. Our BIA Awards are not only an opportunity for business to be recognized but also a platform for networking and learning best business practices. I want to thank them for the contribution they provide to the vibrancy of our community, job creation and the innovation that they bring forward. Thank you Speaker. Thank you. Further member statements? The member from Piran, Bruce. Thank you very much Mr. Speaker. I rise today to speak about a town council meeting that was held last night in the municipality of Concarton. During the meeting a senior manager from the Ministry of Environment and Climate Change made a presentation on renewable energy and wind turbines. Although the Ministry seems to acknowledge that there are health complaints surrounding many industrial wind turbines, there still appears to be little action being taken in response. I, along with many members of the community, still have concerns regarding the response from the Ministry to serious health complaints from those living close to industrial wind turbines. The Ministry acknowledged in their presentation that there are health complaints from both tonal noise and infrasound, yet for some reason the Ministry still refuses to test for infrasound. Councillor Andrew White pointed out that currently the wind proponent does its own testing while no one from the Ministry oversees it. He went on to say and I quote, I see lots of potential for conflict of interest here. How can anyone trust the testing? And even worse, the Ministry official admitted at this time there is no legislative requirement that the company publicly post their results. It's just an expectation of the Ministry. We saw this past week, Speaker, what happens when the Liberal government blindly trusts a company without government oversight? Ratepayers are overcharged to the tune of more than $260 million in eligible costs. So Speaker, I would like to take this opportunity to call on the Ministry to do the right thing. Thank you. Thank all members for their statements.