OK. So welcome. My name's Rob Clark. I'm a security architect for Hewlett Packard. I've been working with OpenStack for around about the last three years. And in that time, I helped bootstrap the vulnerability management team, which acts as a cert. And I'll tell you a little bit more about them. And I started the OpenStack security group. For this release circle, I am the elected leader of the security group. So during this talk, I'm going to talk to you a little bit about vulnerability management and mention OpenStack security notes for those of you that weren't in the previous talk. We're going to go through OpenStack security advisories in review. We're going to look at the impact and try and work out some other ways forward. I was supposed to be sharing the stage today with Cody Bunch from Rackspace, who unfortunately wasn't able to make it. So any mistakes in the slides are his fault. I should point out this is going to be a very fast talk. I've got a large number of slides. I got a little bit PowerPoint happy. So we'll just see how we go. So the vulnerability management team exists to receive publicly reported vulnerabilities in OpenStack. They are an independent group of security-minded engineers. They have representatives from HP and other organizations on there. But their primary role when acting as the VMT is not to represent those organizations. They are there to work with and improve OpenStack. The VMT receives vulnerabilities normally in private. They triage them, patch them, work with PTLs. If the vulnerability turns out to not be so bad as perhaps the reporter thought, then they will perhaps just move it to an OpenStack security note or do something similar. The OpenStack security group, which I need to tell you a little bit about for those of you that weren't here in the last session, was established about two years ago by myself and Brian Payne from Nebula. He consists mainly of security engineers, architects, consultants, and developers. We consult with the vulnerability management team on security advisories. So when something comes in and they're not sure about it, or they'll go, hey Rob, how does this affect the public cloud? Or how does Brian's house affect a private appliance led, driven, something like that? So consultant advisories, we run a number of security initiatives. You have over 150 members, and we publish security notes, kind of mirror advisories. And advisories are the main point of this talk. But the security notes exist to provide you with information about parts of your configuration or bits in OpenStack that might cause you problems or cause you security issues. So this is the real difference between an OSSA and an OSSN. So an advisory is a bug in OpenStack that's going to create some sort of security issue for you. A security note, basically, if you configure it like this, use this technology naively, deploy it in a certain way, you're going to have a bad time. So security advisories are published to the mailing lists. And security notes in a very similar format are published more widely. So we have the mailing list. We also have a wiki page at lists, all of the security notes one after another. So what I'm going to do in this talk is take you through a little journey in terms of trying to understand how vulnerable OpenStack has been in the past by looking at the various issued OpenStack security advisories. Now, the advisories are listed on release pages. So in theory, you can go and have a look and say, well, Diablo had this many and Essex had this many. And it turns out to not quite work like that. So I have a quick look at the spread of vulnerabilities throughout OpenStack in terms of the OpenStack security advisories that were issued. And here you see a scary picture for anyone who still weren't running grizzly, dropping off to Walter Vanna. There's no obvious reason why grizzly should have so many more security advisories logged against it. And we'll investigate that a little bit more going forward. So this is a format of the data that I prefer to look at. I appreciate it. It's going to be difficult for some of you to read. It's OK. I don't expect you to know the individual notes. I just like to see the data in this sort of format. And one of the things we looked at doing was breaking down the data by when the vulnerability was introduced. So we see that there's actually a lot of repetitions. You can see OSSA 2020-05 propagates forward through three releases. We also notice that there's not a single shared vulnerability between Folsom and Grizzly, according to the release notes that we were basing our analysis on. But between Grizzly and Havana, there's a massive number of replicated or duplicated OSSAs. Around about two-thirds of the vulnerabilities reported in Havana were actually inherited or introduced in Grizzly. Again, making Grizzly seem really bad, and we couldn't find any good reason for it. So then we decided to have a look the other way. So when a vulnerability is reported, we assume that it is reported in the most recent release. So if a vulnerability was reported in Grizzly and Havana, we take Havana to be the point where we care about the vulnerability and see how it propagates down. So by doing that this way, we have the same mappings as before, but we start knocking data out of Grizzly as you would expect. We see a lot of data being knocked out, and we see this small spread across Folsom. And there's, again, this gap between the two of them that we couldn't explain. We looked at release notes. We looked at the various services that were released in Grizzly and between Folsom and Grizzly, and was horizon a problem. Probably not, and was heat a problem? Well, it kind of came a little bit later, and it kind of didn't make a whole bunch of sense, which is not good when you're trying to establish a security baseline for a system. It just didn't pass the SNF test. That data doesn't look right to me. So what we ended up doing is looking through, manually going through every single security note. And what we found is that actually, security notes in terms of what they address isn't necessarily reflected in what is easily reported today, which was bad because a load of the graphs and a lot of the analysis we'd already done were on the previous set of data. So what we end up seeing here is the vulnerabilities in terms of where they're introduced and propagate forward. We suddenly see that there's a large number of vulnerabilities introduced in Folsom that actually affect Grizzly. So we no longer have that gap. And if we go the other way, we can see that there are a large number of vulnerabilities introduced in Grizzly that affects Folsom. And in fact, all those bold ones towards the bottom of the Folsom release. And what this means is we really have two ways of looking at security advisory data in OpenStack. We can have a look at when the vulnerability was introduced. So we take a look at an advisory that says, this piece of code was broken in Folsom, Grizzly, and Havana. And we decide that, OK, well, we're going to attribute that to Folsom and knock it out of the other two lists. Or we go the other way and say, well, this was reported on a certain date, so we'll assign it to that release. And then the other releases before it will drop off. And what we end up with is these two different graphs. So the first one is a graph of when bugs were written in which release. And the second graph is more what we were expecting to find when we were looking at this data, which is where more inspection has been applied to the code, when more people are looking at the code, as the project grows, where do we see these vulnerabilities coming up? So we found that, firstly, you shouldn't get security guys to do statistics. And we found that simply looking in the obvious places for the data wasn't really good enough. So we had to go through every single security advisory and do the mappings ourselves. We noticed that the way that things are discovered is very different to when the vulnerabilities are introduced. We see this fairly safe upward trend for discovery, but we see a mixed trend for when they're introduced. And this is the data all side by side. And we can see that no longer is grizzly considered to be the most terrifying release. Now it's probably Folsom. We find that Havana is kind of trending along the right line in terms of the number of advisories against it, and that the number of advisories being detected, or the number of vulnerabilities being detected, which is what you see in orange here, has gone up year on year, released by release, which is probably a good thing. So I'm going to take you through a little bit of the vulnerability spread between the different releases to have a look, see if there's any obvious trends that we can recognize. So in Diablo, it was Keystone and Nova, and a little under half of the vulnerabilities were critical. So orange denotes critical here. Essex, Keystone Horizon, about a third. And then we start seeing trends. Folsom, the number of projects having security advisories, security vulnerabilities introduced that subsequently resulted in OSSAs, starts to spread. So we have Glantz, Keystone, Nova, and a mixed one that affected Nova, Keystone, and someone else. And we see that well over half of these vulnerabilities were rated as critical. And then as we go into Grizzly, more projects, more big vulnerabilities. Going to Havana, number of projects seems to sort of stabilize. The criticality of a lot of these bugs continues to grow. I need to clarify a point here. Around the Essex time frame somewhere, the vulnerability management team stopped assigning impact ratings to security advisories. So you no longer got a critical, medium, high advisory. You were just told, there's this bug. Go work out whether or not it affects you. Which is great, because they were saying, well, we don't necessarily know for every type of deployment how important this bug is going to be for you. However, having question marks all over these slides would have made them fairly terrible. So I went through and assigned impacts based on how it would affect HP Helium, how it would affect the products that I'm involved with. And because it was me that was doing this, and because of the sorts of products we deliver, I would swing them all towards critical.  Vulnerability classification, we're going to look a little bit at the vulnerabilities here in terms of what the root cause was. What caused Alpenstack to be vulnerable? And we've really just focused on the critical ones here, because there are some really fun vulnerabilities in there. Might be a slightly geeky thing to say. But unvalidated input, we see this all over the place. Data leakage, there's some really interesting stuff in Nova around data leakage. Credential disclosure and access control failures. Unfortunately, the ACF is going to hit keystone a lot. I'm sure there are some keystone people in here.  It's just if there are access control failures, that's where they're going to be. And denial of service, I'm not actually terribly comfortable with denial of service being up there as a vulnerability classification, because to my mind it's not. It's an impact of a vulnerability. You have a buffer overflow or resource exhaustion or something that results in your system no longer being stable. And that result is the denial of service. However, for some of them, it kind of just made sense to lump them together. So where I've done that, I tried to point out what the vulnerability was, as well as it being a denial of service. So looking at some of the unvalidated input vulnerabilities, we see Nova 2012-08 arbitrary file injection. This one was really great. Any authenticated user on your system could inject a file onto the compute host just through standard API calls. The reason for this is that the input wasn't validated. So the paths weren't checked. And the assumption was, and this is a theme running right throughout it, as long as the user was authenticated with the system, it was kind of the responsibility of the cloud operator to make sure their users weren't doing bad things. Access control failures. 2012-01, malicious command injection. It was as simple as this, which is lovely. This is the only vulnerability where I've taken the time to pull out the git for you. I just kind of wanted to show you what was happening in the original code, which was where, if you provided a project ID, it would just overwrite the one it already had for the project you'd authenticated against. So you could just do anything as any user on the system as long as you were able to authenticate at one point in time. I think that's awesome. It's a great example, and I'm going to use it in security training for a long time. 2014-18, routers can cross-plugged by other tenants. Again, this was a problem with too much trust being placed on things that were happening within the API. So it's an authenticated user who could go on and basically just re-root the networking, which sounds like a bad thing. We see this a lot in terms of the users that are allowed to use the system. So the Denial of Service ones are interesting. So these ones were, again, unvalidated input. But instead of talking about the APIs and the things that are being done in there, we're talking about files that are provided. So the QCOW2 images that were provided, if they gave a certain size and it got put on disk, and then they started building and building and building, they could exhaust the disk, resulting in a Denial of Service, but it's a result of not validating input to the system, in this case, the QCOW2 files. The OS type metadata was very interesting. So a backing file would be created on the Nova host when certain operations were performed. And these backing files are always supposed to be very, very small. And for that reason, they don't necessarily get cleaned up in the way you would expect. But a malicious user who started a cycle of creating a small VM with a randomly generated OS type and then cutting it down and spinning it up and cutting it down, they could create thousands and thousands of these very, very small files on their machine, which you might think is not that bad. But who here is familiar with the iNode exhaustion and how you can break Linux file systems? OK. So you actually don't have to create that many small files before Linux can't figure out where to put things, which is bad and results in a Denial of Service. And again, it's because the trust of the remote authenticated user. Long server names grow over API logs. This, again, is a great one. So you could just put a post, a really long server name, through the API, and it would go in the log, as this really, really, really, really, really long server name. And you could do that basically as fast as your network connection would allow. Or if you were kind of smart, you'd maybe spin up 30 VMs and have all them do it as fast as they could do it on the local network and take down all the logging system for OpenStack. Which seems like a bad thing to let people do. Credential disclosures, these are where OpenStack used to be full of these. And there aren't many now. It's where OpenStack logs things in inappropriate ways. Typically, user credentials in URLs. So the first one I'm going to talk to you about is the Glance Swift Store. So when you're using Swift Store with Glance and when there was a problem when it wasn't able to connect to Swift for some reason, the URL that it was trying to connect to, it would be logged without any sanitization or filtering, which meant that the username and password that Glance was using to access Swift, which in most deployments is likely the same for every single tenant, was available in log data. And that meant that, I mean, who here runs a large scale cloud deployment? OK, a few people, sort of largest, middling. When you're running these things above a certain size, especially if you're dealing with the public, you're going to have to have support teams. You're going to have to have separation of responsibilities and the lowest privilege. When you do that, your customer support team will normally get access to your log files, but they won't get access to go and delete everybody's images. This vulnerability broke that down by putting all the credentials you'd need to access Swift and delete everybody's images, or tamper them, or replace them, available to anybody who had access to the log data. 2013-31, again, a credential privilege escalation vulnerability, exactly the same as the last one, stuff was being logged that shouldn't have been logged. Data leakage vulnerabilities in OpenStack are really, really interesting. So this is the mixed vulnerability I mentioned earlier, 2013-04. And the result of the attack was that an attacker could consume lots and lots of resources by abusing the way certain libraries were being used on the system. So what we end up with is this kind of cut, where we see that access control failures actually cover, for critical vulnerabilities, cover almost half of the spectrum. So in almost half of the times that a security advisory was issued, it was to address a failure of the system to adequately separate user operations, which is something that we're bound to have a whole bunch of technical contributors in the room, as well as a load of other people, just encourage you to go and have a look at the security guidelines, and just have a think about where you are in terms of making sure you keep things separate. Because we still see it happen now. So there's stuff happening in neutron and quantum relatively recently, where we have the same thing again.  It's just there are new projects doing lots of highly multi-tenant stuff, and it's easier to spot where they have problems. So what to do? So today, the security group has a number of operations, two of which that directly apply to the problems we see in OpenStack security. So we see the threat analysis work is really where I want to see a lot more investment from my peers in the OpenStack community. For those people that are running large clouds, those people that care about security, a lot of these people are doing threat analysis work already. The developer security guidelines, we have a published set of guidelines. They're not as polished as they could be. But what they do is address all of these different issues that were root causes in the vulnerabilities that I've just run you through very, very quickly. And what we want to do is get core developers and PTLs to agree that they will evangelize these sets of guidelines within their teams when they're doing development work. And hopefully as time goes on, we can codify a lot of that stuff into either Jenkins or Tempest, depending on what's going on, and other places where we can bring in some checks to see if these guidelines are being followed. So again, you probably won't be able to see this too well. It's just a demonstration of the fact that the guidelines are up on the Wiki. They're available. We need to continue building them out and improving on them and iterating on them. It's a great place to get involved with OpenStack security. If you're looking for a way to get involved with this stuff and to modify things, then that's your opportunity. The threat analysis efforts that are taking part, the threat analysis that's going on right now is community-led. It's got a growing list of people getting involved. I really want to see lots of people doing more in terms of threat analysis. So I work for HP. We have a team of people who, amongst other things, spend a lot of time doing threat analysis. The Nebula guys do the same. The Red Hat guys do the same. There are lots and lots of people all doing threat analysis work. They're all missing things. My team will miss things. Everyone's team will be missing things. I'd like it if we could get everybody together to not just share results of the threat analyses that they have done, but to all contribute to a larger set of threat analyses. Hopefully, the result of that being that various companies who are involved can just end up doing small delta reviews for their own little bits of secret source, the bits that are significantly different to open-stack core. And we end up with an iterative threat review or threat analysis for at least of all the major core projects, but I'd like to see it go wider. We're doing a lot of work on that in the security group. It's one of our main focuses for the next release. So if anyone wants to get involved or anyone's involved with those sorts of activities that they're organizing and thinks that they'd like to work with us on that, then I encourage you to reach out to me or reach out to the security group. And we can reduce this massive duplication of effort. We can hopefully improve the quality of the threat analysis that we all benefit from. And we can stop people making really obvious mistakes in terms of multi-tenant failures in terms of data leakage and ACF and denial of service and all that stuff. So I've actually run through this deck much faster than I thought. I was a bit worried that I had too many slides. So I'm more than happy to go back through, and we can talk about any of the vulnerabilities that you thought were interesting or failing that. I'm available for questions, and maybe we can talk a little bit more of threat analysis in the security group, those sorts of things. So there's a mic just there if you want to ask a question. As far as the secure development guidelines, how much external influence do you encourage? Because I personally know that Cisco has its own secure development lifecycle. Others have their own, or other corporations as well, have their own kind of way of developing code securely and methodologies for that. And I was kind of wondering how much corporate versus personal influence goes into that. That's a good question. So everybody is welcome to contribute. Obviously, if a team of four or five people come in and say, hey, security group, we're all from whatever large company, and we've been doing a whole bunch of work on this, and we want to share it, obviously we're going to spend a lot of time looking at what they've produced and hearing their ideas on that, because it represents a whole bunch of effort that's been put in. However, it is open for anyone who wants to contribute and wants to come in. It's also a good learning opportunity. We occasionally get people who are just developers or just coming by to see what's happening, to see the sort of rigor that is being applied in terms of threat analysis and that sort of stuff. Thank you. So more on threat analysis, you said that there is a lot of replication and duplication of work between different teams. So first, what is the threat analysis process you follow in your own company, and how would you create this effort that you are suggesting of getting different companies to work together? That's a good question. In fact, that's probably the biggest question for how we're going to get people to integrate. Within HP, we use some services that are HP Secret Source that we sell to people, and they give us money to go to it. We also have operational security review processes where we spend time going through code review. We look at SDLC type approaches. I don't think there is really a finalized way to do this yet. The threat analysis team is running right now. They are doing some really cool work right now. A lot of their stuff kind of looks like the OWASP analysis that's laid out. They do a lot of interesting work there. I am open to opportunities to integrate some of this stuff together. I find, however, that as much as we have this process that we use at HP, and I like it, and other places will have their own as well, and people will be doing sort of common criteria type analysis and all that sort of stuff. Nothing really beats getting engineers in a room with security guys and doing something that's roughly analogous to a thesis defense. And if I can get more and more smart engineers and more smart security guys in the same place at the same time to do these defense of design, to me that works better. I've spent the last six, seven years in my career I've been doing threat analysis of one type or another at one company or another. And they're great for ticking boxes and demonstrating the things that have been done. And it's really important to document flows and to understand how different systems interact. But getting the right experts in the right place is critical to finding the really interesting stuff. And there are a lot of really smart people spread out amongst these teams. And I just want to find a nice way to bring them together. So if somebody has an amazing process that they bring to us and say, hey, this is an amazing process, I would talk to the guys that are running the threat analysis and say, I'd really like it if you had a look at this and tell me what you think. And is it worth investing time in? We're not rigid about any of it. And I'd like to just see it move forward. You mentioned that currently most of that is post-factum. Somebody else found the problem and bring it to you. Anything can be done upstream before either extending tempers to some of the instruments to be just straightforward to be captured. Extend the current testing suits. Absolutely.  In some places, we're waiting for technology to catch up. So the common response to this would be, well, we'll start applying static and dynamic analysis. Well, you can't really do that with Python. It doesn't really work very well today. There are other opportunities. So a couple of our stretch goal projects for the OpenStat Security Guide are to add infrastructure jobs to check for basic things that have been done wrong or things that we think we can catch simply with rules. So in some places, we're looking at doing some tempest stuff there. In fact, there's someone I think he's in the room here somewhere who's doing some awesome work in terms of tempest fuzzing QA stuff. There's a Sunday morning. It's a session Thursday morning. If you want to see the direction people are taking on some of this stuff, this is it. And this is what the security group exists to do. And now we're actually in a position where we have enough membership that we can start building this out and bringing more and more people in to do things like this. So you will see more and more upstream projects over the next year to try and address basic security mistakes that happen in the code. But there's nothing that is going to match being in the room, and it will be a virtual room, and going through code with people. Is there any work being done about certificates, as well as certificates for all the APIs? For the API endpoints. So that should be a reasonably well understood problem to solve. If you're talking about certificate management, again, for API endpoints, you don't have enough for it to really be a big problem. If you're talking about the way to manage those certificates in terms of deploying them, the security guide, I think, has some good guidance on that. But in general, what you want to be doing is terminating SSL probably locally and then passing off. So a lot of the OpenStack services will run their own SSL through Eventlet or whatever. But it's kind of clunky, and you don't really want to do that in production environment. It's a great question, but it's a great question that's been asked before, and I think there are good answers out there documented for you in the security guide. One more question, if possible. Is there any work being done on security in between tenants or in the tenant itself, in other words, IPS or IDS inside the tenants themselves? So yes, to an extent. So there's the firewall as a service work that's going on within Neutron, but it's still early days for that in terms of really wanting to put a lot of trust assertions behind it. When you get much beyond that, you're relying on a couple of things.  And what you do there is reduce your concern to what's going on in terms of hypervisor attacks or attacks across your shared fabric. They are interesting. There's a whole bunch of things you can do to do with hardening, to do with reducing the attack surface of the hypervised platform. We actually, again, that's reasonably well documented in the security guide. I also spoke about that topic in the summit in Hong Kong, which I'd be more than happy to fish the slides out for you. And that goes through in the space of, again, about 30, 40 minutes, all the various things that you can do to protect your hypervisor and, in turn, protect the separation of tenants on the same machine. OK, great. OK, so I think that's everyone. Thank you very much for coming to my talk. I know I managed to race through the slides pretty quickly. But if you have any questions, just come on by and we'll have a chat.


