Contributed by jose on from the BSD-land-security dept.
a friend of mine, who gives a seminar about Information Ethics at the university of our city, asked me some time ago if i could do a short talk about OpenBSD. While if have some years of experience in Linux, my knowledge of OpenBSD is limited to the installation of a router and readings at deadly.org. Plain information-seeking didn't produce very usable results for me. Therefore I would be grateful if someone here could tell me about similar talks or documents, which adress ethical issues in conjuction with OpenBSD. According to my plans, the main point in this talk will be the right in personal privacy and the effort of the OpenBSD-Project to keep a system secure, which is in this case synonymous with securing privacy.
Thanks in advance
Markus"
In some ways the answer to this is pretty simple, but it's potentially an interesting answer. Any thoughts?
(Comments are closed)
By Peter Hessler () spambox@theapt.org on http://www.theapt.org
Or more accurately: theoretically, what ethical issues can there be with OpenBSD?
Comments
By Michael () on
The subject is information ethics relating to privacy. The goals of the OpenBSD project is correctness/security and thus privacy.
The 'ethics' is the focus of the seminar, OBSD is an example of a project that strives to give you personal privacy.
--michael
By Anonymous Coward () on
By Sloppy () on
Hope this helps.
Comments
By Anonymous Coward () on
By Jordi () on
OpenBSD do provide mechanisms to secure IS, which can be illegal in some countries / states / organizations (Minnesota comes to mind) This is clearly illegal, but ethical.
Anyway, maybe some information about GNU versus BSD will be also educative to the audience.
Comments
By Alejandro G. Belluscio () baldusi_NOTWORKING@hotmail.com on mailto:baldusi_NOTWORKING@hotmail.com
Comments
By Matthew Weigel () on
By dlg () dlg+obsdj@dorkzilla.org on mailto:dlg+obsdj@dorkzilla.org
what?! i have openbsd machines in MN .... you're kidding, right?
Comments
By James Nobis () on
Comments
By Justin () on
By Anthony () on
If by "educate" you mean "start a holy war on slashdot", then yes...
By Paul Pruett () ppruett@webengr.com on http://www.cocoavillagepublishing.com/
But an important point to stress is that the developers of OpenBSD have made a strenous effort to adhere to licenses, which IMHO is very ethical.
(and a pain - but worth it)
Msny examples can be found were OpenBSD developers removed ot changed software because the license could not be verified to meet their polices about copyrights. And because of the adherence to having clean licenses, good and better things have resulted, in a strange way good deeds benefit in the long run. A famous example was the squable by the author of the ipf method of filtering and the developers. The developers rewrote a lot of code and put in a lot of support behind pf for packet filtering because that way they could stand on their policy.
And quite a few other applications may not in base because of the license, ask the community for examples if need...
Sure, many is the time, some people say, don't worry about the fuzzy unclear nature of the license, use it any ways. THAT is unethical!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
If you have not already, you should reference the policy page:
http://www.openbsd.org/policy.html
By Dom De Vitto () dom@devitto.com on mailto:dom@devitto.com
b) licensing, what is "open" and "free", BSD/GNU etc.
c), most importantly disclosure issues, if you find a bug that could, maybe, possibly allow remote root, should you make a big sing and dance? or if it's obvious? what about likely? what about if it's actually being exploited?
The latter is REALLY interesting compared to companies like MS, who deny everything and only release bulletins prior to expected exploitation, and Cisco who notify (some) people early - even when only workarounds (no fix) is available!
By SH () on
To make a not quite so contrived example: In OpenBSD (as other *nixes) it's very easy to do extensive monitoring of network traffic, which might be legal but
By Anonymous Coward () on
By Anonymous Coward () on
which boils down to something like: just because we accept funding does not mean we will refrain from voicing our opinions. that is not a very widespread attitude.
By Robert Folkerts () RobertFolkerts@mchsi.com on mailto:RobertFolkerts@mchsi.com
1) Is your privacy worth protecting? If yes, you should support allowing others to have tools that protect thier privacy.
2) Do you want to be able to track down the source of your errors? If so, you should work to have good documentation in your OS. You should also strive to shut down as many defects as you can.
3) Do you want a secure operating system more than you want new features? If so, you should develop a secure OS.
4) Do you want to use other people's software freely, while respecting their authorship? If so, you should use a BSD-style license.
In all of these areas, I find the OpenBSD team to be exibiting the highest ethical standards. I, by comparison, am relatively selfish, most of my coding is for pay. This isn't wrong, but it isn't noble either. There is real nobility in the selflessness of OSS developers.
Does this make sense to others?
By Anonymous Ninja () on
Why did you arrange to speak at a seminar about a subject you clearly did not have sufficient knowledge in?
Comments
By Markus () on
I won't try to do a talk about OpenBSD, because I admittedly don't know as much that I could reasonably argue. That's why this one is rather about privacy and data security, which is a thing I'm into.
But it is not too hard to see that the onset of OpenBSD is clearly different from other systems in terms of security and the underlying philosophy. Machines are the most frequently involved thing when it comes to violations of data. For this reason I deemed it not an insulting idea to ask for some hints.