- Feature Articles
- CodeSOD
-
Error'd
- Most Recent Articles
- A Dark Turn
- Nothing Doing
- Home By Another Way
- Coast Star
- Forsooth
- Epic
- The State of the Arts
- Planing ahead
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
This is all too easy. Simply analyze traffic according to RFC 3514, and only apply proper cryptography to all legit usecases. Problem solved.
Admin
RFC 3514 is just about the stupidest idea I've ever read. It is a utopian pipe dream which may never be accomplished because of its fundamental incompatibility with how the world works. The document has no basis in anything even approaching reality, for one simple reason: There are simply too many preexisting devices which do not implement it and will never be realistically updated to conform to RFC 3514. Bolting it on after the fact in the form of an extension is impossible, the evil bit should have been in IPv4 from the very start.
Admin
Do note the publication date of that RFC 3514
Edit Admin
Before saying things like this, please read the RFC very carefully, especially the date of publication. Geeeeeezussss.
Edit Admin
Everybody gotta be a noob sometime. Today is no's day.
Admin
I think No may be joking, given the comment about the Evil Bit at the very end.
Edit Admin
Such a shame there's no "like" button on these "forums"...
Admin
JUST NERD EVEN HARDER!
Admin
In the beginning, there was FILE *f1 = 0;, which should have been FILE *f1 = NULL; to illustrate that FILE * is a pointer. If you do it, do it consistently (even if it's not needed, dangerous, or plain wrong). Later on, regrding MY_FREE: Checking a pointer for not being NULL before calling free() isn't actually required. Current malloc implementations simply do nothing if you call free(NULL);, as seen in the manual, so no problem. Additionally, it seems like someone believes that calling p = NULL; will magically erase from memory whatever p has been pointing to, violating the rule that thou shalt nott touch ay pointre after free()ing... but hey, don't worry, next week they're going to build secure online banking software!
Admin
I suspect that "no" understands all this and was trying to joke just as much as "JPJ". It does beg the question though - should the evil bit have been added to IPv6 from the start? :)
Edit Admin
Wait, nobody has pointed out Remy's mistake yet? The function does not always return 0!
Admin
Actually, there is something wrong with checking a pointer for NULL before freeing it: as anyone who knows C knows,
free(NULL)
is guaranteed to be a safe no-op.Edit Admin
True enough. One time in 256 it returns 1...
Edit Admin
I think the guarantee about
free(NULL)
was a later add-on, not in the original C, so many old-timers used their own checks, and the habit persists to this day.Edit Admin
I hope not, seeing as how free(NULL) is a no-op at least as long ago as C89...