FyreWyr writes "L0phtCrack — now 12 years old — used to be a security 'tool of choice' for black hats, pen-testers, and security auditors alike — that is, until it was sold by L0pht to @stake, then Symantec, to be released and subsequently dropped as LC 5. As an IT security consultant, I used this tool to regularly expose vulnerabilities or recover data when there were few other options available. Eventually, I let it go as tech evolved away. Now, after being returned to its original developers, version 6 was released this week with fresh features: support for 64-bit multiprocessors, (current) Unix and Windows operating systems, and a number of other features, including enhanced handling of NTLM password hashes and support for rainbow tables. Interested parties, especially consultants, will find this shiny new version sports a hefty price tag. It raises doubts in my mind whether it can effectively compete with open source alternatives that go by similar names, but as I found earlier versions so useful, its re-emergence seems worth the mention."

An anonymous reader writes "Local newspaper talks to Linux International's Jon 'maddog' Hall, who lives in New Hampshire, and who since 1989 has had a 'Live Free or Die' UNIX license plate — a real one, not a conference hand-out — on his Jeep. From the story: 'The day he installed the UNIX plates, he went early to work at DEC's office on Spit Brook Road in Nashua, to be sure to get the parking space right next to the door used by all the Unix engineers. He watched them come in and, one after another, do a double take at seeing the real-world version of the famous fake plate. "People would race in and yell, 'Who is it? Whose plate is it?!?'" Hall said. It was his then and it is his now. After 20 years, one suspects you will have to pry it from his cold, dead fingers.'"

blacklily8 writes "Gamasutra has published "The History of Rogue: Have @ You, You Deadly Zs." Despite only the most 'primitive' audiovisuals, Rogue has continued to excite gamers and programmers worldwide, and has been ported, enhanced, and forked now for over two decades. What is it about Wichman and Toy's old UNIX RPG that has sent so many gamers to their deaths in the Dungeons of Doom, desperately seeking the fabled Amulet of Yendor? This article covers the history of the game, including the Epyx failure to make a ton of cash selling it in 1983. It also goes into rogue-like culture and development."

portscan writes "OpenBSD 4.5 has been released. New and extended platforms include sparc64, and added device drivers. OpenSSH 5.2 is included, plus a number of tweaks, bugfixes, and enhancements. See the announcement page for a full list. OpenBSD is a security-oriented UNIX/BSD operating system." As per OpenBSD tradition, of course there's a song.

narramissic writes "A Dutch university has received a $3.3 million grant from the European Research Council to fund 5 more years of work on a Unix-type operating system, called Minix, that aims to be more reliable and secure than either Linux or Windows. The latest grant will enable the three researchers and two programmers on the project to further their research into a making Minix capable of fixing itself when a bug is detected, said Andrew S. Tanenbaum, a computer science professor at Vrije Universiteit. 'It irritates me to no end when software doesn't work,' Tanenbaum said. 'Having to reboot your computer is just a pain. The question is, can you make a system that actually works very well?'"

Michael J. Ross writes "Two decades ago, Web usage was limited to a single individual (Sir Tim Berners-Lee) using the only browser in existence (WorldWideWeb) running on a single platform (a NeXT Computer). Nowadays, billions of people access the Web daily, with the ability to choose from over a dozen browsers running on desktop computers, laptops, and a variety of mobile devices, such as cell phones. The number of possible combinations is growing rapidly, and makes it increasingly difficult for Web designers and developers to craft their sites so as to be universally accessible. This is particularly true when accounting for Web users with physical and cognitive disabilities — especially if they do not have access to assistive technologies. The challenges and solutions for anyone creating an accessible website are addressed in Universal Design for Web Applications, authored by Wendy Chisholm and Matt May." Keep reading for the rest of Michael and Laura's review.

Microsoft's supposed open-source guru Sam Ramji has asked open-source vendors to focus on "value" instead of "cost" with respect to competition with Microsoft products. This is especially funny given the Redmond giant's recent "Apple Tax" message. "While I'm sure Ramji meant well, I'm equally certain that Microsoft would like nothing more than to not be reminded of how expensive its products can be compared with open-source solutions. After all, Microsoft was the company that turned the software industry on its head by introducing lower-cost solutions years ago to undermine the Unix businesses of IBM and Hewlett-Packard, and the database businesses of Oracle and IBM."

