Linked by Thom Holwerda on Mon 10th May 2010 10:03 UTC, submitted by robertson
Permalink for comment 423988
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
More News »
Sponsored Links



Member since:
2005-06-29
It's my understanding that they are going for full BeOS R5 compatibility with this first release. R5 came about during Windows 98's heyday; at that time, security on home computers was not a big issue. Given that it was such an obscure OS, there were no viruses for it, few exploits, and overall no real need for security beyond the basics. It was a perfect example of security by obscurity. Granted, there were inherent security features from being partially POSIX compliant, but that left a lot of room for improvement.
Let me be clear: I don't agree with BeOS R5's lack of security, and I hope the Haiku team has some great ideas for future security measures. I'd love to see a password barrier before the desktop loads, at the very least. Even though it's meant to be a single-user system, there exists the ability to add user accounts and set permissions.
As it is an open source project, why not build on this foundation and help them to achieve a security concept?