Developer fixes 33-year-old Unix bug
An OpenBSD developer has discovered and fixed a bug in the software that has been traced back to an AT&T version of Unix from 1975.
OpenBSD is a variant of the Berkeley Software Distribution (BSD), a widely used, open-source, Unix-like operating system. BSD's variants include OpenBSD, FreeBSD and NetBSD, and it forms the basis of Apple's Mac OS X operating system.
The latest bug, which affected the yacc parser generator, followed the May discovery of a BSD flaw that was 25 years old.
Otto Moerbeek, an OpenBSD developer, found the bug through the process of testing a new implementation of malloc, a general purpose memory allocator. A user alerted him that on the Sparc64 hardware platform and using the new malloc, compiling large C++ projects would sometimes fail with an internal compiler error.
He found that the bug was in yacc, a parser generator developed by Stephen C. Johnson at AT&T that has been a standard part of Unix since the 1970s.
"Funny thing is that I traced this back to Sixth Edition Unix, released in 1975," Moerbeek wrote in a note describing the bug.
The new malloc was able to trigger the bug because its new features give it a better chance of catching buffer overflows, Moerbeek said. He noted that the bug is only triggered on Sparc64 systems.
In May, Marc Balmer, a Swiss developer closely involved with OpenBSD, found a 25-year-old flaw that proved to exist in all BSD variants including derivatives such as Mac OS X.
Commentators on IT enthusiast websites noted that 1975 is not long after the very beginning of the Unix universe, at least according to the system time used in Unix-like dating systems, which count time in seconds starting at 00:00:00 1 January, 1970.
» posted by ITworld staff
Techworld.com
Sign up for ITworld's Daily newsletter
Follow ITworld on Twitter @IT_world
On Twitter now
OpenBSD
Powered by TwitterOn Twitter now
OpenBSD
Brian Proffitt
Microsoft/Novell: Breaking Down the Coupon Numbers
Esther Schindler
Drupal's Dries Buytaert on Building the Next Drupal
Tom Henderson
Top Ten General Operating Systems Rants
pasmith
PS3 motion controller delayed; goes up against Project Natal
sjvn
Neolithic Windows security hole alive and well in Windows 7
claird
Perl source code comparison makes for good reading
mikelgan
Cell phones don't create stress or interrupt much
Sandra Henry-Stocker
How to: The Unix Interview
Where Google Chrome security fails: the password
I heard mention that the Chrome OS will have some sort of encryption available a la bitlocker. If it's possible to encrypt personal data using another password or key, then it may have potential for very secure data.... And Ubuntu has an 'encrypt home directory' option, perhaps google should follow suit.
- Dann
Join the conversation here
Quick, practical advice for IT pros. Made fresh daily.
- Ubuntu advances: Why Ubuntu server installations will surge in 2010
- Social media marketing: How to make friends with benefits
- More...
Want to cash in on your IT savvy? Send your tip to tips@itworld.com. If we post it, we'll send you a $25 Amazon e-gift card.







great developer!
great developer!I'm not sure about BSD, but
I'm not sure about BSD, but what is it they say about Windows? For every bug fixed two more are created. So it would not really matter if a bug takes 33 years to fix.Fixing a bug with origins
Fixing a bug with origins that old is very cool. But this is not a UNIX bug, it is a bug in yacc. Calling it a UNIX bug is misleading and factually incorrect. There are many (most?) UNIX systems that don't ever run yacc. And most modern versions, or even LINUX distributions, don't install it by default anymore.