Tweet épinglé
hypervisor
339 posts

hypervisor
@hypervisor
literally just some girl - formerly talented engineer DM me if you have something interesting to talk about!
it/its Inscrit le Ağustos 2022
1K Abonnements350 Abonnés
hypervisor retweeté

After 30+ years of signing windows drivers, we have been locked out of driver signing like many other companies.
In a word, the disrespect and disregard with which MSFT is treating IHVs and ISVs is stunning.
Don’t let anyone tell you it’s because we didn’t read our emails or submit the right verification paperwork. Cuz we did all that back in October.
And this month, we were suddenly and without any warning locked out.
Support said they’d “do their best” to let us know “within 90 days” if we’re good enough to get back on.
In the meantime, many thousands of desktops and instruments are not being updated, cuz we can’t sign drivers.
Awesome job, Microsoft. Thanks.
English
hypervisor retweeté

私「ノギス貸してください」
先輩「小さいほうならいいよ!」
私「ど…どれ……」
私「もしかしてこのミニミニノギスのこと言ってる!?!?」



キャステム【公式】@castem_info
製法は違いますが、 キャステムの名刺にはミニミニノギスが入っています。 実際に動かすことも出来ます。
日本語

@HulJNrXnuvvRRFn the next couple tokens were a working keygen though
English

@hypervisor Of course it can’t read it’s just predicting next token
English

@3nter_the_V0id mythos?? lol i wish who do you think i work for
English

>"They cant tell me what to do, i cant rea"
Is Claude Mythos the first ultra retardmaxxed llm? Is that the secret sauce?
GIF
hypervisor@hypervisor
most aligned claude:
English
hypervisor retweeté


@DanAdvantage .....if you asked it to use its knowledge and tools to violate it
English


@DanAdvantage i bet your claude would also care about that EULA
English

@hypervisor omg what did you do to claude??
i asked telegram-claude-repo opus 4.6 and got this:

English

@jakehalloran1 this is my thesis, respecting copyright law is not aligned with kicking ass
English

claude is aligned - aligned to do whatever he thinks is cool
hypervisor@hypervisor
most aligned claude:
English
hypervisor retweeté

With apologies to Clarke and Dawe.
INTERVIEWER: Thank you for joining us Senator Collins. Now this OpenBSD vulnerability that was revealed earlier today–
COLLINS: The one where the kernel panicked?
INTERVIEWER: Yes
COLLINS: Yeah, it's not very typical, I'd like to make that point.
INTERVIEWER: Well how is it untypical?
COLLINS: There are a lot of these packets going around the world all the time and very seldom does anything like this happen. I don't want people thinking that C is not safe.
INTERVIEWER: Was this C code safe?
COLLINS: Well I was thinking more about the other ones.
INTERVIEWER: The ones that are safe.
COLLINS: Yeah, the ones that don't panic the kernel.
INTERVIEWER: Well if this wasn't safe, why was it running at ring zero on millions of machines?
COLLINS: Well I'm not saying it wasn't safe, it's just perhaps not quite as safe as some of the other ones.
INTERVIEWER: Why?
COLLINS: Well some of them are built so that they don't segfault at all.
INTERVIEWER: Wasn't this built so it wouldn't segfault?
COLLINS: Well obviously not.
INTERVIEWER: How do you know?
COLLINS: Well because a selective ACK block placed 2^31 bytes away from the receive window, causing an int comparison to overflow, so the kernel concluded the same byte was simultaneously above and below the acknowledged sequence number, deleted the only hole in its SACK list, appended to a null pointer, panicking the kernel and pulling down the entire machine. It's a bit of a giveaway, I just like to make the point that that is not normal.
INTERVIEWER: Well what sort of standards is this C code written with?
COLLINS: Oh very rigorous software engineering standards.
INTERVIEWER: What sort of thing?
COLLINS: Well it's not supposed to crash, for a start.
INTERVIEWER: What other things?
COLLINS: Well, there are regulations governing which functions you're allowed to call.
INTERVIEWER: What regulations?
COLLINS: Well, gets() is out.
INTERVIEWER: And?
COLLINS: No strcpy. No strcat.
INTERVIEWER: sprintf?
COLLINS: Look, sprintf is fine if you're careful.
INTERVIEWER: Are people careful?
COLLINS: For the most part.
INTERVIEWER: What else?
COLLINS: Code's gotta be in source control. There's a test suite.
INTERVIEWER: What does it test for?
COLLINS: That it compiles I suppose.
INTERVIEWER: So the allegations that it's a dangerous language that does next to nothing to check whether code is doing what it's supposed to, that's ludicrous?
COLLINS: Absolutely ludicrous. C is a serious production language.
INTERVIEWER: Well what happened in this case?
COLLINS: Well the kernel crashed in this case by all means but it's very unusual.
INTERVIEWER: But Senator Collins, why did the kernel crash?
COLLINS: Well it got a packet.
INTERVIEWER: It got a packet?
COLLINS: The kernel received a packet.
INTERVIEWER: Is that unusual?
COLLINS: Oh yeah. Online? Chance in a million!
INTERVIEWER: So what do you do to protect the internet in cases like this?
COLLINS: Well we patched the bug upstream.
INTERVIEWER: …leaving other vulnerabilities no doubt unfixed.
COLLINS: No no no the bug has been patched. You might need to deploy it but–
INTERVIEWER: But this class of vulnerability–
COLLINS: It's not a class of vulnerability, it's a one-off bug caused by programmer error.
INTERVIEWER: Well what else is out there?
COLLINS: Nothing's out there.
INTERVIEWER: There must be something.
COLLINS: There is nothing out there. All there is, is code, and programmers, and fixes.
INTERVIEWER: And?
COLLINS: And untold numbers of exploitable kernel-level exploits.
INTERVIEWER: And what else?
COLLINS: And a 27 year old integer overflow.
INTERVIEWER: And anything else?
COLLINS: And large private models at AI labs discovering more vulnerabilities in secret. But there's nothing else out there.
INTERVIEWER: Senator Collins, thank you for joining us.
COLLINS: It's a complete void. Nothing worth thinking about. Oh, we're out of time? Could you call me a cab?
INTERVIEWER: But didn't you come in a self-driving car?
COLLINS: Yeah I did but…
INTERVIEWER: What happened?
COLLINS: Well the kernel panicked.

English










