Tips to help you stay secure!

San Francisco, CA
Joined January 2011
Replying to @bobby85323
It cant be disabled. Find a phone that is 5+ years old and use only that.
14
37
10
125
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.)
Once execute-only memory is commonly available, it will be an ideal opportunity for people to hide their GPL violations. #justsaynotoXOM
2
11
1
10
Secure Tips retweeted
rm -f /usr/bin/gcc #poormansexploitmitigations
4
18
21
Secure Tips retweeted
Whatever happened to @SecureTips ?
2
2
Replying to @SecureTips
@SecureTips Always use = instead of == for comparisons in C code to avoid unnecessary performance overhead.
6
21
26
Sweetie @SwiftOnSecurity, I love you but I got to say that @SecureTips is the best twitter ever !
1
3
3
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.
13
6
oh, wow OpenSSL: strncpy((char *)p, s->ctx->psk_identity_hint, strlen(s->ctx->psk_identity_hint));
20
134
86
Secure Tips retweeted
Bugs like CVE-2014-0160 are why you should never use SSL/TLS on production web servers.
1
50
50
Secure Tips retweeted
Replying to @i0n1c
@i0n1c my friend @securetips (aka @dinodaizovi ) said to properly terminate string you should: dst[strlen(dst)] = 0x0;
11
10
Advisory: GCHQ keygenme suffers from a BO via malformed license.txt and insecure use of fscanf(). cc: @SecureTips
5
21
1
Leveled up to Busticati level. @securetips certified. http://twitpic.com/58z2gv
@shydemeanor @SummerC0n @SecureTips SecureTips is the conference overlord.
Replying to @lennyzeltser
@lennyzeltser Do everything @SecureTips says.
Secure Tips retweeted
Replying to @SecureTips
@SecureTips PROTIP: Unfollow all security experts except @SecureTips to make sure you only receive fully-validated security advice.
PROTIP: Following @securetips gets you 16 CPE credits for your CISSP!
9
2
Replying to @SecureTips
@SecureTips Your most secure servers should be on obscure and/or obsolete architectures, because noone writes exploits for them.
13
3
Replying to @kernelpool
@kernelpool @securetips I'd also recommend free()'ing every pointer, just in case. Memory leaks can be very bad.
Replying to @SecureTips
@SecureTips I'd wrap subsequent free() calls in try/except blocks to improve program stability