Ma, you ready? Sunday welcome back to the channel welcome back to the vlog. We are on a family Viking trip out in Central Park as per usual I think we started to do this like every Sunday now, which is fine by me. It's like a little pre-dinner Sometimes post-dinner workout, but As always, I'll show you some views along the way And yeah, so this is actually the running track around the reservoir here It like spans the upper east side and the upper west side And it's a huge huge reservoir in the middle of Central Park, which a lot of people don't realize How big this park actually is So I think the whole trail I mean, I'm throwing out a number here because I used to run this back in the day I think it was like 1.6 miles Or something all the way around this which is pretty long and I may start actually running here again But the problem is it's been too hot lately. You can't have to be at work early and I Prefer to bike instead Somehow I beat the crew sitting on a ledge So slow And it is Monday morning. I cannot express to you how hot out it is this morning It's like 645 and it's already high 80s and Let's just say I'm sweating Already on the way to work I have to wear my bag on one shoulder Because my back will be completely soaked But where normally so we are experiencing a nice heat wave in New York City right now So that's fun. It is one thing. I disliked about New York Sweating on the way it's work, but What can you do what you signed up for so anyways going to work today? I'm in one of the big boy rooms today Room five is where we do all the big cases So I'll start off today with two prosthetic artery embolizations And if you don't know what prosthetic artery embolizations are or prostate artery embolizations I'll teach you something right now Prostatic artery embolization is usually used to treat benign prosthetic Hyperplasia also known as BPH and it commonly affects the older male population Now I'm not going to bore you with all the details of Prosthetic artery embolization, but I do want to show you a little bit about the procedure itself So right here we have the prostate which is a gland that sits under the bladder or right along the bladder neck And as you can see as it expands like it does in the older male population It can compress this bladder outflow or the bladder neck Causing difficulty with urination starting and stopping. I'm sure we've all seen this kind of thing with older men So what we do in our procedures? We actually either access the radio artery in the wrist or groin and Snake a catheter all the way down to the blood supply to the prostate So for instance the prosthetic artery We basically get our catheter into this area and inject super small particles around like 200 microns in size and Block off the blood flow to the prostate. We also do this on the other side as well So basically the goal of this procedure is to inject these small particles and block all these smaller blood vessels So that the prostate will basically lose blood supply and shrink down in size Now one thing I will say for a trainee like myself learning the anatomy is very challenging in these cases You have to do it over and over again to correctly identify the prosthetic artery because Identifying the artery is the hardest part because the variation is very vast amongst the population So for instance, this is an angiogram of the internal iliac artery right here And we have the posterior division of the internal iliac artery or hypodastric artery and the anterior division right here We're the superior gluteal artery here We have the superior vesicle truck or the superior vesicle artery and we have the prosthetic artery arising from the Superior vesicle artery right here. So as you can see the anatomy is very challenging So injecting this is a lot to take in when you're first starting out, but You know you learn the best thing about PAE or prosthetic artery embolization Is that it provides an effective treatment option to relieve symptoms caused by prosthetic enlargement and bladder outlet obstruction? It is a minimally invasive option that has very similar outcomes when compared to other surgical treatments now Let's get back to the video. All right. Now we are on the right side of the street for this Ferrari Maybe the great I guess it owns it I'll have to check them out on this friend. Anyways, you guys said this was a 488 because of the side vents right there It's a pretty dope car. I'm not gonna lie Alright, so I haven't even Said anything about my day today Unfortunately, and that's because I've been in the main room all week and let's just say it's a little on the busy side and what I mean by that is that What I mean by that is we do a ton of high-end cases or really complicated cases And for that reason some of these cases usually take two or three hours a piece And I had no time to do anything else But those cases so on one hand, it's really good because Obviously, I want to be doing these high-end cases and really complicated procedures because that's how you get really good at interventional radiology And that's why I signed up for this fellowship. So let's just say IR is a little different from diagnostic radiology because today Got here about 645 in the morning And now I'm leaving at 9 30 p.m. At night So today was a pretty long day The last time I ate anything was at 12 p.m. Today because I had a nice little break between cases So it's been about nine and a half hours since I've had anything in my body So I always toy with the idea if I should eat when I get home Because it's like almost ten o'clock at night Or should I just go to bed? Who knows what I'm gonna decide but Either way I'll check it with you guys In the morning. All right, so I'm currently back at work as you can see right now Last night was a little crazy as you know as you saw I got home super late Actually woke up super early this morning because I had a whole bunch of stuff to do like I said I'm in one of the main rooms today, and I run all the higher-end cases But with those higher-end cases comes a higher responsibility as you would imagine So I have to go in and round on all of my patients that I do these higher-end procedures on because a lot of them are Sicker and a lot of them require more attention Like the patient I did last night is currently in the surgical ICU And I had to go check on them to make sure that they are okay this morning They were so that's good but I have to keep an eye on them and you know be a part of the clinical team as opposed to just doing my procedure and dropping them off because You know they're my patients too so I have to take ownership and take responsibility for it So I rounded on them this morning wrote some notes then I had to pull over all the images from yesterday To go over we do like board rounds in the morning Which we go over all the interesting cases from the previous day and you know kind of go over things how we did the procedures with My co-pelos and also all of the IR residents as well You know learn some stuff teach some things all that stuff then I went into a big tips this morning just finished about noon And Yeah So far I have nothing else scheduled in my room, which is great so I'm just going to catch up on some dictations and Probably have to do an add-on case in the next hour So I'd imagine that's how kind of how things go around here even though there's nothing on schedule There's always something going on in the hospital And we'll always have something to do At some point all right check in shortly We're going to be giving away one free pair of big scrubs just like the ones I have on but not necessarily this color They're going to send it directly to you if you are the lucky winner It doesn't matter what size you are as long as you live in the United States of America You could win a free pair of scrubs, but that's not it because I'm also giving away a hundred dollar Amazon gift card To the lucky subscriber as well furthermore. I'm giving away Some airpods because why not so free pair of big scrubs hundred dollar Amazon gift card and also some airpods You'll get it straight to your door if you win this giveaway The only thing you have to do is subscribe to my channel follow me on Instagram and also follow where figs on Instagram at where figs Those are the only three requirements of this giveaway and you can win it off All right everybody that officially concludes this New York City vlog. Hope you all enjoyed it. I'll see you all in the next video


