Frequently Asked Questions

Why SecBSD?

No telemetry, no tracking, no mic recording sound, no webcam access by default. Security in our days is a necessity and privacy a right that we are not willing to lose. We are living in a world that evolves constantly and meet new challenges. We need a secure and stable operating system for all.

What is SecBSD goal?

SecBSD wants create an open source community to develop an operating system that is free, secure with focus on privacy, stable and functional for hackers, security researchers, bug hunters, pentesters, hacktivists and cybersecurity folks.

we want our toolkit to be the best both on the offensive and defensive aspects.

How do I contribute to SecBSD?

We are looking for developers, C programmers, Unix architects, OS designers and people interested to create a great project and hacker community.

Why OpenBSD?

We have been OpenBSD users for a long time, is our preferred platform with the relentless focus on security, shipping with sane defaults, proper documentation and a thorough and constant auditing process. From our perspective OpenBSD is the best quality code known and that fits with our project goals.

Why release SecBSD?

This is the last time I will be on this planet. It is my contribution to others hackers.

Who design the SecBSD Website and all stuff?

Banshee.

How SecBSD is built?

I made it out of a Lenovo X200 (died). For some ports I used a HP Elitebook 820 (died).

Supported architectures?

SecBSD runs on AMD's Athlon-64 family of processors in 64-bit mode. It also runs on processors made by other manufacturers which have cloned the AMD64 extensions. More info.

Why haven't you compiled and hosting all packages?

We don't have space on our server.
My overheating laptop is not enough to compile the whole source tree during several days.

How can I trust SecBSD?

Because a vanilla OpenBSD forms the foundation, you can apply syspatch or do release upgrades via sysupgrade just like with any other OpenBSD system.
Our packages are verificable by inspecting them.
Binary packages are to be signed by the project itself alongside with multiple core members.
Releases are signed by the project itself alongside with multiple core members.

During the installation of SecBSD, the sets and packages are verified with checksums and GPG signatures.
Furthermore, despite the effort our team goes through, there is always a certain degree of trust involved. Aside from the operating system, modern processors have a complete subsystem (Intel ME and AMD TrustZone) which are as proprietary and closed as it gets. Furthermore, the UEFI system, component firmware - you probably get the idea. Despire the groundbreaking research by parties like Invisible Things Lab, innovations like Coreboot, there still is a long way to go. Though, as of now, this falls outside the scope of SecBSD. We might revise this in the future.

How can I donate to SecBSD?

We don't take donations. SecBSD is a starting project, building forth and depending upon the awesome work of the OpenBSD project. This, we kindly ask you to donate to the OpenBSD Foundation instead. That is - indirectly - also a donation to SecBSD but goes a much longer way.

How can I contact SecBSD?

Through email:
Purple Rain or h3artbl33d.