Hacker News

Top stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. I Built Non-Autoregressive Decision Models with RL a Year Ago(convaiinnovations.com ↗)
    159comments
  2. AI-generated posters don’t have to be horrible(john.hartnup.uk ↗)
    522comments
  3. Human brain is two separate organs, Stanford Medicine-led research finds(stanford.edu ↗)
    194comments
  4. Tin: full-text search for Postgres(planetscale.com ↗)
    52comments
  5. A graphical desktop for the ZX Spectrum(github.com/mindbox77 ↗)
    79comments
  6. “The Secret Life of Circuits” is here(coredump.cx ↗)
    58comments
  7. Android 17 is the first since 3.x to add new APIs without releasing to the AOSP(grapheneos.social ↗)
    571comments
  8. Supabase (YC S20) Is Hiring for OrioleDB(supabase.link ↗)
    discuss
  9. Black Holes or Black Hole Stars? Astronomers Spar over 'Little Red Dots'(quantamagazine.org ↗)
    20comments
  10. New evidence for hidden chambers beyond Tutankhamun's tomb(nature.com ↗)
    9comments
  11. GPT-6 Astra Solves a WWI German Radio Cipher(prinzai.com ↗)
    141comments
  12. San Francisco Onion Futures Company(onionfutures.com ↗)
    125comments
  13. Almost Never Use AI to Write Anything Substantive(erichgrunewald.substack.com ↗)
    21comments
  14. What Zig felt like, coming from Rust(besok.github.io ↗)
    134comments
  15. If math is more than proof, we need to better celebrate the rest of it(terrytao.wordpress.com ↗)
    203comments
  16. Cloudflare Quick Tunnels(cloudflare.com ↗)
    301comments
  17. How to Write with an LLM(sockpuppet.org ↗)
    364comments
  18. People who know the most often sound the least certain(vrash.substack.com ↗)
    1comments
  19. Asking Authors About Their Own Papers(medium.com/tmlrorg ↗)
    47comments
  20. Adventures in Microcontroller Circuit Debugging(bigmessowires.com ↗)
    1comments
  21. You can run Git on object storage if you re-make packfiles(tigrisdata.com ↗)
    28comments
  22. Saving another 100TB of RAM(cloudflare.com ↗)
    93comments
  23. Communication by means of modulated Johnson noise(pnas.org ↗)
    21comments
  24. SDCC – Small Device C Compiler(sourceforge.net ↗)
    25comments
  25. Science Is Open Software(jepedersen.dk ↗)
    51comments
  26. OpenJev(openjev.com ↗)
    283comments
  27. Why building a Rust LSP is hard(rust-glancer.github.io ↗)
    50comments
  28. Ray Ozzie and the Optimism of Being Early(reproof.app ↗)
    16comments
  29. The first new cat species discovered in 100 years(nationalgeographic.com ↗)
    128comments
  30. How OpenAI Used Its Own LLMs to Design Its Jalapeño Chip(ieee.org ↗)
    123comments

Ask HN: Text-based web-browsers. Are it affected by Meltdown and Spectre?

3 pointsby 8y ago
4 comments
Most popular web-browsers (Mozilla FireFox, Gooogle Chrome, Pale Moon, etc.) already work on solving issues related to Spectre and Meltdown attacks and this month rolled out it's security updates.

Text-based[1] web-browsers (such as Lynx, Links2, etc.) are much simpler than 'normal' browsers, so could they be affected by Meltdown and Spectre? Are there any news on security issues for text-based browsers related to such attacks?

[1] https://en.wikipedia.org/wiki/Text-based_web_browser

P.S.: I use Links browser in graphics mode as default browser on my PC, and this post also submitted throw it ;-)

  $ links2 -g http://news.ycombinator.com
8y agoHN ↗

Those browser's vulnerability to those attacks are entirely based on the fact that they execute JavaScript. Thus, if your browser doesn't execute JS, it's immune.

8y agoHN ↗

Thus, if your browser doesn't execute JS, it's immune.

I hope on that, but it would be cool get more details why text-based browsers are much more secure than modern browsers in 2018.

P.S.: Screenshot[0] from my web-browser with this thread.

[0] http://hnng.moe/f/ZZJ

8y agoHN ↗

That is the complete explanation… JavaScript. Executing arbitrary code from strangers on the Internet is what makes browsers less secure.

8y agoHN ↗

Possibly.

Because Meltdown and Spectre are vulnerabilities caused by CPU design, any running code is potentially vulnerable. Text based browsers are not safe merely because they do not run javascript, they are only safe in that case from javascript being able to exploit the vulnerabilities. The application itself may still be vulnerable.

You should contact the maintainers of these projects directly and find out from them.