Printable True Bugs Wait Posters

I’ve uploaded printable #truebugswait posters. You can download the full set 8 1/2 x 11 (A4) here (PDF here), and 11×17 (A3) here (PDF here). Everyone is free to print and use these.

The posters have also been updated to contain a QR code which links to a page on why to avoid each function.

Posters:

arithmetic8x11

By subject:

Uncategorized

17 responses to Printable True Bugs Wait Posters


  1. Great stuff here :D For interactive example of xtrcpy vulnerability check this demo:
    http://viralpoetry.org/en/strcpy.html

  2. Introspection Exception

    I was going to strcat you to my favorites list. Then I thought, woah! That just wouldn’t be safe. So first I freed all my literal strings, because you can’t be too safe.

  3. Isn’t the real solution to dangerous intercourse on the internet, to avoid C altogether?

  4. The fact that the kid on the first poster looks like one of the backend devs at my office (I’d guess he’s not much older) alone made me LMAO. I’ll be showing these posters to my coworkers on Monday. ;)

  5. anon

    Dave, C is a beautiful and sacred thing when used by responsible adults. You shouldn’t write if off entirely just because you’re not ready.

  6. Pingback: To LOLz and Back. This is just too much. : Uncommon Media

  7. Stefan Metzeler

    Just don’t use C, C++ or any other C-related programming language!

    Even the syntax of those languages is dangerous and misleading! The human brain is not good at recognizing symbols and parenthesis, it excels at reading WORDS.

    Full words are not a problem – you either learn proper touch-typing or you use keyboard shortcuts to generate the keywords and structures for you in a good programming editor.

    The best language so far is hands-down Obern-2 by Prof.Wirth (creator of Pascal and Modula-2 as well).

    It’s highly readable, extremely easy to learn (20 pages of documentation), more expressive than C++, none of the defects and generates fully optimized binary code that typically runs faster than C++ and without all the traps and pitfalls, as it has garbage collection and does automatic bounds checking.

  8. Nate

    Before I read natashenka’s website, I was using pickles for every database. Now I know better.
    Having sex with my code never felt so secure.

  9. Pingback: Security News #0×64 | CyberOperations

  10. Bill Tyler

    Reminds me of the first computer I ever programmed, an IBM 1620, back around 1965. You could wipe out the entire memory with any one of several machine language instructions. The simplest was Transmit Field Immediate. It worked like this. The memory consisted of decimal digits, each of which had an additional flag bit that was used to mark the ends of data objects. Transmit Field Immediate had two operands, a destination address and the literal source data. The usual use would be to put a small constant somewhere. It picked up the source data digit by digit, copying it to successive digits starting at the destination address, until copying a digit with the flag on, which indicated the end of the field. If the destination address happened to fall within the source data, the terminating flagged digit could be overwritten by unflagged digits, so the termination was never read. And because the address registers of the machine wrapped around modulo memory size, the instruction in fact never terminated until someone manually hit a console key.

  11. Pingback: vtluu.net » Blog Archive » Abstain from using unsafe string and memory handling functions!

  12. Pingback: Link blog: funny, C, philosophy, shuffle | Name and Nature

  13. Pingback: Февральская лента: лучшее за месяц

  14. Pingback: Link blog: funny, philosophy, mohammed, twitter | Name and Nature

  15. Pingback: Cavalcade of Mammals » Blog Archive » Links for April 2014

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>