I think, i think collectively, and i think ubiquity is very popular in the tech heavy set, because there were a lot of sesos that i talked to that day when we all got the ml and went a crap, and then went about changing our passwords, and then siped about what possibly could have got along. Absolutely.

And you know, the i guess the one positive thing was that in the old days, we'd probably have to run home to do it. So at least this way we were already theree the power of the cloud. Absolutely. And so so brian crabbs actually published an article this week that was pretty good. Ie. He generally has some pretty interesting insights into security. I'll just, i'll just grab a couple sources, or a couple of sentences here that read for the folks, just to get setsome context, cause i think it's actually really interesting. So, so he published this article, basically, a whistle blower from inside the company had come forward. And and the way he described it was that a source who participated in the response to the breach alleges that ubiquity massively down played a catastrophic incident to minimize the hit to its stock price, and that a third party cloud provider claim was a fabrication. Ubiquity said it became aware of unauthorized access to our information technology systems hosted by a third cloud party provider. This is amazon a adam. This is the name, the pseudonym that's been given to the whistle blower. Said that the attacker had access to privileged credentials that were previously stored in the last pass account of a ubiquity i t employe, which gave hem rute administrator access to all ubiquity a w s accounts, including us, three buckets application logs, data bases, et cetera. And then when security engineers removed the back door in the first week of january, right around the time that we were about to get our e notifications, the intruders actually sent a ransom demand to ubiquity, saying that for 50 bit coins, about two point eight million dollars, dollars, they would remain quiet about the breach, essentially asking for them to commit some form of cover up. They actually sent proof that they had ubiquity source code and pledged, theywd pledged to kind of come back and get them, cause they had planted multiple sort of a back door account. So that that's a pretty, pretty big bombshell ought to be coming from a whistle blower, i guess it took me a little bit of time to kind of churn through this, but i think, starting from iv, that the credentials came from last pass, which means that we had probably a single factor protection on a number of different resources. T, that's obviously not a good thing, i but just, i think this kind of, jeff, you know, it sort of frames the discussion we had when joe sullivan joined us a while back, about the right way to kind of describe a breach. And i'm just kind of, i'd love to get your take first before we get into the whistle blow. R like ubiquity issued a pretty standard breach disclosure ad. Probably could find some of the same verbiage in other companies. And technically it's correct. Was there announcement enough yet?