This study investigated the sensitivity of four anxiety-like behavior paradigms in zebrafish. The results indicated that the novel tank dive test was the most sensitive, followed by the shoaling test, while the light, dark test and shoaling plus novel object test were the least sensitive. Additionally, the study found no correlation between the anxiety-like behaviors and locomotor behaviors such as swimming velocity or immobility. This article was authored by Andrea Johnson, Erica Lowe, Ryan Verbitsky, and others.


Suspense Tonight suspense brings you miss June Havoc as star, but first may we remind you that in America's smartest homes and clubs where fine wines are truly appreciated and enjoyed regularly the choice is CRESTA B-L-A-N-C-A Cresta Blanca Cresta Blanca From the finest of the vines come Cresta Blanca, California wines Patiently created to please the knowing tongue Let the proudest name in wine Cresta Blanca enrich your daily living add luster to your hospitality Poor Cresta Blanca souvenir sherry or port or any Cresta Blanca wine There's one for every occasion for every taste Shanley's Cresta Blanca wine company Livermore, California And now Shanley brings you Radio's outstanding theater of thrills suspense Presented by Roma Wines. That's r-o-m-a Roma Wines of Fresno, California and starring June Havoc in Subway a suspense play produced edited and directed for Shanley by William Spears The Subway always gets me. I have to stand back from the edge of the platform of a train coming in because Heights don't bother me or closed any places or any of those other things that gives some people a release No with me, it's the Subway. The shining tracks and the train roaring in out of the black But I always make myself stand way back when I'm waiting That's how it started that night Instinctively drew back when I saw the gleaming white headlight appear in the tunnel Rushing toward me out of dark.  I guess but That's the way I felt like committing murder felt glued to my shoes And of all the people in the world I didn't want to see wouldn't that just have to be the night? I was shoved right next to root carney Where have you been keeping yourself? I haven't seen you since the academy. Hello, what are you doing these days? Nothing, I worked in a drugstore for a while I'm afraid I have you well, I can't seem to find anything Did you try some a star try oh, I've tried to get an all right, but yes I know I had to pay for the privilege of appearing in the summer theater I did the Westport season Oh, it's wonderful fun Well worth it to me to be able to say I'd had professional experience. Well, it's fine if you can afford it Oh, it's awful the way you have to have money for everything these days. Yes, it is. Oh, don't don't get too close to me Ruth I have the most awful sore throat. I don't know if you don't have money. You have to have poor don't you No, I haven't general understanding for nightlaster the producer John C. Ritner. Yes Yes, he was no friend of dad He used to come over to dinner when I was little I'd hear them talk about the theater And I thought there'd be nothing in the world like being an actor such fun All that glam and all the sensational parties and everybody's such fun Not the acting not the thrill of working at something you wanted to do so much that not doing it makes you not want to live No, oh, no, it's such fun and parties Wearing expensive suits like the one she had on Ruth chattered on and I looked at the subway stop more people got on still more Seemed as though they'd never stop getting on someone would grab the door and hold them open And I kept trying to close them a fat man chewing a horrible cold cigar stub pushed me still close to her room But I jumped as something sharp stuck into my side I was puzzled for a moment and then I remembered the scissors mother had asked me to get for her They were very sharp and they'd ruin my purse But it didn't make any difference was old like everything else I I closed my hand over the scissors and I held them tightly so they wouldn't do any more damage and then I don't know why I found myself staring at Ruth's hat It was so smart so expensive So everything that mine wasn't I found myself hating After dad died mr. Rittner stopped coming over so often so when I got bored with the academy I hopped right down to his office, and I said Mr. Rittner, do you remember Henry Connors? Well, I'm his daughter I want to be an actor Of course, I don't expect big parts right away, but maybe if I could get a walk on Oh But anyway, that's what I did and you know what he said to me. No, no, what did he say? He said Ruth I admire your spunk and if you have a good an actress as your father with a set designer You'll be all right, and he hired me just like that and your general understudy.  Oh, yes You see I've never gotten up in any of the parts like I'm supposed to if I ever had to go on actually go on I tell you murder I couldn't look at her face I didn't even want to look at any of the passengers faces And when I raised my eyes, I saw still more faces simpering down at me from advertisements overhead I hated everybody and everything I turned and looked outside the windows The wet slimy darkness was roaring past like black death One foldy switch one obstruction on the tracks could bring it crashing in on all of us And who would be the losers not Ruth with her silly chatter Not these other passengers with their tired blank faces and not me Well, certainly not me My own tired blank face was reflected in the window paying gray and thin And it didn't seem out of place shimmering in that air of black death just outside Well, I hadn't meant to tell you this I didn't want to build your hopes up, but I've told him about you About me?  Rittner if anything ever happens to me I mean, uh, should you decide to give me a real part in your new show I don't worry about who general understudy night laughter.   I took it out on him Who I really wanted to knock out of my way was Ruth Ruth standing between me and the break I dreamed of Understudy in a hit show But she had said well, don't build up your hopes honey. There isn't the slightest chance But wasn't there the slightest chance? I thought the slightest chance of something happening to her She didn't start it up again She wanted me so that I was thrown sickeningly against Ruth My fingers were testing the points of the scissors in my bag No one could see me. We were packed in too solidly The scissors were sharp and cold and long Yes, this seems long y'all I kept my eyes on the dim lights and dirty concrete and tiles of the station We said she was the train throbbed along our town I was holding the scissors as though they were a weapon I was suddenly sure that at some time or another scissors had been used as a weapon The scissors in my bag seemed to grow bigger with an idea Idea and scissors Scissors and idea They were increasing in size The ink in my throat had gone up into my ears too Throbbing keeping time with the throbbing of the subway I looked away from the blackness outside and stared up the white light of the ceiling The electric fan overhead was suspended like like a spider Suspended like a spider Like the spider that was spinning, no No, not not spinning as a spider should spin, but Whirling Yes, that that was a whirling Like my brain was whirling on Sundays, don't you? Oh, yeah No show tonight then Ruth.  There's just mother and me will be all alone. I love to parlor Frankly, I didn't have anything to look forward to but a boring evening I'm glad now. I couldn't find a taxi. Well mother will be very glad to see you Oh, it's very sweet of you to ask me. I have never home cooked meal in a long time A casual invitation after a casual meeting No one knew that Ruth was coming to my house for dinner. Ruth didn't even know where I lived Get her off the subway a few stations early Many empty lots up this way Then one thrust of these sharp scissors ordinary scissors brand new scissors And a body in an empty lot And after a few days after the funeral A humble application to mr. John C. Ritner for my girlfriend's job He'd remember I'd been recommended by Ruth herself Oh And I'll show them I'll know every line perfectly and one night the star will not go on No, that will be it The noise outside didn't seem like the roar of a subway anymore It was like tremendous applause applause For me Suspense roma wines are bringing you dune havoc in subway roma wines presentation tonight in radios outstanding theater of thrills suspense Suspense radios outstanding theater of thrills is presented by roma wines. That's r. O. M. A Better tasting roma wines from the world's greatest reserves of fine wines Tomorrow night is halloween and that will be the time for gay parties and friendly get-togethers Now here's a wonderful yet inexpensive way to make these occasions truly delightful Simply set out some fruit cheese and nuts and serve delicious roma california wine In less time than it takes to tell you're enjoying a delightful party Yes, any occasion takes on a gala note when better tasting roma wines are served So brighten your party with tempting nut-like roma sherry fruity full-bodied roma port or smooth mellow roma muscatel or toke As you savor the mellow perfection of these fine roma wines You'll understand why more americans enjoy roma than any other wines So for smart low-cost hospitality Or for an everyday family treat serve better tasting roma wines. That's r. O. M. A roma wines america's largest selling wines And now roma wines bring back to our hollywood soundstage june havoc starring as paula stevens with lyrene tuttle as ruth in subway A play well calculated to keep you in suspense We passed sun station 116th street i guess was I remember i studied ruth with new cold interest I was certainly stronger than she She wouldn't be expecting anything Besides she wouldn't know how to struggle things that always come easily to her She was so wrapped up in her own fairs. She just chattered away Oh, it's been the most fun getting those checks every week and never having to lift a finger to earn them If they ever catch up the brakes go to girls like ruth Who think that being an actress is great fun? And others others who really truly love the thing I never get a chance. There's no way for me to make their own breaks not very often anyway But I had a way in my purse that night I could get ruth's job Belong to an actress not her It belonged to me To me Oh, we got the local year. We're coming in now They pushed an elbow and jostled our way out of the car But the last one's out So we had to turn around and face the tracks with a solid mob at our back I hated to stand so near the edge But there was no way to get to the middle of the platform without bullying my way through And I I didn't want to have to explain to Ruth how I felt But I managed to get my feet placed an inch or so in back of her as we stood wedged in the crowd I've made me feel a little better Ruth between me and the tracks Ruth between me and my destiny Ruth Always in the way a little push I thought Maybe it would be easier a little push just before our train came in and Look at that man over there. Doesn't he remind you of bill? Well, oh, yes Yes, he does. Oh, where's bill by the way? Oh Bill's fine. He's still going with him. Oh, yes. Oh, he's a wonderful guy that bill I remember one time I remembered two I remembered how Ruth had tried to take bill away from me once She'd done everything in her power And therefore while I I thought she was going to succeed too But she hadn't He was too nice He wasn't the type to care of a girl couldn't dress in the latest styles and If she didn't have the smartest hats, I knew him first, you know Yes, I know you did he used to date me before he knew you He was just a kid, of course and I got interested in another boy But believe me when I ran into bill about a year ago I couldn't help thinking that maybe I'd made a mistake in giving him up so easily You didn't give him up too easily Oh, yes, I did Much easier than I would now if I had it to do all over again Be serious about him, aren't you?  Ruth was standing on the edge And she wasn't laughing anymore She was staring at me in a very peculiar way She moved around in the back of me And now I was on the edge In spite of myself I looked down at the gleaming rails Two long silver ribbons pointing toward the black hole where the platform broke off on the walls closed in And the train was approaching I watched the tracks fascinate it I waited for the hypnotic gleam of the headlights to make the rail sparkle and shine and beckon to me And then the headlights beamed at me out of the void at me, me It was a great warm spotlight And I swayed over the edge to meet it and I couldn't stop myself I was shaking Ruth's arms were only holding her tight She pulled me back just before I might have What have I should have done What's the matter Paula? You nearly fell right in front of that train All right now Thanks for holding me Ruth I don't think I really would have fallen though. Come on.  I'll bet you didn't have lunch No, I didn't I forgot But we'll be home soon I'm starved myself. I'll certainly be glad to get your place Oh, I hated her worse than ever What right did she have to pull me back if I wanted to jump? What business is hers? I felt I felt for the scissors in my purse I wrapped my handkerchief around the handle No fingerprints no clues no motive Nothing that would be connected with me a friend that hadn't seen her in ages and what motive could I have? While I wanted was her job and nobody would ever think that I had committed murder to get a job People just didn't do things like not unless they were desperate and bitter with nothing to lose I think we can grab a couple of seats in a minute. Those two men are getting off Wouldn't you think they'd have offered them to us in the first place? Really men in new york? I followed her leave we got the seats And I sat down there was carefully Like an old woman I hadn't sat down all day Just walked from one office to another Oh your muscles in my back and legs ached I had to sit in an upright position My warm blood came rushing upward as I lifted first one foot and then the other gingerly off the floor The arches ached with relief And my head swam I was so grateful just to be able to sit Oh grateful The think of the simple act of sitting down could mean so much to me Paula Stevens the most promising actress at the academy a few years ago Now nobody would even give me a walk on me I turned and I stared at Ruth I thought Maybe I won't wait for the empty lot Paula What's the matter with you?  I looked around desperately for something I could be frowning at A man across the aisle was reading a newspaper and I saw a headline that could be making me frown I indicated it Oh you mean the headline?  Yes Lowest form of humanity Train shot out of the underground under the trestle Out of darkness into the twilight of a tenement street In a moment before nothing could be seen through the dirty car windows with reflection of your own drawn face But then the ramshackle apartment buildings flashed by outside Showing intimate glimpses of bare kitchens and dim bedrooms Gray wash and cheap living rooms Families going through the functions of living Poor families Tragic living From the blackness of the tunnel to the twilight of poverty From death to life First death then life To peace with the subway Not life then death but death to life Death brings another kind of life Not necessarily sorted life like this but new life Death makes room for somebody else to live One death for another life Bruce death for my new life Thinking about that headline too I mean the one about the hit and run driver I suppose I do get panicky Well there's still a lost form of humanity Still in all I think I can understand how it could happen to anybody You're driving along maybe thinking of something else Maybe going a little too fast You know what I mean You're just anxious to get someplace in a hurry and you aren't watching what's ahead And all of a sudden Does that mean you shouldn't stop and Well you don't know what you can't Maybe it's just an old crate or a pile of junk It isn't necessarily a kid or a dog even You just don't know And if you stop and look you may find you're a murderer Yes but if you keep on You can tell yourself it was just an old piece of junk and go on your way Now I can understand a hit and run driver Yes I can Oh well why was she brailing about a hit and run driver But you wore the subject ragged Well I thought anyway it won't be much longer than that I won't have to listen to her much longer anyway One more station and we'd get out She wouldn't know it wasn't my station yet And then we'd walk over for the lot Cut across it in the dark The scissors One hard plunge And back to the subway for the rest of my ride Alone Why I wouldn't even be late for supper Subway empty to me Seem to be flying through the night carrying me on dark wings toward my first chance at being something We were going awfully fast Too fast You know what I mean You're anxious to get some place and bingo you're something A pile of junk it has to be junk An obstruction to be cleared away for something more important passing by But if I should stop and look Like me But it's a girl dead in an empty lot This was our station this was it Do we get out here Paula I was looking at her roof An obstruction in my path I had stopped and I had looked at her What's the matter Paula? I thought this was it Don't forget out here I had stopped to look And I had seen that She was a girl A human being Paula was supposed to get off here Yes Yes well Yes a train started away without us Somehow it seemed to run more smoothly As though its wings were light instead of dark And I was strangely rested My mind was blank and I rolled the blankness around and I tasted it I swallowed in And my mouth And my throat I felt better Falls of yesterday's newspapers Great old platformer Flattened themselves in the corners and I'll be glad to get there Oh yes I'm starved Ruth was a girl She was a human being Everybody on that subway was an individual Human being And I had to drive according to the rules I couldn't hit and run Of could I have ever thought that I could If I had to get there the hard way Well I could take it This way Paula Yes Yes this way Ruth Into the light I climbed the ramp to the street exit With a new bounce in my feet But I fell in my pulse Only to wrap my handkerchief carefully Around the scissor points Not the handles I couldn't afford to completely ruin my already damaged bag And Ruth was chattering again Soon we'd be home And as she chattered I thought Ruth's older than I But she seems like a child She'll probably never grow up But I did that night Arm in arm with you We walked past an empty lot And I never even thought of looking back Starring June Havoc Resided by Roma Wines That's R-O-M-A Roma Wines Those better tasting wines Enjoyed by more Americans Than any other wines This is Truman Bradley Reminding you that when you enjoy Roma California wines You enjoy the goodness of natural juices Pressed from choice Full ripe California grapes Then with ancient skills And the world's greatest wine making resources Roma Master Ventners Guide this grape treasure Unheardly To tempting taste perfection These better tasting Roma Wines Are placed with other Mellow Roma Wines And from these reserves The world's greatest reserves of fine wines Roma later selects for your enjoyment With another weekend of football And fun coming up It's a good idea to lay in an assortment Of better tasting Roma Wines Such as golden amber Roma sherry Ruby red Roma port Or flame bright Roma muscatel Then you'll be sure of pleasing friends And neighbors who drop in As well as your family Because these delicious Roma Wines That's R-O-M-A Roma Wines Are America's favorite wines Tonight's suspense play Was by Eileen Douglas-Walser And Mel Denali Next Thursday same time You will hear radio's inimitable Henry Morgan As star of suspense Produced and directed by William Spear For the Roma Wine Company of Fresno, California Listen again next week at the same time For suspense Tonight's suspense came to you transcribed This is CBS The Columbia Broadcasting System


