What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
0
0
0

"SCE to AUX" the famous words said by EECOM engineer John Aaron that saved the Apollo 12 mission.

On Nov 14, 1969, Apollo 12 was struck by lightning twice in the 1st minute after launch, causing a major power outage in the spacecraft. All 3 fuel cells got disconnected from the power bus; the inertial navigation system went awry.

Switching the Signal Conditioning Equipment to auxiliary power restored telemetry to mission control and to computing equipment.

nasa.gov/history/afj/ap12fj/a1
1/n

1. Diagram of Panel 3 on the Main Display Console. SCE switch is circled.
2. Pic of bottom of panel 3 with the SCE power switch.
3. EECOM engineer John Aaron in Mission Control. Photo from NASA History Office.
0
0
0

https://www.youtube.com/watch?v=K3S1j1Z2r18

남대문 카메라 딜러 아저씨의 유튜브 영상인데, 파나소닉 코리아가 심각하네... 신품 구매자여야 3년 AS, 중고 구매자는 신품 구입 시의 영수증 요구도 문제지만 대리점에서 신품 판매한 후에 정품 등록하려면 본사에 전화해야 한다니, 온라인도 안 되고 시리얼 관리도 안 되고 이게 지금 2020년대 맞나 싶을 지경. 연친분이 AS에 고생하셨던 게 우연이 아니었구나.

파코가 저러는게 안마의자 때문에 바뀐 거라던데, 이래서야 이제 어떻게 파나 카메라 사겠냐 싶다.

0
2
0
1
0
0
1
0
0
0
0
1

For folks who missed my keynote or talk, I wanted to pull out the two key points.

The first is that CHERI solves memory safety, but that’s almost incidental. I don’t want to downplay addressing the root cause of 70% of vulnerabilities but that’s not the goal. CHERI was originally designed to support scalable fine-grained compartmentalisation. To do that well, you need a programmer model. You need to be able to share things programmers understand (objects, in object graphs) not pages. And that means you need to be able to trivially map your protection up to language-level constructs like pointers / references and protect both them and the objects that they refer to. And so you need to build memory safety. And, it turns out, making an entire program memory safe is much easier than making just an exposed API memory safe. So we have memory-safe C/C++ and we can use those from languages like Java or Rust to ensure that the C/C++ doesn’t violate the guarantees that the safe language’s security depends on. And then we can use that for easy to use compartmentalisation, safe FFI, supply-chain security, and many more things.

The second is that CHERI is still quite young. I gave a talk about how CHERI impacted OS design. That’s like, in 1985, asking someone from IBM to give a talk about how MMUs impacted OS design. They would tell you you could create VMs to consolidate multiple minicomputers onto a single mainframe. They would tell you that you could enforce process isolation. And, just like the things we can do with CHERI today, these are hugely valuable. But they wouldn’t tell you about using Zygote models to speed up process creation. They wouldn’t tell you about how memory-mapped files could enable new I/O models. They wouldn’t tell you about how IOMMUs could enable kernel-bypass storage and networking. They wouldn’t tell you about how MMUs can introduce lightweight GC barriers. They wouldn’t tell you about how MMUs enable lightweight CoW snapshots for time-trace debugging. Because, although a lot of the hardware existed for these things (and the rest was a fairly small incremental tweak on existing ideas), most of these software uses hadn’t been invented.

CHERI is exactly the same. We have barely scratched the surface of what CHERI can let you build. The BLACKOUT work (presented at CCS and again at CHERITech) is another great example of this. I had never thought of using CHERI as a building block for providing a clean programmer model for avoiding side channels, but some other smart people did and proposed a really interesting model for doing so. I hope future CHERI systems will incorporate something based on this work.

As with MMUs in the early ‘80s, we have no idea what people will be building on top of CHERI in ten or twenty years. Many of these things will be possible on existing implementations, some will require hardware changes. This is why it’s very important for the RISC-V CHERI standard to be designed with agility in mind, so that future hardware can continue to add new and exciting features without breaking backwards compatibility for software. I think we’re on a good path to that.

0
0
1

[立院修法光電加嚴環評 7大公協會:能源轉型大挫敗⸺中央社](cna.com.tw/news/afe/2025111500)

"立法院會14日經表決三讀通過環境影響評估法部分條文等,台灣太陽光電產業協會等7大公協會發出聲明,直指為「台灣能源轉型大挫敗」,將波及95%守法業者,使台灣綠電新增量大幅放緩,RE100企業勢必面臨綠電稀缺與成本墊高的壓力,並衝擊半導體、AI與出口產業的國際競爭力。"

