SecBSD's current website code
101
amd64.html
Normal file
@ -0,0 +1,101 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD amd64</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD amd64">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box">
|
||||
<div class="title green">SECBSD</div>
|
||||
<div class="subtitle">AMD64</div>
|
||||
<div class="txt">
|
||||
<span>█</span> Supported architecture
|
||||
<div>
|
||||
<p class="purple">SecBSD/amd64 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.
|
||||
</p>
|
||||
<p>X Window System support is available for most
|
||||
graphics cards, using the X.Org server. As with other free
|
||||
operating systems it is highly recommended that Nvidia cards
|
||||
are avoided since this vendor continues to show tremendous
|
||||
resistance towards releasing information that would allow X.Org
|
||||
to support their hardware properly.
|
||||
</p>
|
||||
<h3>Current status:</h3>
|
||||
The only major shortcoming at this time is that the kernel
|
||||
debugger <a href="https://man.openbsd.org/amd64/ddb.4">ddb</a>
|
||||
is somewhat poor.
|
||||
<h2>Supported hardware:</h2>
|
||||
<h2>Processors</h2>
|
||||
<p>
|
||||
All versions of the AMD Athlon 64 processors and their clones
|
||||
are supported.
|
||||
<h2>Graphics Support</h2>
|
||||
<p class="green">
|
||||
Basic graphics support should support most hardware, but some
|
||||
features like video or 3D acceleration require additional
|
||||
driver support. Unsupported devices will typically still work
|
||||
in VESA or EFIFB mode.
|
||||
</p>
|
||||
<p class="purple">
|
||||
AMD devices use a confusing mix of code names and rebadging.
|
||||
Some devices expected to work:
|
||||
<ul class="list">
|
||||
<li>Products using "Northern Islands," "Southern Islands,"
|
||||
or "Sea Islands" graphics cores.
|
||||
<li>AMD Radeon 5000 series
|
||||
<li>Earlier AMD and ATI models are expected to work as well.
|
||||
</ul>
|
||||
<p class="purple2">
|
||||
Intel devices can be confusing as well. Some devices expected
|
||||
to work:
|
||||
<ul class="list">
|
||||
<li>Intel Kaby Lake (found on i-7xxx CPU)
|
||||
<li>Intel Skylake (found on i-6xxx CPU)
|
||||
<li>Intel Broadwell (found on i-5xxx CPU)
|
||||
<li>Intel Broxton/Apollo Lake
|
||||
<li>Intel Amber Lake
|
||||
<li>Intel Gemini Lake
|
||||
<li>Intel Coffee Lake
|
||||
<li>Intel Whiskey Lake
|
||||
<li>Earlier Intel models and revisions are expected to work
|
||||
as well.
|
||||
<li>The PowerVR graphics found on some Atom CPUs are not
|
||||
supported.
|
||||
</ul>
|
||||
<h3>Unsupported Hardware:</h3>
|
||||
<p class="purple">
|
||||
New hardware is constantly being released, some of which may
|
||||
lack support.
|
||||
Your <a href="sponsors.html">donation</a>,
|
||||
<a href="hardware.html"> hardware</a>, or
|
||||
<a href="docs.html">documentation</a> can accelerate
|
||||
this support!
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
210
ddb.html
Normal file
@ -0,0 +1,210 @@
|
||||
|
||||
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD: Crash Reports</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="How to report an SecBSD kernel crash">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box">
|
||||
<b>█</b>
|
||||
<b>SecBSD: Crash Reports</b><br><br>
|
||||
<b class="purple">Minimum information for kernel problems</b>
|
||||
<p>Familiarize yourself with <a href="report.html">the general bug
|
||||
reporting procedures</a> first.
|
||||
All of that will apply.
|
||||
When reporting a kernel panic or crash, please remember:
|
||||
</p>
|
||||
<ul>
|
||||
<li>We need the console output on the screen.
|
||||
Capture it and save it.
|
||||
Serial consoles are best, but if you are on a VGA console you can
|
||||
<a href="https://www.openbsd.org/faq/faq7.html">scroll the console back</a>
|
||||
and take readable pictures with a phone or camera.
|
||||
<li>If the kernel panicked we need the traceback.
|
||||
It may be displayed on the screen.
|
||||
If you are at a
|
||||
<a href="https://man.openbsd.org/ddb.4">ddb</a>>
|
||||
prompt, type <kbd>trace</kbd>.
|
||||
If you are running SMP, use the <kbd>mach ddbcpu N</kbd> command for each
|
||||
of the <var>N</var> processors you have and repeat the <kbd>trace</kbd>
|
||||
command for each processor.
|
||||
<li>We need the process list.
|
||||
Use the command <kbd>ps</kbd> to get that.
|
||||
</ul>
|
||||
<p>
|
||||
Reports without the above information are useless.
|
||||
This is the minimum we need to be able to track down the issue.
|
||||
</p>
|
||||
<b class="purple">Additional information you can send</b>
|
||||
<p>
|
||||
In some situations more information is desirable.
|
||||
Below are outlined some additional steps you can take in certain situations:
|
||||
<ul>
|
||||
<li>
|
||||
If your crash appears to involve filesystems.
|
||||
The following additional things would be helpful
|
||||
<ul>
|
||||
<li>The output of the
|
||||
<a href="https://man.openbsd.org/ddb.4">ddb</a>> command
|
||||
<kbd>show uvm</kbd>
|
||||
<li>The output of the
|
||||
<a href="https://man.openbsd.org/ddb.4">ddb</a>>
|
||||
command <kbd>show bcstats</kbd>
|
||||
<li>The output of the <kbd>mount</kbd> command from your running machine, so
|
||||
we know what filesystems are mounted and how.
|
||||
</ul>
|
||||
<li> ... XXX boot crash? XXX
|
||||
<li> ... XXX show regs? XXX
|
||||
</ul>
|
||||
<b>Lost the panic message?</b>
|
||||
<p>
|
||||
Under some circumstances, you may lose the very first message of a panic,
|
||||
stating the reason for the panic.
|
||||
</p>
|
||||
<pre class="cmdbox">
|
||||
ddb> <b>show panic</b>
|
||||
0: kernel: page fault trap, code=0
|
||||
ddb>
|
||||
</pre>
|
||||
<b>Note for SMP systems</b>
|
||||
<p>
|
||||
You should get a trace from each processor as part of your report:
|
||||
</p>
|
||||
<pre class="cmdbox">
|
||||
ddb{0}> <b>trace</b>
|
||||
pool_get(d05e7c20,0,dab19ef8,d0169414,80) at pool_get+0x226
|
||||
fxp_add_rfabuf(d0a62000,d3c12b00,dab19f10,dab19f10) at fxp_add_rfabuf+0xa5
|
||||
fxp_intr(d0a62000) at fxp_intr+0x1e7
|
||||
Xintr_ioapic0() at Xintr_ioapic0+0x6d
|
||||
--- interrupt ---
|
||||
idle_loop+0x21:
|
||||
ddb{0}> <b>machine ddbcpu 1</b>
|
||||
Stopped at Debugger+0x4: leave
|
||||
ddb{1}> <b>trace</b>
|
||||
Debugger(d0319e28,d05ff5a0,dab1bee8,d031cc6e,d0a61800) at Debugger+0x4
|
||||
i386_ipi_db(d0a61800,d05ff5a0,dab1bef8,d01eb997) at i386_ipi_db+0xb
|
||||
i386_ipi_handler(b0,d05f0058,dab10010,d01d0010,dab10010) at i386_ipi_handler+0x
|
||||
4a
|
||||
Xintripi() at Xintripi+0x47
|
||||
--- interrupt ---
|
||||
i386_softintlock(0,58,dab10010,dab10010,d01e0010) at i386_softintlock+0x37
|
||||
Xintrltimer() at Xintrltimer+0x47
|
||||
--- interrupt ---
|
||||
idle_loop+0x21:
|
||||
ddb{1}>
|
||||
</pre>
|
||||
<p>
|
||||
Repeat the <code>machine ddbcpu x</code> followed by <code>trace</code> for each
|
||||
processor in your machine.
|
||||
</p>
|
||||
<b>How do I gather further information from a kernel crash?</b>
|
||||
<p>
|
||||
A typical kernel crash on SecBSD might look like this:
|
||||
<pre class="cmdbox">
|
||||
kernel: page fault trap, code=0
|
||||
Stopped at <b>pf_route+0x263</b>: mov 0x40(%edi),%edx
|
||||
ddb>
|
||||
</pre>
|
||||
<p>
|
||||
This crash happened at offset <code>0x263</code> in the function <code>pf_route</code>.
|
||||
</p>
|
||||
<p>
|
||||
The first command to run from the
|
||||
<a href="https://man.openbsd.org/ddb">ddb(4)</a> prompt is <code>trace</code>:
|
||||
<pre class="cmdbox">
|
||||
ddb> <b>trace</b>
|
||||
<b>pf_route</b>(e28cb7e4,e28bc978,2,1fad,d0b8b120) at <b>pf_route+0x263</b>
|
||||
pf_test(2,1f4ad,e28cb7e4,b4c1) at pf_test+0x706
|
||||
pf_route(e28cbb00,e28bc978,2,d0a65440,d0b8b120) at pf_route+0x207
|
||||
pf_test(2,d0a65440,e28cbb00,d023c282) at pf_test+0x706
|
||||
ip_output(d0b6a200,0,0,0,0) at ip_output+0xb67
|
||||
icmp_send(d0b6a200,0,1,a012) at icmp_send+0x57
|
||||
icmp_reflect(d0b6a200,0,1,0,3) at icmp_reflect+0x26b
|
||||
icmp_input(d0b6a200,14,0,0,d0b6a200) at icmp_input+0x42c
|
||||
ipv4_input(d0b6a200,e289f140,d0a489e0,e289f140) at ipv4_input+0x6eb
|
||||
ipintr(10,10,e289f140,e289f140,e28cbd38) at ipintr+0x8d
|
||||
Bad frame pointer: 0xe28cbcac
|
||||
ddb>
|
||||
</pre>
|
||||
<p>
|
||||
This tells us what function calls lead to the crash.
|
||||
</p>
|
||||
<p>
|
||||
To find out the particular line of C code that caused the crash, you can
|
||||
do the following:
|
||||
</p>
|
||||
<p>
|
||||
Find the source file where the crashing function is defined.
|
||||
In this example, that would be <code>pf_route()</code> in <code>/sys/net/pf.c</code>.
|
||||
Use <a href="https://man.openbsd.org/objdump">objdump(1)</a> to get the
|
||||
disassembly:
|
||||
<pre class="cmdbox">
|
||||
$ <b>cd /sys/arch/$(uname -m)/compile/GENERIC</b>
|
||||
$ <b>objdump -dlr obj/pf.o >/tmp/pf.dis</b>
|
||||
</pre>
|
||||
<p>
|
||||
In the output, grep for the function name:
|
||||
<pre class="cmdbox">
|
||||
$ <b>grep "<pf_route>:" /tmp/pf.dis</b>
|
||||
0000<b>7d88</b> <pf_route>:
|
||||
</pre>
|
||||
<p>
|
||||
Take this first hex number <code>7d88</code> and add the offset <code>0x263</code> from
|
||||
the <code>Stopped at</code> line:
|
||||
<pre class="cmdbox">
|
||||
$ <b>printf '%x\n' $((0x7d88 + 0x263))</b>
|
||||
7feb
|
||||
</pre>
|
||||
<p>
|
||||
Scroll down to the line <code>7feb</code>.
|
||||
The assembler instruction should match the one quoted in the <code>Stopped at</code>
|
||||
line.
|
||||
Then scroll up to the nearest C line number:
|
||||
<pre class="cmdbox">
|
||||
$ <b>more /tmp/pf.dis</b>
|
||||
/sys/net/pf.c:<b>3872</b>
|
||||
7fe7: 0f b7 43 02 movzwl 0x2(%ebx),%eax
|
||||
<b>7feb</b>: 8b 57 40 <b>mov 0x40(%edi),%edx</b>
|
||||
7fee: 39 d0 cmp %edx,%eax
|
||||
7ff0: 0f 87 92 00 00 00 ja 8088 <pf_route+0x300>
|
||||
</pre>
|
||||
<p>
|
||||
So, it's precisely line <code>3872</code> of <code>pf.c</code> that crashes:
|
||||
<pre class="cmdbox">
|
||||
$ <b>nl -ba /sys/net/pf.c | sed -n 3872p</b>
|
||||
3872 if ((u_int16_t)ip->ip_len <= ifp->if_mtu) {
|
||||
</pre>
|
||||
<p>
|
||||
The kernel that produced the crash output and the object file for objdump must
|
||||
be compiled from the exact same source file, otherwise the offsets won't match.
|
||||
</p>
|
||||
<p>
|
||||
If you provide both the ddb trace output and the relevant objdump section,
|
||||
that's very helpful.
|
||||
</p>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
||||
|
153
download.html
Normal file
@ -0,0 +1,153 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>Download SecBSD & Create Bootable OS Image</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD Download">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a class="active">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box docs">
|
||||
<h3><span class="green">█</span> Download SecBSD & Create Bootable OS Image</h3>
|
||||
<p>
|
||||
Installation images .img and .iso are available on main SecBSD mirror:<br><br>
|
||||
<a href="https://mirror.secbsd.org/pub/SecBSD/snapshots/amd64/">
|
||||
https://mirror.secbsd.org/pub/SecBSD/snapshots/amd64/</a><br><br>
|
||||
|
||||
Laylo mirror, Netherlands:<br><br>
|
||||
<a href="https://mirror.laylo.nl/pub/SecBSD/snapshots/amd64/">
|
||||
https://mirror.laylo.nl/pub/SecBSD/snapshots/amd64/</a><br><br>
|
||||
|
||||
Tor Onion service by Laylo:<br><br>
|
||||
<a href="http://zqsjg25lnx7zratmne3dhbcqt5paehitom3qp2rjmwttuy7gzbzqwayd.onion/pub/SecBSD/">
|
||||
http://zqsjg25lnx7zratmne3dhbcqt5paehitom3qp2rjmwttuy7gzbzqwayd.onion/pub/SecBSD/</a><br><br>
|
||||
To install SecBSD from either an USB flash drive download install14.img<br>
|
||||
If you want to install SecBSD from either an optic medium as CD-ROM / DVD
|
||||
download install14.iso
|
||||
</p>
|
||||
<h3><span class="green">█</span> Prepare a bootable USB flash drive with SecBSD Installer</h3>
|
||||
<h3>From:</h3>
|
||||
<p>
|
||||
<ul class="list">
|
||||
<li><a href="#secbsd-openbsd">SecBSD / OpenBSD</a></li>
|
||||
<li><a href="#hardened-freebsd">HardenedBSD / FreeBSD</a></li>
|
||||
<li><a href="#netbsd">NetBSD</a></li>
|
||||
<li><a href="#mac">Mac</a></li>
|
||||
<li><a href="#windows">Windows</a></li>
|
||||
<li><a href="#gnu-linux">GNU/Linux</a></li>
|
||||
</ul>
|
||||
<h3 id="#secbsd-openbsd"><span class="green">█</span>
|
||||
SecBSD / OpenBSD
|
||||
</h3>
|
||||
<p>
|
||||
<pre class="cmdbox">
|
||||
$ cd /tmp
|
||||
$ ftp https://mirror.secbsd.org/pub/SecBSD/snapshots/secbsd-14-base.pub
|
||||
$ ftp https://mirror.secbsd.org/pub/SecBSD/snapshots/amd64/{install14.img,SHA256.sig}
|
||||
$ signify -Cp secbsd-14-base.pub -x SHA256.sig install14.img
|
||||
Signature Verified
|
||||
install14.img: OK
|
||||
</pre>
|
||||
<p class="purple">Plug in an usb flash drive.</p>
|
||||
<pre class="cmdbox">
|
||||
$ sysctl hw.disknames
|
||||
hw.disknames=sd0:xxxxxxxxxxxxxxxx,sd1:xxxxxxxxxxxxxxxx
|
||||
</pre>
|
||||
<p class="purple">Assuming the device was recognized as sd1:</p>
|
||||
<pre class="cmdbox">
|
||||
$ doas dd if=install14.img of=/dev/rsd1c bs=1m
|
||||
664+1 records in
|
||||
664+1 records out
|
||||
696745984 bytes transferred in 72.198 secs (9650464 bytes/sec)
|
||||
</pre>
|
||||
You are now ready to start installing SecBSD.<br>
|
||||
<p class="purple">
|
||||
Now boot on usb flash drive created and <a href="docs.html#install">perform a install.</a><br>
|
||||
<p class="purple">
|
||||
How to <a href="docs.html#xfce">install XFCE Desktop</a> on SecBSD.
|
||||
|
||||
<h3 id="hardened-freebsd"><span class="green">█</span>
|
||||
HardenedBSD / FreeBSD
|
||||
</h3>
|
||||
<p>
|
||||
<pre class="cmdbox">
|
||||
$ cd /tmp
|
||||
$ curl -O https://mirror.secbsd.org/pub/SecBSD/snapshots/secbsd-14-base.pub
|
||||
$ curl -O https://mirror.secbsd.org/pub/SecBSD/snapshots/amd64/{install14.img,SHA256.sig}
|
||||
$ signify -Cp secbsd-14-base.pub -x SHA256.sig install14.img
|
||||
</pre>
|
||||
<p class="purple">Plug in an usb flash drive.</p>
|
||||
<pre class="cmdbox">
|
||||
$ su
|
||||
root@hardenedbsd:~ # camcontrol devlist
|
||||
SanDisk Cruzer Blade 1.26 at scbus5 target 0 lun 0 (da0,pass1)
|
||||
</pre>
|
||||
<p class="purple">
|
||||
Assuming your usb device was recognized as da0:
|
||||
<pre class="cmdbox">
|
||||
root@hardenedbsd:~ # dd if=install14.img of=/dev/da0 bs=1M conv=sync
|
||||
665+0 records in
|
||||
665+0 records out
|
||||
697303040 bytes transferred in 83.083902 secs (8392757 bytes/sec)
|
||||
root@hardenedbsd:~ #
|
||||
</pre>
|
||||
You are now ready to start installing SecBSD.<br>
|
||||
<p class="purple">
|
||||
Now boot on usb flash drive created and <a href="docs.html#install">perform a install.</a><br>
|
||||
<p class="purple">
|
||||
How to <a href="docs.html#xfce">install XFCE Desktop</a> on SecBSD.
|
||||
|
||||
<h3 id="netbsd"><span class="green">█</span>
|
||||
NetBSD
|
||||
</h3>
|
||||
<p>
|
||||
<pre class="cmdbox">
|
||||
$ cd /tmp
|
||||
$ ftp https://mirror.secbsd.org/pub/SecBSD/snapshots/amd64/install14.img
|
||||
</pre>
|
||||
<p class="purple">Plug in an usb flash drive.</p>
|
||||
<pre class="cmdbox">
|
||||
$ su
|
||||
dd if=install14.img of=/dev/rsd0d bs=1m
|
||||
</pre>
|
||||
<p class="purple">In the previous command we have used rsd0d in order to refer to the whole sd0 disk.</p>
|
||||
You are now ready to start installing SecBSD.<br>
|
||||
|
||||
<p class="purple">
|
||||
Now boot on usb flash drive created and <a href="docs.html#install">perform a install.</a><br>
|
||||
<p class="purple">
|
||||
How to <a href="docs.html#xfce">install XFCE Desktop</a> on SecBSD.
|
||||
<h3 id="mac"><span class="green">█</span>
|
||||
Mac
|
||||
</h3>
|
||||
<p>Please create the SecBSD installation guide for Mac and send it to purplerain@secbsd.org</p>
|
||||
<h3 id="windows"><span class="green">█</span>
|
||||
Windows
|
||||
</h3>
|
||||
<p>Please create the SecBSD installation guide for Windows and send it to purplerain@secbsd.org</p>
|
||||
<h3 id="gnu-linux"><span class="green">█</span>
|
||||
GNU/Linux
|
||||
</h3>
|
||||
<p>Please create the SecBSD installation guide for GNU/Linux and send it to purplerain@secbsd.org</p>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
110
faq.html
Normal file
@ -0,0 +1,110 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD F.A.Q.</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD F.A.Q.">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html"><img src="/img/logo.png" alt="[SecBSD]"></a></h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a class="active">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box">
|
||||
<b>█</b>
|
||||
<b class="purple">Frequently Asked Questions</b>
|
||||
<br>
|
||||
<h2>What is the current state of the project?</h2>
|
||||
<p class="purple">SecBSD 1.4-f669713 is <a href="https://mirror.secbsd.org/pub/SecBSD/snapshots/amd64/">100% functional</a>.
|
||||
Detailed explanations for installation can be found in
|
||||
<a href="docs.html">Docs</a>
|
||||
</p>
|
||||
<h2>How do I contribute to SecBSD?</h2>
|
||||
<p class="purple">We are currently looking for Unix
|
||||
wizards, C, Perl, Python, Go, Rust and Ruby
|
||||
programmers.
|
||||
</p>
|
||||
<h2>How do I get the source code?</h2>
|
||||
<p class="purple">src <a href="https://code.laylo.cloud/SecBSD/src">https://code.laylo.cloud/SecBSD/src</a><br>
|
||||
<p class="purple">ports <a href="https://code.laylo.cloud/SecBSD/src">https://code.laylo.cloud/SecBSD/ports</a><br>
|
||||
<p class="purple">xenocara <a href="https://code.laylo.cloud/SecBSD/xenocara">https://code.laylo.cloud/SecBSD/xenocara</a><br>
|
||||
<p class="purple">www <a href="https://code.laylo.cloud/SecBSD/www">https://code.laylo.cloud/SecBSD/www</a><br>
|
||||
|
||||
</p>
|
||||
<h2>I want to help, but I'm not a programmer. How can I support?</h2>
|
||||
<p class="purple">This is a <a href="hardware.html">list
|
||||
of hardware</a> that could help our project.
|
||||
</p>
|
||||
<h2>How is the installation process?</h2>
|
||||
<p class="purple">Simple text mode installer, SecBSD
|
||||
installs in less than 5 minutes. Despite we not are
|
||||
desktop fans to ensure that new users of SecBSD use as a
|
||||
desktop daily driver, we added an easy desktop flavor
|
||||
installer for XFCE4, Mate, Gnome, i3, Lumina, LXQt
|
||||
and others. <a href="screenshots.html">See
|
||||
screenshots.</a>
|
||||
</p>
|
||||
<h2>Where i can download .img or .iso?</h2>
|
||||
<p class="purple">The most up-to-date file can be found at
|
||||
<a href="https://mirror.secbsd.org/pub/SecBSD">https://mirror.secbsd.org/pub/SecBSD</a>
|
||||
<a href="mirrors.html">See mirrors.</a>
|
||||
</p>
|
||||
<h2>Supported architectures?</h2>
|
||||
<p class="purple"> 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. <a href="amd64.html">More info.</a>
|
||||
</p>
|
||||
<h2>How can I trust SecBSD?</h2>
|
||||
<ul class="list">
|
||||
<li>Our packages are verificable by
|
||||
<a href="https://code.laylo.cloud/SecBSD/ports">inspecting them.</a>
|
||||
</li>
|
||||
<li>Binary packages and releases are to be signed by the project itself
|
||||
alongside with multiple core members.
|
||||
</li>
|
||||
<li>During the installation of SecBSD, the sets and packages
|
||||
are verified with checksums and GPG signatures.
|
||||
</li>
|
||||
</ul>
|
||||
<h2>How can I donate to SecBSD?</h2>
|
||||
<p class="purple">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
|
||||
<a href="https://www.openbsdfoundation.org/">OpenBSD
|
||||
Foundation</a> instead. That is - indirectly - also a
|
||||
donation to SecBSD but goes a much longer way.
|
||||
</p>
|
||||
<h2>Who design the website and SecBSD stuff?</h2>
|
||||
<p class="purple"> The best artist
|
||||
we known: <b class="green">Banshee.</b>
|
||||
</p>
|
||||
<h2>How can I contact SecBSD?</h2>
|
||||
<p class="purple">Through email:
|
||||
<b class="green">purplerain@secbsd.org</b> or
|
||||
<b class="green">h3artbl33d@secbsd.org</b>
|
||||
</p>
|
||||
<h2>License</h2>
|
||||
<p class="purple"> See <a href="license.html">License</a>
|
||||
</p>
|
||||
<h2>Last updated date of SecBSD website?</h2>
|
||||
<p class="purple"> Tue Jan 9 02:09:32 CET 2024.
|
||||
</p>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
66
hardware.html
Normal file
@ -0,0 +1,66 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>Hardware Donation</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="Hardware Donation">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box hardware">
|
||||
<div class="title green">HARD</div>
|
||||
<div class="subtitle">WARE</div>
|
||||
<div class="txt">
|
||||
<span class="green">█</span><b class="purple"> Interested in supporting us?</b>
|
||||
<div>
|
||||
<h2>Hardware wanted:</h2>
|
||||
<ul class="list">
|
||||
<li>Laptop or Desktop: mint condition is desirable.
|
||||
</li>
|
||||
<li>SSDs: For test machines and backup. Every
|
||||
disk is appreciated.
|
||||
</li>
|
||||
<li>Devices: WiFi Pineapple, HackRF One, Proxmark3, LAN Turtle,
|
||||
LAN Tap Pro, Packet Squirrel, Chameleon Tiny Pro.
|
||||
</li>
|
||||
<li>Boards: Raspberry Pi 3/4, BeagleBone, APU, NanoPi A64,
|
||||
Raspberry Pi Zero, Orange Pi.
|
||||
</li>
|
||||
</ul>
|
||||
<h3>You don't have hardware but you still want to help us?</h3>
|
||||
<ul class="list">
|
||||
<li>Spread the word in your social media. #SecBSD</li>
|
||||
<li>Be a SecBSD advocate. We need hackers sharing ideas all over
|
||||
the world.
|
||||
</li>
|
||||
<li>Prepare an Write-Up using SecBSD and share your knowledge
|
||||
and hacking skills to the community.
|
||||
</li>
|
||||
<li>Attend our hackathons. We want to solve big problems and
|
||||
hack everything.
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
BIN
img/0xdarkpadr3.png
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
img/0xdeadbea7.png
Normal file
After Width: | Height: | Size: 9.3 KiB |
BIN
img/about.png
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
img/arthome.png
Normal file
After Width: | Height: | Size: 274 KiB |
BIN
img/banshee.png
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
img/bg.png
Normal file
After Width: | Height: | Size: 163 KiB |
BIN
img/bsdbandit.png
Normal file
After Width: | Height: | Size: 8.6 KiB |
BIN
img/cwm.png
Normal file
After Width: | Height: | Size: 1.2 MiB |
BIN
img/git-laylo.png
Normal file
After Width: | Height: | Size: 1015 B |
BIN
img/h3artbl33d.png
Normal file
After Width: | Height: | Size: 12 KiB |
BIN
img/logo.png
Normal file
After Width: | Height: | Size: 607 B |
BIN
img/mastodon.png
Normal file
After Width: | Height: | Size: 366 B |
BIN
img/purplerain.png
Normal file
After Width: | Height: | Size: 9.7 KiB |
BIN
img/secbsd-core-team.png
Normal file
After Width: | Height: | Size: 5.9 KiB |
BIN
img/secbsd-mate.jpg
Normal file
After Width: | Height: | Size: 570 KiB |
BIN
img/secbsd-xfce.jpg
Normal file
After Width: | Height: | Size: 449 KiB |
BIN
img/twitter.png
Normal file
After Width: | Height: | Size: 337 B |
59
index.html
Normal file
@ -0,0 +1,59 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html"><img src="/img/logo.png" alt="[SecBSD]"></a></h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a class="active">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box welcome">
|
||||
<h3><span class="green">█</span> SecBSD</h3>
|
||||
<p>
|
||||
Welcome to our passionate community-driven project!<br><br>
|
||||
We're dedicated to developing a security-focused UNIX-like
|
||||
operating system based on the renowned OpenBSD.<br><br>
|
||||
SecBSD is designed to meet the needs of security researchers,
|
||||
pentesters, bug hunters, cybersecurity professionals, hacktivists,
|
||||
and privacy-conscious individuals.
|
||||
</p>
|
||||
<p>
|
||||
At the core of our development process is the same philosophy as OpenBSD,
|
||||
emphasizing robust security, privacy protection, and strong cryptography by
|
||||
default.
|
||||
</p>
|
||||
<p>
|
||||
Join a vibrant community of like-minded individuals and gain valuable insights
|
||||
from BSD users through our collaborative forum. Our commitment to open source
|
||||
principles ensures transparency, fostering innovation and shared learning.
|
||||
</p>
|
||||
<div class="year">2024</div>
|
||||
</div>
|
||||
<div class="arthome">
|
||||
<img src="img/arthome.png" alt="[Artwork]">
|
||||
</div>
|
||||
<div class="footer">
|
||||
<ul class="contact">
|
||||
<li><a rel="me" href="https://exquisite.social/@secbsd"><img src="/img/mastodon.png" alt="[Mastodon]"></a></li>
|
||||
<li><a href="https://code.laylo.cloud/SecBSD"><img src="/img/git-laylo.png" alt="[Git-Laylo]"></a></li>
|
||||
</ul>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
49
license.html
Normal file
@ -0,0 +1,49 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD License</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD License">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box">
|
||||
<b>█</b>
|
||||
<b>License</b><br>
|
||||
<pre>
|
||||
Copyright (c) 2018-2024 Purple Rain purplerain@secbsd.org
|
||||
|
||||
Permission to use, copy, modify, and distribute this software for any
|
||||
purpose with or without fee is hereby granted, provided that the above
|
||||
copyright notice and this permission notice appear in all copies.
|
||||
|
||||
THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
|
||||
WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
|
||||
MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
|
||||
ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
|
||||
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
|
||||
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
|
||||
OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
||||
</pre>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
25
license.template
Normal file
@ -0,0 +1,25 @@
|
||||
Below is an example license to be used for new code in SecBSD,
|
||||
modeled after the ISC license.
|
||||
|
||||
It is important to specify the year of the copyright. Additional years
|
||||
should be separated by a comma, e.g.
|
||||
Copyright (c) 2020, 2023
|
||||
|
||||
If you add extra text to the body of the license, be careful not to
|
||||
add further restrictions.
|
||||
|
||||
/*
|
||||
* Copyright (c) YYYY YOUR NAME HERE <user@your.dom.ain>
|
||||
*
|
||||
* Permission to use, copy, modify, and distribute this software for any
|
||||
* purpose with or without fee is hereby granted, provided that the above
|
||||
* copyright notice and this permission notice appear in all copies.
|
||||
*
|
||||
* THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
|
||||
* WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
|
||||
* MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
|
||||
* ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
|
||||
* WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
|
||||
* ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
|
||||
* OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
||||
*/
|
86
mirrors.html
Normal file
@ -0,0 +1,86 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD Mirrors</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD Mirrors">
|
||||
<link rel="canonical" href="https://www.secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box">
|
||||
<b class="green">█</b>
|
||||
<b>SecBSD Mirrors</b><br><br>
|
||||
<p class="purple">Download via HTTPS.
|
||||
</p>
|
||||
<p class="purple">SecBSD can be obtained via HTTPS.
|
||||
Typically you only need a single small piece of boot media and then the rest
|
||||
of the files can be installed from a number of locations, including directly
|
||||
off the internet.
|
||||
Consult the <a href="docs.html#overview">installation guide</a> for details.
|
||||
</p>
|
||||
<p class="purple">Choose a mirror near you from the following list of mirrors
|
||||
which provide SecBSD.
|
||||
</p>
|
||||
<b>Netherlands:</b>
|
||||
<ul class="list">
|
||||
<li>https://mirror.secbsd.org/pub/SecBSD<br>
|
||||
Location: Amsterdam.<br>
|
||||
Maintained by Purple Rain.<br>
|
||||
Protocols: https.<br><br>
|
||||
</li>
|
||||
<li>https://mirror.laylo.nl/pub/SecBSD<br>
|
||||
Location: Amsterdam.<br>
|
||||
Maintained by h3artbl33d.<br>
|
||||
Protocols: https.<br>
|
||||
Updated hourly from mirror.secbsd.org<br><br>
|
||||
</li>
|
||||
</ul>
|
||||
<p>Information for prospective mirrors</p>
|
||||
<p class="purple">To be listed on this page we require mirrors
|
||||
to be fast, up to date, capable, and well-connected to networks
|
||||
in the region in which they serve.
|
||||
</p>
|
||||
<p>Mirrors must carry the following:</p>
|
||||
<p>OS and packages for all architectures supported
|
||||
by SecBSD.
|
||||
</p>
|
||||
<p class="purple">As of Jan 2024, the minimum space required is approximately
|
||||
250GB.
|
||||
</p>
|
||||
<p>However, to reduce problems for users when snapshot
|
||||
packages are updated,
|
||||
it is strongly recommended to use the rsync options
|
||||
--delete-delay --delay-updates which requires additional space
|
||||
during updates.
|
||||
--fuzzy may also be helpful to reduce the amount of data transferred
|
||||
when updating snapshot packages. Depending on the disk space
|
||||
available, mirrors may provide more contents, such as older releases,
|
||||
current source tree, etc.
|
||||
</p>
|
||||
<p>Operators of mirrors who are interested in having their site added
|
||||
to the list on this page should contact purplerain@secbsd.org with
|
||||
further details about their site, including network connectivity,
|
||||
geographic location, and general information.
|
||||
</p>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
410
policy.html
Normal file
@ -0,0 +1,410 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD: Copyright Policy</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD Copyright Policy">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box">
|
||||
<b class="green">█</b>
|
||||
<b>SecBSD Copyright Policy</b><br><br>
|
||||
<p class="purple">Goal.
|
||||
</p>
|
||||
<p>
|
||||
Copyright law is complex, SecBSD policy is simple — SecBSD strives to
|
||||
provide code that can be freely used, copied, modified, and distributed
|
||||
by anyone and for any purpose. This maintains the spirit of the original
|
||||
Berkeley Software Distribution. The preferred wording of a license to be
|
||||
applied to new code can be found in the
|
||||
<a href="license.template">license template</a>.
|
||||
</p>
|
||||
<p>
|
||||
SecBSD can exist as it does today because of the example set by the
|
||||
Computer Systems Research Group at Berkeley and the battles which they
|
||||
and others fought to create a Unix source distribution un-encumbered
|
||||
by proprietary code and commercial licensing.
|
||||
</p>
|
||||
<p>
|
||||
The ability of a <strong>freely redistributable</strong> "Berkeley" Unix
|
||||
to move forward on a competitive basis with other operating systems depends
|
||||
on the willingness of the various development groups to exchange code amongst
|
||||
themselves and with other projects.
|
||||
Understanding the legal issues surrounding copyright is fundamental to
|
||||
the ability to exchange and re-distribute code, while honoring the spirit of
|
||||
the copyright and concept of attribution is fundamental to promoting the
|
||||
cooperation of the people involved.
|
||||
</p>
|
||||
<p class="purple">The Berkeley Copyright</p>
|
||||
<p>
|
||||
The original Berkeley copyright poses no restrictions on private or commercial
|
||||
use of the software and imposes only simple and uniform requirements
|
||||
for maintaining copyright notices in redistributed versions and
|
||||
crediting the originator of the material <strong>only</strong> in
|
||||
advertising.
|
||||
</p>
|
||||
<p class="purple">For instance:</p>
|
||||
<p>
|
||||
<pre>
|
||||
* Copyright (c) 1982, 1986, 1990, 1991, 1993
|
||||
* The Regents of the University of California. All rights reserved.
|
||||
*
|
||||
* Redistribution and use in source and binary forms, with or without
|
||||
* modification, are permitted provided that the following conditions
|
||||
* are met:
|
||||
* 1. Redistributions of source code must retain the above copyright
|
||||
* notice, this list of conditions and the following disclaimer.
|
||||
* 2. Redistributions in binary form must reproduce the above copyright
|
||||
* notice, this list of conditions and the following disclaimer in the
|
||||
* documentation and/or other materials provided with the distribution.
|
||||
* 3. All advertising materials mentioning features or use of this software
|
||||
* must display the following acknowledgement:
|
||||
* This product includes software developed by the University of
|
||||
* California, Berkeley and its contributors.
|
||||
* 4. Neither the name of the University nor the names of its contributors
|
||||
* may be used to endorse or promote products derived from this software
|
||||
* without specific prior written permission.
|
||||
*
|
||||
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
||||
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
||||
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
||||
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
||||
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
||||
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
||||
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
||||
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
||||
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
||||
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
||||
* SUCH DAMAGE.
|
||||
*
|
||||
</pre>
|
||||
<p>
|
||||
Berkeley rescinded the 3rd term (the advertising term) on 22 July 1999.
|
||||
Verbatim copies of the Berkeley license in the SecBSD tree have that
|
||||
term removed. In addition, many 3rd-party BSD-style licenses consist
|
||||
solely of the first two terms.
|
||||
</p>
|
||||
<p>
|
||||
Because the SecBSD copyright imposes no conditions beyond those
|
||||
imposed by the Berkeley copyright, SecBSD can hope to share the same
|
||||
wide distribution and applicability as the Berkeley distributions.
|
||||
It follows however, that SecBSD cannot include material which
|
||||
includes copyrights which are more restrictive than the Berkeley
|
||||
copyright, or must relegate this material to a secondary status,
|
||||
i.e. SecBSD as a whole is freely redistributable, but some optional
|
||||
components may not be.
|
||||
</p>
|
||||
<p class="purple">Copyright Law</p>
|
||||
<p>
|
||||
While the overall subject of copyright law is far beyond the scope of
|
||||
this document, some basics are in order. Under the current copyright law,
|
||||
copyrights are implicit in the creation of a new work and reside with
|
||||
the creator. In general the copyright applies
|
||||
only to the new work, not the material the work was derived from, nor
|
||||
those portions of the derivative material included in the new work.
|
||||
</p>
|
||||
<p>
|
||||
Copyright law admits to three general categories of works:
|
||||
<dl>
|
||||
<dt>Original Work
|
||||
<dd>A new work that is not derived from an existing work.
|
||||
<dt>Derivative Work
|
||||
<dd>Work that is derived from, includes or amends existing works.
|
||||
<dt>Compilation
|
||||
<dd>A work that is a compilation of existing new and derivative works.
|
||||
</dl>
|
||||
<p>
|
||||
The fundamental concept is that there is primacy of the copyright, that
|
||||
is a copyright of a derivative work does not affect the rights held by
|
||||
the owner of the copyright of the original work, rather only the part
|
||||
added. Likewise the copyright of a compilation does not affect the rights
|
||||
of the owner of the included works, only the compilation as an entity.
|
||||
</p>
|
||||
<p>
|
||||
It is vitally important to understand that copyrights are broad protections
|
||||
as defined by national and international copyright law. The "copyright
|
||||
notices" usually included in source files are not copyrights, but rather
|
||||
notices that a party asserts that they hold copyright to the material or
|
||||
to part of the material. Typically these notices are associated with
|
||||
license terms which grant permissions subject to copyright law and with
|
||||
disclaimers that state the position of the copyright holder/distributor
|
||||
with respect to liability surrounding use of the material.
|
||||
</p>
|
||||
<p>
|
||||
By international law, specifically the Berne Convention for the
|
||||
Protection of Literary and Artistic Works, part of the author's
|
||||
copyright, the so-called moral rights, are inalienable. This
|
||||
includes the author's right "to claim authorship of the work and
|
||||
to object to any distortion, mutilation or other modification of,
|
||||
or other derogatory action in relation to, the said work, which
|
||||
would be prejudicial to his honor or reputation". In some countries,
|
||||
the law reserves additional inalienable moral rights to the author.
|
||||
On the other hand, the author is free to transfer other parts
|
||||
of his copyright, the so-called economic rights, in particular the
|
||||
rights to use, copy, modify, distribute, and license the work.
|
||||
</p>
|
||||
<p class="purple">Permissions — the flip side</p>
|
||||
<p>
|
||||
Because copyrights arise from the creation of a work, rather than through
|
||||
a registration process, there needs to be a practical way to extend
|
||||
permission to use a work beyond what might be allowed by "fair use"
|
||||
provisions of the copyright laws.
|
||||
</p>
|
||||
<p>
|
||||
This permission typically takes the form of a "release" or "license"
|
||||
included in the work, which grants the additional uses beyond those
|
||||
granted by copyright law, usually subject to a variety of conditions.
|
||||
At one extreme sits "public domain" where the originator asserts that
|
||||
he imposes no restrictions on use of the material, at the other
|
||||
restrictive clauses that actually grant no additional rights or impose
|
||||
restrictive, discriminatory or impractical conditions on use of the work.
|
||||
</p>
|
||||
<p>
|
||||
Note that a license is not to be confused with a copyright transfer.
|
||||
While a transfer would give the new copyright holder <em>exclusive</em>
|
||||
rights to use the code and take these rights away from the author,
|
||||
a license typically grants <em>additional</em> people non-exclusive
|
||||
rights to use the code, while the authors retain all their rights.
|
||||
</p>
|
||||
<p>
|
||||
The above observations regarding moral rights imply that putting
|
||||
code under an ISC or two-clause BSD license essentially makes the
|
||||
code as free as it can possibly get. Modifying the wording of these
|
||||
licenses can only result in one of the three following effects:
|
||||
|
||||
<ul class="list">
|
||||
<li>making the code less free by adding additional restrictions
|
||||
regarding its use, copying, modification or distribution;
|
||||
<li>or effectively not changing anything by merely changing the wording,
|
||||
but not changing anything substantial regarding the legal content;
|
||||
<li>or making the license illegal by attempting to deprive the
|
||||
authors of rights they cannot legally give away.
|
||||
</ul>
|
||||
<p>
|
||||
Again, an important point to note is that the release and conditions can
|
||||
only apply to the portion of the work that was originated by the copyright
|
||||
holder—the holder of a copyright on a derivative work can neither
|
||||
grant additional permissions for use of the original work, nor impose more
|
||||
restrictive conditions for use of that work.
|
||||
</p>
|
||||
<p>
|
||||
Because copyright arises from the creation of a work and not the text
|
||||
or a registration process, removing or altering a copyright notice or
|
||||
associated release terms has no bearing on the existence of the copyright,
|
||||
rather all that is accomplished is to cast doubt upon whatever rights the
|
||||
person making the modifications had to use the material in the first place.
|
||||
Likewise, adding terms and conditions in conflict with the original terms
|
||||
and conditions does not supersede them, rather it casts doubts on the rights
|
||||
of the person making the amendments to use the material and creates confusion
|
||||
as to whether anyone can use the amended version or derivatives thereof.
|
||||
</p>
|
||||
<p>
|
||||
Finally, releases are generally binding on the material that they
|
||||
are distributed with. This means that if the originator of a work distributes
|
||||
that work with a release granting certain permissions, those permissions
|
||||
apply as stated, without discrimination, to all persons legitimately
|
||||
possessing a copy of the work. That means that having granted a permission,
|
||||
the copyright holder can not retroactively say that an individual or class
|
||||
of individuals are no longer granted those permissions. Likewise should
|
||||
the copyright holder decide to "go commercial" he can not revoke permissions
|
||||
already granted for the use of the work as distributed, though he may impose
|
||||
more restrictive permissions in his future distributions of that work.
|
||||
</p>
|
||||
<p class="purple">Specific Cases</p>
|
||||
<p>
|
||||
This section attempts to summarize the position of SecBSD relative to
|
||||
some commonly encountered copyrights.
|
||||
</p>
|
||||
<p>
|
||||
Again, an important point to note is that the release and conditions can
|
||||
only apply to the portion of the work that was originated by the copyright
|
||||
holder—the holder of a copyright on a derivative work can neither
|
||||
grant additional permissions for use of the original work, nor impose more
|
||||
restrictive conditions for use of that work.
|
||||
</p>
|
||||
<dl><dt>Berkeley<dd>
|
||||
<p>
|
||||
The Berkeley copyright is the model for the SecBSD copyright. It retains
|
||||
the rights of the copyright holder, while imposing minimal conditions on
|
||||
the use of the copyrighted material. Material with Berkeley copyrights,
|
||||
or copyrights closely adhering to the Berkeley model can generally be
|
||||
included in SecBSD.
|
||||
</p>
|
||||
|
||||
<dt>AT&T<dd><p>
|
||||
As part of its settlement with AT&T, Berkeley included an
|
||||
AT&T copyright notice on some of the files in 4.4BSD lite and lite2.
|
||||
The terms of this license are identical to the standard Berkeley license.
|
||||
</p>
|
||||
<p>
|
||||
Additionally, SecBSD includes some other AT&T code with non-restrictive
|
||||
copyrights, such as the reference implementation of
|
||||
<a href="https://github.com/onetrueawk/awk">awk</a>.
|
||||
</p>
|
||||
<dt>Caldera<dd><p>
|
||||
The original Unix code (AT&T versions 1 through 7 UNIX, including 32V)
|
||||
was freed by Caldera, Inc. on 23 January 2002 and is now available under a
|
||||
<a href="http://www.tuhs.org/Archive/Caldera-license.pdf">4-term BSD-style license</a>.
|
||||
As a result, it would theoretically be possible to incorporate original
|
||||
Unix code into SecBSD. However, that code is now so old that it does not
|
||||
satisfy today's interface and quality standards.
|
||||
</p>
|
||||
<dt>DEC, Sun, other manufacturers/software houses.<dd><p>
|
||||
In general SecBSD does not include material copyrighted by manufacturers
|
||||
or software houses. Material may be included where the copyright owner has
|
||||
granted general permission for reuse without conditions, with terms similar
|
||||
to the Berkeley copyright, or where the material is the product of an
|
||||
employee and the employer's copyright notice effectively releases any
|
||||
rights they might have to the work.
|
||||
</p>
|
||||
<dt>Carnegie-Mellon (CMU, Mach)<dd><p>
|
||||
The Carnegie-Mellon copyright is similar to the Berkeley copyright, except
|
||||
that it requests that derivative works be made available to Carnegie-Mellon.
|
||||
Because this is only a request and not a condition, such material can still
|
||||
be included in SecBSD. It should be noted that existing versions of Mach
|
||||
are still subject to AT&T copyrights, which prevents the general
|
||||
distribution of Mach sources.
|
||||
</p>
|
||||
<dt>Apache<dd><p>
|
||||
The original Apache license was similar to the Berkeley license,
|
||||
but source code published under version 2 of the Apache license is
|
||||
subject to additional restrictions and cannot be included into SecBSD.
|
||||
In particular, if you use code under the Apache 2 license, some of
|
||||
your rights will terminate if you claim in court that the code
|
||||
violates a patent.
|
||||
</p>
|
||||
<p>
|
||||
A license can only be considered fully permissive if it allows use
|
||||
by anyone for all the future without giving up any of their rights.
|
||||
If there are conditions that might terminate any rights in the
|
||||
future, or if you have to give up a right that you would otherwise
|
||||
have, even if exercising that right could reasonably be regarded
|
||||
as morally objectionable, the code is not free.
|
||||
</p>
|
||||
<p>
|
||||
Again, an important point to note is that the release and conditions can
|
||||
only apply to the portion of the work that was originated by the copyright
|
||||
holder—the holder of a copyright on a derivative work can neither
|
||||
grant additional permissions for use of the original work, nor impose more
|
||||
restrictive conditions for use of that work.
|
||||
</p>
|
||||
<p>
|
||||
In addition, the clause about the patent license is problematic because
|
||||
a patent license cannot be granted under Copyright law, but only under
|
||||
contract law, which drags the whole license into the domain of contract
|
||||
law. But while Copyright law is somewhat standardized by international
|
||||
agreements, contract law differs wildly among jurisdictions. So what
|
||||
the license means in different jurisdictions may vary and is hard to
|
||||
predict.
|
||||
</p>
|
||||
<dt>ISC<dd><p>
|
||||
The ISC copyright is functionally equivalent to a two-term BSD
|
||||
copyright with language removed that is made unnecessary by the
|
||||
Berne convention. This is the preferred license for new code
|
||||
incorporated into SecBSD. A sample license is available in the file
|
||||
<a href="license.template">license.template</a>.
|
||||
</p>
|
||||
<dt>GNU General Public License, GPL, LGPL, copyleft, etc.<dd><p>
|
||||
The GNU Public License and licenses modeled on it impose the restriction
|
||||
that source code must be distributed or made available for all works that
|
||||
are derivatives of the GNU copyrighted code.
|
||||
</p>
|
||||
<p>
|
||||
While this may superficially look like a noble strategy, it is a
|
||||
condition that is typically unacceptable for commercial use of software.
|
||||
So in practice, it usually ends up hindering free sharing and reuse
|
||||
of code and ideas rather than encouraging it.
|
||||
As a consequence, no additional software bound by the GPL terms
|
||||
will be considered for inclusion into the SecBSD base system.
|
||||
</p>
|
||||
<p>
|
||||
For historical reasons, the SecBSD base system still includes the
|
||||
following GPL-licensed components: the GNU compiler collection (GCC)
|
||||
with supporting binutils and libraries, GNU CVS, GNU texinfo,
|
||||
the mkhybrid file system creation tool, and the
|
||||
readline library. Replacement by equivalent, more freely licensed
|
||||
tools is a long-term desideratum.
|
||||
</p>
|
||||
<dt>OpenBSD<dd><p>
|
||||
SecBSD is fully based on and evolved from OpenBSD.
|
||||
The general OpenBSD license terms permit such use, copy, modify,
|
||||
and distribute this software for any purpose.
|
||||
OpenBSD license can generally be included in SecBSD.
|
||||
<dt>NetBSD<dd><p>
|
||||
Much of OpenBSD is originally based on and evolved from NetBSD, since some
|
||||
of the OpenBSD developers were involved in the NetBSD project. The general
|
||||
NetBSD license terms are compatible with the Berkeley license and permit
|
||||
such use. Material subject <strong>only</strong> to the general NetBSD
|
||||
license can generally be included in SecBSD.
|
||||
</p>
|
||||
<dt>FreeBSD<dd><p>
|
||||
Most of FreeBSD is also based on Berkeley licensed material or includes
|
||||
copyright notices based on the Berkeley model. Such material can be
|
||||
included in SecBSD, while those parts that are subject to GPL or
|
||||
various individual copyright terms that are at odds with the SecBSD license
|
||||
can not be included in SecBSD.
|
||||
</p>
|
||||
<dt>Linux<dd><p>
|
||||
Most of Linux is subject to GPL style licensing terms and therefore
|
||||
can not be included in SecBSD. Individual components may be eligible,
|
||||
subject to the terms of the originator's copyright notices. Note that
|
||||
Linux "distributions" may also be subject to additional copyright claims
|
||||
of the distributing organization, either as a compilation or on material
|
||||
included that is not part of the Linux core.
|
||||
</p>
|
||||
<dt>X.Org<dd><p>
|
||||
The X.Org Foundation maintains and distributes the X Window System
|
||||
under a modified MIT license, which is quite similar to the BSD
|
||||
license and additionally allows sublicensing. Under the name of
|
||||
Xenocara, the SecBSD base system includes an improved and actively
|
||||
maintained version of the X.Org code.
|
||||
</p>
|
||||
<dt>Shareware, Charityware, Freeware, etc.<dd><p>
|
||||
Most "shareware" copyright notices impose conditions for redistribution,
|
||||
use or visibility that are at conflict with the SecBSD project goals.
|
||||
Review on a case-by-case basis is required as to whether the wording
|
||||
of the conditions is acceptable in terms of conditions being requested vs.
|
||||
demanded and whether the spirit of the conditions is compatible with
|
||||
goals of the SecBSD project.
|
||||
</p>
|
||||
<dt>Public Domain<dd><p>
|
||||
While material that is truly entered into the "public domain" can be
|
||||
included in SecBSD, review is required on a case by case basis.
|
||||
Frequently the "public domain" assertion is made by someone who does
|
||||
not really hold all rights under copyright law to grant that status or
|
||||
there are a variety of conditions imposed on use. For a work to be
|
||||
truly in the "public domain" all rights are abandoned and the material
|
||||
is offered without restrictions.
|
||||
</p>
|
||||
<p>
|
||||
In some jurisdictions, it is doubtful whether voluntarily placing
|
||||
one's own work into the public domain is legally possible.
|
||||
For that reason, to make any substantial body of code free,
|
||||
it is preferable to state the copyright and put it under an ISC
|
||||
or BSD license instead of attempting to release it into the public
|
||||
domain.
|
||||
</p>
|
||||
</dl>
|
||||
</div>
|
||||
</body>
|
||||
</html>
|
60
screenshots.html
Normal file
@ -0,0 +1,60 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset=utf-8>
|
||||
<title>SecBSD Screenshots</title>
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
<meta name="description" content="SecBSD Screenshots">
|
||||
<link rel="canonical" href="https://secbsd.org/">
|
||||
<link rel="stylesheet" href="secbsd.css">
|
||||
</head>
|
||||
<style>
|
||||
img {
|
||||
padding: 5px;
|
||||
width: 160px;
|
||||
}
|
||||
|
||||
</style>
|
||||
<body>
|
||||
<header>
|
||||
<nav>
|
||||
<div>
|
||||
<h1><a href="index.html">
|
||||
<img src="/img/logo.png" alt="[SecBSD]"></a>
|
||||
</h1>
|
||||
</div>
|
||||
<ul>
|
||||
<li><a href="index.html">About</a></li>
|
||||
<li><a href="download.html">Download</a></li>
|
||||
<li><a href="docs.html">Docs</a></li>
|
||||
<li><a href="faq.html">Faq</a></li>
|
||||
<li><a href="team.html">Team</a></li>
|
||||
<li><a href="sponsors.html">Sponsors</a></li>
|
||||
</ul>
|
||||
</nav>
|
||||
</header>
|
||||
<div class="box">
|
||||
<b>█</b>
|
||||
<b>Screenshots</b><br>
|
||||
<div>
|
||||
<div class="row">
|
||||
<div class="item">
|
||||
<p>
|
||||