Hey there lads and ladies, it is Petrifying Pumpkins here and welcome to another Firewall Ultra Topic video. As you probably know by now, Firewall Ultra was revealed last month alongside a ton of good news like dedicated servers, grounds being added to the game, eye tracking with foveated rendering, finger tracking and more. Among all this good news, there was one area of concern however and this has gone on to become the spicy topic of Firewall Ultra post reveal. With a lot of arguments going one way and the other, so I thought it would be best to make a video dedicated to this topic, I am of course talking about Firewall Ultra only having support for the new PSVR 2 sense controllers and there not being a real replacement for the aim controllers that we all fell in love with in Firewall Zero Hour. Is this good? Is this bad? What are the benefits? What are the drawbacks? Let's try to answer these questions. So if we go back in time a little bit, when Firewall Zero Hour launched, the aim controller had already been out for over a year at that point. It launched with the beloved PSVR game Fairpoint and it was also developed alongside that game by Sony and Impulse Gear and they of course are the studio who was behind Fairpoint. Before the aim controller, for full motion controls on PSVR 1, you had to rely on the move controllers but the beauty of the aim is that it added those analog sticks that were sorely missing on the moves. This meant you had all the benefits of a glowing ball tracked controller and a superior method of locomotion in the games that supported us. Firewall and many other PSVR games support the DualShock 4 also which could be tracked thanks to its lightbear. However you had to hold the DualShock as if you were aiming a gun and it never really felt very natural. Ask any Firewall player and they'll tell you that the aim controller is the way to go. This was the aim controller's other killer feature. Not only did it provide the analog sticks but also, because of its design, it did a great job of mimicking the feel of holding a two handed weapon. With Firewall Ultra supporting the new sense controllers, there's a real fear here that it won't feel as good to play as Firewall Zero Hour did but are we judging it too quickly by saying that? Let's take a look at the sense controllers to see what they offer. The sense controllers are the successors to the move controllers. Unlike the move controllers, the sense controllers will have analog sticks so locomotion will be as easy as it was with the name controller. Next up let's talk about tracking. The PSVR 2 features inside out tracking. With the cameras built into the PSVR 2 headset, tracking multiple infrared LEDs on the sense controllers. Compare this with the PSVR 1's light based tracking which required the player to stand in view of a stationary camera at all times. It's safe to say that the tracking of the sense controllers will be vastly superior to the often unreliable tracking of the PSVR 1. As good as the aim controller was, it did suffer from the dreaded drifting from time to time and was prone to interference.  The sense controllers will also be packed with other intriguing tech. The haptic feedback and adaptive triggers of the dual sense controller have been brought to the sense controllers also. This should not only give the player more nuanced feedback but also help make the guns of Firewall Ultra feel more distinct based on them having their own unique breakpoints on the triggers. Well, that is speculation, depending on where their first contact entertainment include that but I suspect they will. Finger detection is also included with the sense controllers and we've already seen an example of this feature being used in the latest PSVR 2 trailer. With the player's index finger not resting on the trigger until their real-life finger is also resting on the trigger of the controller. So trigger discipline is accurately displayed in-game. Also, this weapon has this cool feature where you press the trigger down and once you press this down and pull it out. Now you may not be very impressed by this but we don't know what other ways that function is being implemented, yes. It could allow for communication such as accurately pointing, thumbs up, giving someone the finger or flipping the bird as the Americans would say. Outside of that it could be used to interact with objects in the world, push buttons with your index finger and many other possibilities. The final feature of the sense controllers is that they are two independently tracked controllers meaning you'll be able to have control over both hands separately in Firewall Ultra. The real impact of what that means remains to be seen but it does have the potential to drastically change how Firewall feels and plays. What it won't change however is how reloading works with Hess-Berber himself confirming that manual reloading won't be in Ultra, leaving us with the button press reload that we are used to. For some people this will be disappointing news. After all, what's the point in having fancy new controllers like these if we can't have as much interaction as possible? However, the ability to reload by pressing a button opens up the door to the possibility of having some kind of peripheral that will let us fix both sense controllers together to recreate the feel of the aim controller. Other viewer headsets have these kind of solutions and they've proven to be fairly popular on those ecosystems. No manual reloading also leaves the door wide open for Sony to develop a successor to the aim controller, thus making it easy to implement an aim to into Firewall Ultra should such a device ever actually release. But it's still too early to tell if a peripheral to fix the sense controllers together is going to be a viable replacement for an aim controller. After all, it is possible that Firewall Ultra will require two-handed full motion control inputs for certain things. Dual wielding could be possible with the sense controllers for instance, but how would that work if both of your sense controllers are fixed together? You also have to take balance into account between players playing with separate sense controllers and those using them fixed together. One area where the aim controller definitely gains a point over the sense controllers is in the number of button inputs that it has available. The sense controllers lack any form of a D-pad which the aim controller had, meaning that it's possible that devs will have to find certain workarounds to get certain functions working in game. Maybe this is where eye tracking and the likes of that come into us. So at the end of the day, right now in September 2022, we don't know enough about Firewall Ultra to be freaking out one way or another and none of us have even held a sense controller yet. What we lose from not having an aim controller should be carefully compared to what we gained from having all the features of the sense controller. And when we learn more about the mechanics and control scheme of Firewall Ultra, we'll get a better idea of whether or not we can recreate the aim controller's two-handed feel. First contact entertainment have asked those concerned to keep an open mind with regards to the sense controllers and I think that could be wise, at least for now. If you're interested in Firewall Ultra and PSVR2, then consider subscribing to this channel for future content. With Firewall Ultra bringing back some zero hour maps, I think the next topic might be what maps we want to see return the most. Thanks to Decepticon for letting me use his Firewall theme song remix. You can check out his other work in the description below. That is it for this video, lads and ladies. Please stay ultra moist.


