Secure Tips retweeted
Replying to @bobby85323
It cant be disabled. Find a phone that is 5+ years old and use only that.
Secure Tips retweeted
Protip: Avoid the intel kernel memory protection flaw by running all of your code within Minix inside Intel Management Engine.
(i.e. everything is terrible. and it goes way down, so go all the way down.)
Secure Tips retweeted
Once execute-only memory is commonly available, it will be an ideal opportunity for people to hide their GPL violations. #justsaynotoXOM
Secure Tips retweeted
rm -f /usr/bin/gcc #poormansexploitmitigations
Secure Tips retweeted
Replying to @SecureTips
@SecureTips Always use = instead of == for comparisons in C code to avoid unnecessary performance overhead.
Secure Tips retweeted
Sweetie @SwiftOnSecurity, I love you but I got to say that @SecureTips is the best twitter ever !
Secure Tips retweeted
Replying to @SecureTips
@SecureTips Match your browser and OS versions for best performance. Use Firefox 10 and Chrome 10 on Mac OS 10 and Windows 10.
Secure Tips retweeted
oh, wow OpenSSL:
strncpy((char *)p, s->ctx->psk_identity_hint, strlen(s->ctx->psk_identity_hint));
Secure Tips retweeted
Bugs like CVE-2014-0160 are why you should never use SSL/TLS on production web servers.
Secure Tips retweeted
Replying to @i0n1c
@i0n1c my friend @securetips (aka @dinodaizovi ) said to properly terminate string you should: dst[strlen(dst)] = 0x0;
Secure Tips retweeted
Advisory: GCHQ keygenme suffers from a BO via malformed license.txt and insecure use of fscanf(). cc: @SecureTips
Secure Tips retweeted
Leveled up to Busticati level. @securetips certified. http://twitpic.com/58z2gv
Secure Tips retweeted
@shydemeanor @SummerC0n @SecureTips SecureTips is the conference overlord.
Secure Tips retweeted
Replying to @SecureTips
@SecureTips PROTIP: Unfollow all security experts except @SecureTips to make sure you only receive fully-validated security advice.
Secure Tips retweeted
PROTIP: Following @securetips gets you 16 CPE credits for your CISSP!
Secure Tips retweeted
Replying to @SecureTips
@SecureTips Your most secure servers should be on obscure and/or obsolete architectures, because noone writes exploits for them.
Secure Tips retweeted
Replying to @kernelpool
@kernelpool @securetips I'd also recommend free()'ing every pointer, just in case. Memory leaks can be very bad.
Secure Tips retweeted
Replying to @SecureTips
@SecureTips I'd wrap subsequent free() calls in try/except blocks to improve program stability

