Death Metal writes "PC-BSD 7.1 is built upon the FreeBSD 7.1-STABLE operating system. FreeBSD is a UNIX-based operating system that provides a high level of security and stability. The Galileo Edition of PC-BSD includes updated versions of KDE (4.2.2) and Xorg (7.4). The latest version of KDE includes new window effects, screen savers, and better 3D Acceleration. PC-BSD exclusively features the Push Button Installer, a software installation wizard with a wide range of applications. The latest version improves PBI self-containment to increase reliability. The Add / Remove Programs tool and the Update Manager have been consolidated into 'Software & Updates.'"

suraj.sun points to a story in the New York Times indicating that the much-rumored merger (or purchase) that would have united Sun with IBM may have dissolved before it began. Excerpting: "I.B.M., after months of negotiations, withdrew its $7 billion bid for Sun Microsystems on Sunday, one day after Sun's board balked at a slightly reduced offer, according to a person close to the talks. The deal's collapse raises questions about Sun's next step, since the I.B.M. offer was far above the value of the Silicon Valley company's shares when news of the I.B.M. offer first surfaced last month. .. Since last year, Sun executives had been meeting with potential buyers. I.B.M. stepped up, seeing an opportunity to add to its large software business, acquire valuable researchers and consolidate the market for larger, so-called server computers that corporations use in their data centers. ... Now, Sun is free to pursue other suitors, including I.B.M. rivals like Hewlett-Packard and Cisco Systems. Cisco recently entered the market for server computers."

plasticsquirrel was one of several readers to send in the sharpening rumors that IBM is on the verge of acquiring Sun Microsystems, as we discussed last week. The pricetag is reportedly $7 billion. According to the NYTimes's sources, "People familiar with the negotiations say a final agreement could be announced Friday, although it is more likely to be made public next week. IBM's board has already approved the deal, they said." After the demise of SGI, one has to wonder about the future of traditional Unix. If the deal goes through, only IBM, HP, and Fujitsu will be left as major competitors in the market for commercial Unix. And reader UnanimousCoward adds, "Sun only came into the consciousness of the unwashed masses with the company not being able to get E10K's out the door fast enough in the first bubble. We here will remember some pizza-box looking thing, establishing 32 MB of RAM as a standard, and when those masses were scratching their heads at slogans like 'The Network is the Computer.' Add your favorite Sun anecdote here."

Shlomi Fish writes "O'Reilly is publishing a new book titled 'Mastering cat,' about the UNIX 'cat' command. Here is an interview O'Reilly-Net conducted with the author about it. Read it to see if this book should be part of your bookshelf of technical books."

CWmike writes "As the tech community gears up to celebrate Unix's 40th birthday this summer, one thing is clear: People do love operating systems. They rely on them, get exasperated by them and live with their little foibles. So now that we're more than 30 years into the era of the personal computer, Computerworld writers and editors, like all technology aficionados, find ourselves with lots of memories and reactions to the OSes of yesteryear (pics galore). We have said goodbye to some of them with regret. (So long, AmigaOS!) Some of them we tossed carelessly aside. (Adios, Windows Me!) Some, we threw out with great force. (Don't let the door hit you on the way out, MS-DOS 4.0!) Today we honor a handful of the most memorable operating systems and interfaces that have graced our desktops over the years. Plus: We take a look back at 40 years since Unix was introduced."

SkiifGeek writes "With Adobe's patch for the JBIG2Decode vulnerability due in a few days time, new methods to target the vulnerability have been discovered that make it far riskier than previously thought. Didier Stevens recently showed the world how it is possible to exploit the vulnerability without the user actually opening an affected file, and now he has discovered a way that allows for completely automated exploitation that results in anything up to a Local System account without any user interaction at all and only relies upon basic Windows components and Acrobat Reader elements. There are some mitigating factors that limit the overall risk of this new discovery, but it does also highlight that merely uninstalling the Reader will not protect you from exploitation and does raise the possibility that other tools will access the vulnerable components and thus be vectors for attack." However, the fix is now in: nk497 writes "Adobe had finally released a fix for a PDF vulnerability discovered — and already exploited — last month. The update only applies to the most recent versions of Reader and Acrobat, with early versions and Unix editions not fixed until later this month. Adobe has taken its time with the patch, despite an independent security researcher releasing her own fix just days after the flaw was announced."