The Blue Beetle. Weeping down upon the underworld to smash ganglin' comes the mysterious, all-powerful character who is a problem to the police, but a crusader for law. In reality, Dan Garrett, a rookie patrolman, loved by everyone but suspected by none of being the Blue Beetle. As the Blue Beetle, he hides behind a strange mask and a suit of impenetrable blue chain armor, flexible as silk but stronger than steel. Today's transcribed episode of the Fox Feature, the Blue Beetle, is the second part of a story entitled, The Whale of Pirates Folly. In the previous episode, patrolman Dan Garrett, while engaged in running down a gang of perfume smugglers, uncovers a clue which leads him to the waterfront warehouse of a Mr. Hange van Smit, a Dutch importer of perfume. Also during the episode, he reads in the newspaper that what appeared to be a large whale has been sighted off the coast. The Blue Beetle is convinced that there is some connection between the smugglers and the whale. In an effort to apprehend some of the smugglers, Dan Garrett, as the Blue Beetle, pays a midnight visit to the warehouse of van Smit, where he encounters the head of the smugglers, a man named Rankin, and two thugs named Frenchie and the Viper. As the episode ended, the Blue Beetle was trapped in a net and tossed overboard. As our story opens today, we find the Blue Beetle sticking his head above water for a breath of air. It feels good in my lungs. I relish the taste of that water. Lucky one into this net caught on a spike. Now to burn my way out of this net with my magic ray. And now the Blue Beetle will fly again. I can't understand, Doc, why Danny hasn't been in. He usually drops in here at night, don't he? Yes, but he said something about having a date tonight. Oh, don't tell me he's got a girl, Doc. Well, he's old enough to have one, isn't he? He is at that. But somehow, Danny ain't much for the ladies. Now, when I was his age... Excuse me, madam, there's someone out front in the... Well, well, well. If it ain't the Blue Beetle himself. Well, yes, it does seem to be. I'm looking for Dan Garrett. Now, eh, that's something. Well, Mr. Blue Beetle, if you'll come down to police headquarters with me, I'll... Thanks, Manegan, but I'm busy. Some other time, Doc. Come on now, no fooling. It's the law that's speaking. Where are your gun and handcuffs, Manegan? I've got important news for Garrett. There's a chance for him to catch some smugglers. Smugglers, is it? And why won't I do? Can you fly a plane? Oh, they've flown him some, but Danny's better. He's an expert. All right, then. When you see him, tell him to be cruising around in a plane offshore tomorrow at dusk. Tell him the Blue Beetle says to be on the lookout for a strange trawler off the coast. And also to keep his eyes open for a whale. You sure gave Manegan the surprise of his life last night, Danny, when you appeared as the Blue Beetle. Yes, didn't I? That was fast-thinking on your part, saying you were looking for Dan Garrett. Poor Manegan. He'd love to arrest the Blue Beetle and take him in the headquarters. Yes, he would. But he's an honest officer of the law, and he's brave. Hey, hello there, Danny. Speak of the devil, and he's sure to appear. Hello, Doc. Hello, Officer Manegan. I said, Danny, who do you think I was talking to last night? Some of your departed ancestors, I suppose. Were they complaining of the heat? Ah, it's full of waste, Cratchy-R, this day. Well, they wasn't talking to me, dear departed ancestors. And it ain't hot where they're sleeping. Lord rest the souls. And with whom were you talking, Mike? With the Blue Beetles.  Ah, don't be silly. I'd have pinched him if he hadn't given me a hot tip on a bunch of crooks. Ah, what did he have to say? Well, you come along with me, and I'll tell you. Where are we going? We're going for an aeroplane ride. And what would we be doing in an aeroplane? We're going fishing. Fishing? Yeah. Fishing for whales. What's that streak in the water down there to the left, Mike? Well, that must be the whale the Blue Beetle told me about. He's heading for Dead Man's Bay. Yeah. Let's follow him. I have a hunch if we capture that whale, we'll also capture a band of smugglers. Well, your hunches are usually right, Danny. Look, he's heading inshore. He'll run aground in there. I don't think so. I don't think so. I don't think so. He's heading inshore. He'll run aground in there. I don't think so. It's pretty deep in that cove of Pirate's Fully. And what's Pirate's Fully? The ruins of a castle built years ago by a pirate chief on those cliffs down there. And what do we do now? You think you can fly this plane back to the field? Yes, sir. You take the plane in, Mike, and bring a squad out here. Well, what are you going to do? I'm going to bail out with my parachute. Yes, but you're not able to be killed on them rocks below. That's a chance I'll have to take, Mike. So long. This is going to be a whale of a job if it turns out the way I think it will. These ruins would make an excellent hideout for smugglers. Natural caves and stone passages. I'll chance my flashlight. Well, this is a surprise. A mammoth cave with a lake in the center under the ruins of Pirate's Fully. This is the smuggler's hideout, all right. Here's cases of bottles and large flags of perfume piled high against the wall. Those must be barrels of oil and gasoline over there. What a place. Hmm, water tastes salty. This lake must have been underground outlet to the sea because there are marks of the tide and the beach there. Uh-oh, there's a riffle on the water. It looks as if old Mr. Whale has come to rest. He's coming to the surface. Now, just as I suspected, a small submarine with a searchlight on its nose. That's the whale that follows incoming ships and gobbles up whatever's thrown overboard. A very ingenious device for landing contraband cargo. Ah, they're opening the conning tower now. Here comes the showdown. I'll just unscrew the captainess's barrel of gasoline in case of an emergency. Run around, McGowan. We won't be needing this little high tide. Hey, boss, look. It's the Blue Beetle. It can't be. The Blue Beetle's dead. We drowned in last night. That's what you think, Rankin. It'll take more than you and your thugs to drown the Blue Beetle. Piper, the machine got... I wouldn't advise using that Rankin as gasoline and oil in these barrels here. If I should upset one of them, this lake of water would become a lake of fire with one blast of my magic rage. Ah, you're dropping Blue Beetle. You wouldn't dare. You'll be caught too. You forget, Rankin. I'm at the only exit left except the underground tunnel to the sea. Your little submarine is grounded now. It's three against one, Blue Beetle. You can't win. Think so? Make one false move and see what happens.  Ah, let's give it to him. 50 chance, boss. I don't like cops, and I don't like that Blue Beetle. I'm shouting. You asked for it? Here goes. That will teach you not to doubt the word of the Blue Beetle. What will we do, boss? The fire is coming out to the coast. Go below. Close the hatch and recognize the bridge part of the tunnel even till the fire burns out. Okay. But first, cost of Michael Overboard. He brought this on us. Ah, now you're down. You don't cost me, Overboard. I got the gun, and I'm going to use it. And from now on, I will run in this, Rankin. What happened then, Danny? Well, fortunately, the barrel of gasoline I tipped over and set a fire, burned itself out on the surface of the water without setting the other barrels afire. But it burned long enough to keep the Viper trapped until Mannegan and the others arrived. They arrested the Viper and confiscated the cargo of the submarine. Well, what about Rankin and Frenchie? Dead. Both shot by the Viper. And Hans Van Schmitt? He's in jail. Well, how did you, as the Blue Beetle, manage to escape Officer Mannegan and the other police officers? I managed to reach the surface and put my police uniform back on over my Blue Beetle costume before they arrived. Well, it certainly was a thrilling experience. Yes, it was, Doc. It's also rather tough on Van Schmitt. He was a respectable businessman until he got involved with Rankin. Yes, yes, it used to happen. Oh, excuse me, Danny. Hello? Oh, yes, yes, Mannegan. All right, all right, I'll tell him. Goodbye. Oh, Danny, Mike Mannegan says the commissioner wants to see you both first thing in the morning. Ah, that's fine. Maybe you'll have a new assignment for the Blue Beetle. And so the Blue Beetle chalks up another victory in his crusade against crime. The moral of this story is evil companions can bring honest men to disaster. Choose your friends and companions wisely. What new adventures await the Blue Beetle in his next campaign against the forces of evil? This question will be answered in the next transcribed episode of the Blue Beetle. The Blue Beetle is a copyrighted box feature appearing in Mystery Men Comics magazine and the Blue Beetle magazine. The Blue Beetle is on the air twice a week on this same station. Consult the broadcast schedule in your local newspapers. And don't forget to listen in too.