BuuQu9hu

32 ms·

1. 241.▲
   Is your internet up to date?(en.conn.internet.nl)

   150 points by BuuQu9hu 10y ago|73 comments
2. 242.▲
   Tails: Social Contract(tails.boum.org)

   3 points by BuuQu9hu 10y ago|0 comments
3. 243.▲
   New Debian Developers and Maintainers (November and December 2016)(bits.debian.org)

   1 points by BuuQu9hu 10y ago|0 comments
4. 244.▲
   Measuring execution performance of C++ exceptions vs. error codes(nibblestew.blogspot.com)

   78 points by BuuQu9hu 10y ago|70 comments
5. 245.▲
   Wanted: your wishes on managing author identity data in KDevelop(frinring.wordpress.com)

   1 points by BuuQu9hu 10y ago|0 comments
6. 246.▲
   Debian Policy(debian.org)

   1 points by BuuQu9hu 10y ago|0 comments
7. 247.▲
   by BuuQu9hu 10y ago

   https://www.youtube.com/watch?v=kQTW7Pd1vqc
8. 248.▲
   by BuuQu9hu 10y ago

   N900 is coming back: https://neo900.org/
9. 249.▲
   Finding a Libc for tiny embedded ARM systems(keithp.com)

   3 points by BuuQu9hu 10y ago|0 comments
10. 250.▲
    by BuuQu9hu 10y ago

    Perl gives you plenty of rope to hang yourself with. That isn't a good thing in any language.
11. 251.▲
    by BuuQu9hu 10y ago

    Decompilers exist (like Boomerang), but it is more likely the author used something like IDA Pro, which has a code flow graph feature. http://boomerang.sourceforge.net/
12. 252.▲
    Elphel: Lens aberration correction with the lapped MDCT(blog.elphel.com)

    1 points by BuuQu9hu 10y ago|0 comments
13. 253.▲
    Hacker Noir, chapter 1: Negotiation(noir.liw.fi)

    1 points by BuuQu9hu 10y ago|0 comments
14. 254.▲
    Crossgrading Debian in 2017(simonrichter.eu)

    3 points by BuuQu9hu 10y ago|0 comments
15. 255.▲
    The importance of the press kit(opensource-usability.blogspot.com)

    1 points by BuuQu9hu 10y ago|0 comments
16. 256.▲
    ModemManager in OpenWRT (take #2)(sigquit.wordpress.com)

    2 points by BuuQu9hu 10y ago|0 comments
17. 257.▲
    by BuuQu9hu 10y ago

    Wow, that is scary
18. 258.▲
    by BuuQu9hu 10y ago

    We can't solve device security, period. Regulation isn't going to help and effective regulation would be way too costly.
19. 259.▲
    Monitordarkly: run code on your monitor(firmwaresecurity.com)

    2 points by BuuQu9hu 10y ago|0 comments
20. 260.▲
    by BuuQu9hu 10y ago

    Monitors still contain firmware and can be hacked: https://firmwaresecurity.com/2016/12/12/monitordarkly-dell-m...
21. 261.▲
    by BuuQu9hu 10y ago

    Got a link?
22. 262.▲
    by BuuQu9hu 10y ago

    Firmware should be on the board before you buy it.
23. 263.▲
    by BuuQu9hu 10y ago

    Start small (fixing typos for eg), read code and fix issues you notice in the process. Also, check out Kernelnewbies: http://kernelnewbies.org/
24. 264.▲
    by BuuQu9hu 10y ago

    See debdelta
25. 265.▲
    Address Sanitizer local root exploit(openwall.com)

    1 points by BuuQu9hu 10y ago|0 comments
26. 266.▲
    by BuuQu9hu 10y ago

    Lucky 10000: We have observed humans evolving on reasonably fast time scales: https://www.sciencedaily.com/releases/2009/11/091120091959.h...
27. 267.▲
    by BuuQu9hu 10y ago

    For this reason alone, I have refused to use Truffle. Consider the RPython toolchain, from the makers of PyPy; it does a similar thing (turn an interpreter with light annotations into a JIT compiler) but you are in no legal danger.
28. 268.▲
    by BuuQu9hu 10y ago

    Most of them will be identical for your requirements, continue using what you're using already, you can copy over the whole system with dd.
29. 269.▲
    Tails: Our plans for the coming years(tails.boum.org)

    4 points by BuuQu9hu 10y ago|0 comments
30. 270.▲
    by BuuQu9hu 10y ago

    Just use Tor.