An anonymous reader writes "Steve Bourne, the creator of the Bourne shell, or sh, talks about its history as the default Unix shell of Unix Version 7. Bourne worked on the shell in 1975 and said the process took no more than 6 months. Sh aimed to improve on the Thompson shell. 'I did change the shell so that command scripts could be used as filters. In the original shell this was not really feasible because the standard input for the executing script was the script itself. This change caused quite a disruption to the way people were used to working. I added variables, control flow and command substitution. The case statement allowed strings to be easily matched so that commands could decode their arguments and make decisions based on that. The for loop allowed iteration over a set of strings that were either explicit or by default the arguments that the command was given. I also added an additional quoting mechanism so that you could do variable substitutions within quotes. It was a significant redesign with some of the original flavor of the Thompson shell still there. Also I eliminated goto in favour of flow control primitives like if and for. This was also considered rather radical departure from the existing practice. Command substitution was something else I added because that gives you very general mechanism to do string processing; it allows you to get strings back from commands and use them as the text of the script as if you had typed it directly. I think this was a new idea that I, at least, had not seen in scripting languages, except perhaps LISP,' he says."

chthonicdaemon writes "I have been using Linux as my primary environment for more than ten years. In this time, I have absorbed all the lore surrounding the Unix Way — small programs doing one thing well, communicating via text and all that. I have found the command line a productive environment for doing many of the things I often do, and I find myself writing lots of small scripts that do one thing, then piping them together to do other things. While I was spending the time learning grep, sed, awk, python and many other more esoteric languages, the world moved on to application-based programming, where the paradigm seems to be to add features to one program written in one language. I have traditionally associated this with Windows or MacOS, but it is happening with Linux as well. Environments have little or no support for multi-language projects — you choose a language, open a project and get it done. Recent trends in more targeted build environments like cmake or ant are understandably focusing on automatic dependency generation and cross-platform support, unfortunately making it more difficult to grow a custom build process for a multi-language project organically. All this is a bit painful for me, as I know how much is gained by using a targeted language for a particular problem. Now the question: Should I suck it up and learn to do all my programming in C++/Java/(insert other well-supported, popular language here) and unlearn ten years of philosophy, or is there hope for the multi-language development process?"

os2man was one of many readers to let us know that later on today, at 23:31:30 UTC (30 seconds after this story went live), the number of seconds since January 1st 1970 will be exactly 1234567890. January 1st, 1970 marks the start of the clock for the Unix operating system and many other operating systems. Here is a list of celebrations of the moment around the world.

Joe MacDonald writes "The earliest UNIX shell I encountered was the Bourne shell on a SPARCStation 2 at my university. As with many students of my generation, prior to that nearly all of my exposure to command line interfaces was some variant of DOS. I was quite proficient with the primitive scripting language that was available on such platforms but I immediately felt far out of my depth in this new environment. The commands seemed arcane, possibly dangerous, and almost immediately I regretted stepping into this unfamiliar wilderness without some sort of guide." Read below for the rest of Joe's thoughts.

Dark Neuron writes "My institution has thousands of computers, and is looking at starting an IT policy to encrypt everything, all hard drives, including desktops, laptops, external hard drives, USB flash drives, etc. I am looking at an open source product for Windows, Mac, UNIX, as well as portable hard drives, but I am concerned about overhead and speed penalties. Does anyone have experience and/or advice with encrypting every single device in a similar situation?"

mikesd81 writes "Over at Linux Magazine Online, Jon maddog Hall writes that on Friday the 13th, 2009 at 11:31:30pm UTC UNIX time will reach 1,234,567,890. This will be Friday, February 13th at 1831 and 30 seconds EST. Matias Palomec has a perl script you an use to see what time that will be for you: perl -e 'print scalar localtime(1234567890),"\n";' Now, while this is not the UNIX epoch, Alan Cox does assure us that Linux is now working on 64-bit time, and the UNIX epoch 'roll-over' would happen about the time that the sun burnt out."

David Gerard writes "Wine (the Windows not-an-emulator for Unix) runs Windows applications more often than not. (Certainly more often than Vista does.) Dan Kegel on the wine-users mailing list/forum has started gathering apps that declare Wine a supported platform. And there's now a Wine Support Honor Roll page on the Wine wiki. We need more apps that work with Wine stating that they consider it a supported platform. If you write Win32 open source or shareware, please open yourself to the wider market!"