Finally, a decent HIDS for Win32!

OSSEC has finally been aqcuired by a software-company with enough resources to boost development towards a windows-client as well as a linux-client.

I installed the win32-client on my office workstation, and it is working like a charm. Active Responses are working, I'm getting the notifications I set-up manually and the agent-manager made administration quite easy.

So I can say I'm very pleased that Canada-based software-company ThirdBrigade aqcuisitioned OSSEC HIDS as a security product. And even more so because they promised to continue with the open-source development and distribution of it under the GPL.

http://www.ossec.net/

My job...

Yes, I will now try to explain exactly what I do for a living ;) but first, a little prologue about myself.

I first started doing paid work with computers when I volunteered for a community-job at a local youth-club where I lived at the time I'm referring to. Where I did everything from administrating websites, doing webdesign, handling the networking, webserver tweaking, email server maintenance, etc. I had this job for a full year until I got sick of it. Being an operator isn't as glamourus as it may/may not seem.

Then I worked 6 months for a major Scandinavian ISP company as a service desk consultant; answering troubleshooting questions, logging faults, reading for the CCNA exam (which I never finished, due to lack of interest), and a lot of other cool stuff that heightened my professional skill levels.

Now, I do what I set out to be doing, when I was still in Junior High, I make: web designs, web templates, web applications (php & asp), administer Microsoft Servers (not my kind of bag, but I gotta make a livin').

What this means in 'g33k':
I work with programs that provide interoperability in support of the move to coherent distributed architectures.

What this means in somewhat plain (computer-)English:
I work with programs that make business-trading more efficient by supporting enterprise application integration, which simplifies the exchange of information between enterprise software for the buyer, and the supplier. This is achieved by relying on non-architecture specific languages and tools (webservers, databases, AJAX,ASP) for cross-interoperability.

I never imagined I would end up doing programming and scripting for a living, in fact, it was the last choice I would have taken a few years ago... It's even the reason I dropped out of uni'. But here I am, and that's what I'm doing...and I'm loving it! ;D

DEC terminals

I was just sitting, surfing and playing around. Reading about computer equipment from the 70's and 80's. When I suddenly came across this DEC terminal, that has _the_ most unusual model name I have ever heard/seen... ;D

Ladies and gentlemen! The 1990 "DEC VT420" computer terminal! ;P

Jargon

The _original_ hacker's dictionary!
With tons of interesting definitions and puns ;)

http://www.dourish.com/goodies/jargon.html

OSS participation!

A 30-page ebook on how to participate in the Open Source community; whom to talk to, where to go for info, etc. =) A recent addition to open source development, following the beta release of the brilliant testing program 'AppChecker'.

http://ldn.linuxfoundation.org/

Application checker

AppCheck is a testing-application for programs made for linux to check for cross-system portability. AppCheck tests the ELFs, scripts, libraries and more. As a testing framework, it doesn't seem to differentiate itself much from the forerunner of all checking programs: lint. The first program to flag suspicious and non-portable contructs, first appeared in System V Unix version 7 (outside of Bell Labs) in 1979.

But it's what AppCheck does after these checks that makes it stand out. It checks all the components of the program against the Linux Standard Base, AND different distributions listed in the LSB Database. It then displays all of this information on a webpage to make the report more intuitive and structured, and even gives you the opportunity to submit the program directly from the test-program for LSB certification!

After reading about this wonderful piece of software, I was inspired to do more C/C++ programming in my spare time, since AppCheck will spare me a lot of time when it comes to testing.

AppCheck is in no way a perfect checker, it's still in beta, and it cannot check libraries, binaries, and other components that aren't listed in the LSB. But it is a significant step forward for portability development.

** Note however that AppCheck is in no way a debugger **

http://www.linux.com/feature/144170

BSOD x 10

Seriously, someone should have learned by now that you can only trust Microsoft products to a certain degree when it comes to complex production environments. The computer running the lightshow in the picture above for the opening of the Beijing Olympics 2008? Well, it didn't perform quite as it should.., and then displaying a gigantic BSOD (Blue screen of death), when it wasn't even running Vista! IT WAS RUNNING XP!

Computer manufacturer Lenovo was responsible for the Olympic computers, and insisted they run Windows XP instead of Vista, which they considered to be untrustable and unstable. Yeah, like XP was the better choice, huh?

http://blogs.computerworld.com/

http://www.smh.com.au/

OpenSSH

OpenSSH er en derivat av den originale "free ssh 1.2.12" utgivelsen fra Tatu Ylönen. Denne versjonen var den siste som var "fri" nok for gjenbruk i OpenSSH-prosjektet. Deler av OpenSSH bærer fremdeles Tatus lisens som var inkludert i hans egen utgivelse. Denne versjonen, og alle tidligere, brukte matematiske funksjoner fra "libgmp" biblioteket. Biblioteket var også inkludert med disse tidlige ssh versjonene. Libgmp er gjort tilgjengelig under (LGPL) Lesser GNU Public License, selv om versjoner av lisensen på denne tiden lignet mer på standard (GPL) GNU Public License.

En kombinert lisens for alle delene er tilgjengelig på http://www.openbsd.org/cgi-bin/cvsweb/src/usr.bin/ssh/LICENCE.

Snart etter 1.2.12 utgivelsen fra Tatu, ville nyere utgivelser by på mer restriktive lisenser, selv om libgmp fremdeles var inkludert og nødvendig for å bruke programvaren. Tidligere restriktive lisenser nektet folk å lage en Windows eller DOS versjon. Senere lisenser avgrenset bruken av ssh i kommersielle miljøer, hvor de i stedet krevde at firmaer kjøpte en dyr versjon fra Datafellows.

Tidlig i 1999, gjenoppdaget Björn Grönvall denne bestemte utgivelsen og startet å fikse bugs. Hans versjon av ssh er kalt OSSH og hadde bare støtte for SSH 1.3 protokollen. Rykter sier at OSSH har blitt integrert i noen kommersielle produkter i Sverige. Og til og med den dag i dag, har ikke OSSH støtte for SSH 2 protokollen.

OpenBSD prosjekt medlemmer ble klar over Björns arbeid mindre enn 2 måneder før utgivelsen av OpenBSD 2.6 release. De ville inkludere støtte for ssh protokollen i 2.6 utgivelsen av OpenBSD, men de måtte bli sikre på at den var perfekt. Derfor bestemte de seg for å 'forke' fra OSSH utgivelsen, og strebe etter rask utvikling på samme måte som den originale sikkerhetsrevisjonsprosessen ble utført internt i OpenBSD prosjektet. Som et resultat, var mye av kildekoden i utgivelses-filene allerede på RCS revision 1.34, noen helt oppe i 1.66. Utvikling gikk veldig raskt siden de hadde en deadline å komme i møte.

Memory IS RAM!

Moss on Firewalls

Anti-Piracy?

Think Free