//藍白真的要毀了台灣。

0
0
1
3
2

中國政府呼籲中國人不要到日本旅遊、香港保安局在旅遊警示網頁中也更新資訊,指「自2025年中起,中國公民在日本發生遇襲事件的趨勢漸增。特區政府呼籲計劃前赴或已在當地的港人應提高警惕,注意安全」

同頁尚有地震、熊害的資訊

但除福島第一核電廠附近區域外,香港目前並沒有對日本發出旅遊警示

0
1
0
0
0
0
0
0
0
0
0
0
0

六花亭のお菓子をマルセイバターサンドだけだと思っているのは本当にもったいないので皆さん機会があれば六花亭のお菓子セットを買ってください。全部美味いんで。

1
1
0
0
0
0
1
0

Why does people who never been to Palestine, never met a Palestinian, never been affected by a Palestinian hate them so much.

Most of them are not even Israeli or Jewish, but they just hate innocent people of Palestine who only want to live their lives in their ancestral home.

They have been watching them suffer for over 70 years with blessing of the entire western world.

I don't get it!

@palestine@lemmy.ml
@palestine@fedibird.comPalestine_Group

0
0

For folks who missed my keynote or talk, I wanted to pull out the two key points.

The first is that CHERI solves memory safety, but that’s almost incidental. I don’t want to downplay addressing the root cause of 70% of vulnerabilities but that’s not the goal. CHERI was originally designed to support scalable fine-grained compartmentalisation. To do that well, you need a programmer model. You need to be able to share things programmers understand (objects, in object graphs) not pages. And that means you need to be able to trivially map your protection up to language-level constructs like pointers / references and protect both them and the objects that they refer to. And so you need to build memory safety. And, it turns out, making an entire program memory safe is much easier than making just an exposed API memory safe. So we have memory-safe C/C++ and we can use those from languages like Java or Rust to ensure that the C/C++ doesn’t violate the guarantees that the safe language’s security depends on. And then we can use that for easy to use compartmentalisation, safe FFI, supply-chain security, and many more things.

The second is that CHERI is still quite young. I gave a talk about how CHERI impacted OS design. That’s like, in 1985, asking someone from IBM to give a talk about how MMUs impacted OS design. They would tell you you could create VMs to consolidate multiple minicomputers onto a single mainframe. They would tell you that you could enforce process isolation. And, just like the things we can do with CHERI today, these are hugely valuable. But they wouldn’t tell you about using Zygote models to speed up process creation. They wouldn’t tell you about how memory-mapped files could enable new I/O models. They wouldn’t tell you about how IOMMUs could enable kernel-bypass storage and networking. They wouldn’t tell you about how MMUs can introduce lightweight GC barriers. They wouldn’t tell you about how MMUs enable lightweight CoW snapshots for time-trace debugging. Because, although a lot of the hardware existed for these things (and the rest was a fairly small incremental tweak on existing ideas), most of these software uses hadn’t been invented.

CHERI is exactly the same. We have barely scratched the surface of what CHERI can let you build. The BLACKOUT work (presented at CCS and again at CHERITech) is another great example of this. I had never thought of using CHERI as a building block for providing a clean programmer model for avoiding side channels, but some other smart people did and proposed a really interesting model for doing so. I hope future CHERI systems will incorporate something based on this work.

As with MMUs in the early ‘80s, we have no idea what people will be building on top of CHERI in ten or twenty years. Many of these things will be possible on existing implementations, some will require hardware changes. This is why it’s very important for the RISC-V CHERI standard to be designed with agility in mind, so that future hardware can continue to add new and exciting features without breaking backwards compatibility for software. I think we’re on a good path to that.

0
0
1

10월 20일에 마우스 해외배송을 시켰는데
10월 23일에 발송이 지연되어 12월 8일 도착 예정이라는 톡을 받았지만
그렇게 급하지는 않으니 그냥 기다려야지 하고 주문취소를 하지 않은 과거의 나에게 곤장 100대형을...
:ablobcatreereach:

1
0

Man darf wegen hunderten faschistischen Polizisten nicht die Polizei unter "Generalverdacht" stellen.

Man darf wegen hunderten korrupten Politikern nicht die Politiker unter "Generalverdacht" stellen.

Aber man darf alle dunkelhäutigen, alle Flüchtlinge, alle Bürgergeldempfänger, alle Nicht-Bio-Deutschen, alle Alten, alle Armen, unter Generalverdacht stellen.

Sagen Polizisten und Politiker

0
0
0