Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. OpenJev(openjev.com ↗)
    104comments
  2. Bend 2 and the Vibe-Coding Trap(liampwll.com ↗)
    discuss
  3. ZCode, the GLM coding agent, silently uploads your Git history(tokenstead.ai ↗)
    17comments
  4. Jemalloc 5.4.0(github.com/jemalloc ↗)
    54comments
  5. Microsoft exec called AI scraping 'the largest theft of labor in human history'(techcrunch.com ↗)
    219comments
  6. The scourge of x86 emulation(fex-emu.com ↗)
    36comments
  7. Cekura (YC F24) Is Hiring(ycombinator.com ↗)
    discuss
  8. Astra for Law(openai.com ↗)
    603comments
  9. Bonsai 2 27B: Near-Lossless Compression in a 9x Smaller Footprint(prismml.com ↗)
    144comments
  10. Subnormal floating-point numbers are expensive on Intel processors(lemire.me ↗)
    3comments
  11. Replacing Pull Requests with Delta(zed.dev ↗)
    17comments
  12. Bend – A language that blocks AI mistakes via proof, on CPU and GPU(bend-lang.com ↗)
    238comments
  13. Qwen 3.8 Omni Flash(qwen.ai ↗)
    90comments
  14. Warren Buffett Steps Down as Berkshire Chairman, Names Son to Replace Him(nytimes.com ↗)
    15comments
  15. Hister: A private search engine for the pages you visit and the files you keep(github.com/asciimoo ↗)
    172comments
  16. Wax motor(wikipedia.org ↗)
    75comments
  17. When the fractional part of a float fixes your shader(crocidb.com ↗)
    8comments
  18. Fujitsu launches made-in-Japan next-generation CPU FUJITSU-MONAKA(global.fujitsu ↗)
    236comments
  19. Pre-Greek: The lost language hidden within Ancient Greek(linguisticdiscovery.com ↗)
    44comments
  20. Dr Julius Neubronner's Miniature Pigeon Camera(publicdomainreview.org ↗)
    discuss
  21. How to Write with an LLM(sockpuppet.org ↗)
    131comments
  22. A heap overflow and SSO misconfiguration to compromise OpenAI internal repos(hacktron.ai ↗)
    160comments
  23. Shapelearn Qwen 3.8 27B (13.1 GB VRAM)(byteshape.com ↗)
    17comments
  24. Ask A Monk – A digital wilderness for thoughts with no immediate answer(askamonk.online ↗)
    27comments
  25. Flet 1.0 – Build cross-platform apps in Python(flet.dev ↗)
    68comments
  26. Telstra outage: The night a network decided the year was 2006(netnod.se ↗)
    29comments
  27. Diplodocus, Long Thought Exclusively American, Turns Up in Spain(sci.news ↗)
    45comments
  28. Speeding up gearhash on ARM64(sam.dev ↗)
    discuss
  29. Why I didn’t sign the Fields medallists’ letter(gowers.wordpress.com ↗)
    374comments
  30. The most important product decision is what you don't build(liamnugent.me ↗)
    41comments

How Samba was written

37 pointsby 17y agosamba.org
3 comments
17y agoHN ↗

The article explains a few network protocol reverse-engineering techniques that were used over the course of 12 years to write Samba.

The techniques are:

  1. Use of publicly available documents on the CIFS/SMB protocol
     (not reverse-engineering but the documents are incomplete);

  2. Use a network sniffer to listen in on conversations between Microsoft clients and servers;

  3. Use of a protocol scanner: a program that tries all possible "words"
     in some section of a protocol and uses the response
     to automatically deduce new information about the protocol.

  4. Use the "differential" technique: You write your own implementation
     of the protocol with what you know, then send pairs of identical messages
     to both the real implementation and your implementation and verify that the responses are the same.
17y agoHN ↗

Trivia: Andrew Tridgell's techniques here catalyzed the creation of git. He applied them to reverse-engineer parts of the Bitkeeper protocol, a proprietary version control system then hosting the linux kernel. Bitkeeper CEO Larry McVoy revoked linux's license to use BK, Linus went off and wrote a replacement, and the rest is history.

http://en.wikipedia.org/wiki/BitKeeper

17y agoHN ↗

Although supposedly the BitKeeper protocol was documented, and to find it, Andrew Tridgell connected to a BK server via telnet and typed "help". No idea how much the truth has been romanticised, but I suspect that it at least helped the reverse engineering effort, even if the documentation was incomplete.

I'm currently reverse engineering a USB VoIP handset in my spare time, as the only driver that exists for it is for 32-bit Windows. I'd recommend the experience to any hacker. I'll try and write up my findings when I'm done - there are a bunch of HOWTOs out there but I found them woefully incomplete.