Inferencium/website
1
0
Fork 0
Code Issues Activity

Contact Pages Improvements

Browse Source
This commit is contained in:
inference 2022-11-14 11:55:36 +00:00
commit 46983e9be5
6 changed files with 64 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

39
README.md
View File

@ -3,11 +3,14 @@
<br>
<br>
<h2>Licensing</h2>
<p>All content is licensed under BSD 3-Clause Clear License.</p>
<p>All content is licensed under BSD 3-Clause Clear license.</p>
<br>
<p>Exceptions: All content outside of code, including personal content<br>
<p>Exceptions:<br>
<ol>
<li>All content outside of code, including personal content<br>
such as blog posts, is copyrighted and cannot be distributed or modified<br>
without explicit consent from myself.</p>
without explicit consent from myself.</li></p>
</ol>
<br>
<br>
<h2>Security</h2>
@ -19,40 +22,14 @@ The maintainers take no responsibility for any security issues which<br>
may arise due to usage of this repository.</p>
<br>
<br>
<h2>Policy</h2>
<h3>Contributing</h3>
<p>To contribute to the project, submit a pull request. All pull requests<br>
are subject to approval.<br>
<br>
Code must follow the standard style for Inferencium Network code:<br>
- 80 character column limit.<br>
- Tab indents.<br>
- 1 tab indent equals 4 columns.<br>
- Comments must be used for each different block of code.<br>
- Comments must be concise. Do not make comments longer than necessary.<br>
- Code and comments must be professional. No funny or vulgar code or<br>
comments.<br>
<br>
Files must be stored in their related directories.<br>
<br>
Text files must be stored as plain text (.txt) or Markdown (.md) files.<br>
<br>
All dates and times must be ISO 8601 compliant (YYYY-MM-DD HH:MM).<br>
<br>
All filenames must be most significant to least significant, lowercase, and<br>
hyphens must be used instead of spaces.</p>
<br>
<br>
<h2>Branches</h2>
<h3>dev</h3>
<p>Development branch. All pre-alpha development and alpha testing happens<br/>
here.<br/>
Merge requests must be made to the dev branch.</p>
<br>
<h3>beta</h3>
<p>Beta branch. All beta testing of the software happens here.</p>
<p>Beta branch. All beta testing happens here.</p>
<br>
<h3>stable</h3>
<p>Stable branch. Complete and stable versions of the software are stored<br/>
here.<br/>
<p>Stable branch. Complete and stable versions are stored here.<br/>
<br/>

27
blog/systemd-insecurity.html
View File

@ -19,23 +19,29 @@
<h2>systemd Insecurity</h2>
<br>
<p>Posted: 2022-01-29 (UTC+00:00)</p>
<p>Updated: 2022-10-29 (UTC+00:00)</p>
<p>Updated: 2022-11-14 (UTC+00:00)</p>
<br>
<br>
<p>Anyone who cares about security may want to switch from systemd as soon as
possible; its lead developer doesn't care about your security at all.</p>
<br>
<br>
<h3>Issue #0 - Against CVE Assignment</h3>
<br>
<p>Poettering:<br>
"You don't assign CVEs to every single random bugfix we do, do you?"</p>
<br>
<p>My thoughts:<br>
Yes, if they're security related.</p>
Yes, if they're security-related.</p>
<br>
<p>Source:<br>
<a class="body-link" href="https://github.com/systemd/systemd/pull/5998">https://github.com/systemd/systemd/pull/5998</a></p>
<a class="body-link" href="https://github.com/systemd/systemd/pull/5998#issuecomment-303782334"
>systemd GitHub Issue 5998</a></p>
<br>
<br>
<br>
<h3>Issue #1 - CVEs Are Not Useful</h3>
<br>
<p>Poettering:<br>
"Humpf, I am not convinced this is the right way to announce this.
We never did that, and half the CVEs aren't useful anyway, hence I am not
@ -49,19 +55,25 @@ found and their severity, so yes, it *is* the correct way to announce it.
It seems as if over 95 security-concious people think the same.</p>
<br>
<p>Source:<br>
<a class="body-link" href="https://github.com/systemd/systemd/pull/6225">https://github.com/systemd/systemd/pull/6225</a></p>
<a class="body-link" href="https://github.com/systemd/systemd/pull/6225#issuecomment-311739869"
>systemd GitHub Issue 6225</a></p>
<br>
<br>
<br>
<h3>Issue #2 - Security is a Circus</h3>
<br>
<p>Poettering:<br>
"I am not sure I buy enough into the security circus to do that though for
any minor issue..."</p>
<br>
<p>Source:<br>
<a class="body-link" href="https://github.com/systemd/systemd/issues/5144">https://github.com/systemd/systemd/issues/5144</a></p>
<a class="body-link" href="https://github.com/systemd/systemd/issues/5144#issuecomment-276740654"
>systemd GitHub Issue 5144</a></p>
<br>
<br>
<br>
<h3>Issue #3 - Blaming the User</h3>
<br>
<p>Poettering:<br>
"Yes, as you found out "0day" is not a valid username. I wonder which tool
permitted you to create it in the first place. Note that not permitting
@ -73,7 +85,7 @@ to generate invalid configuration. Hence, yes, it's a feature that we don't
permit invalid user names, and I'd consider it a limitation of xinetd that
it doesn't refuse an invalid username.<br>
<br>
So, yeah, I don't think there's anything to fix in systemd here. I<
So, yeah, I don't think there's anything to fix in systemd here. I
understand this is annoying, but still: the username is clearly not valid."</p>
<br>
<p>My thoughts:<br>
@ -81,7 +93,8 @@ systemd was the thing that allowed root access just because a username
started with a number, then Poettering blamed the user.</p>
<br>
<p>Source:<br>
<a class="body-link" href="https://github.com/systemd/systemd/issues/6237">https://github.com/systemd/systemd/issues/6237</a></p>
<a class="body-link" href="https://github.com/systemd/systemd/issues/6237#issuecomment-311900864"
>systemd GitHub Issue 6237</a></p>
<br>
<br>
</body>

6
contact.html
View File

@ -21,10 +21,10 @@
<h3>Preferred</h3>
<p>Whenever possible, use the following contact methods;
they allow verification to mitigate man-in-the-middle attacks,
have solid security, and reasonable privacy.<br>
have high security, and reasonable privacy.<br>
<br>
<p>Use the keys for each contact method to verify my devices.
Note that verification does not verify a person, only their devices,
<p>Use the keys for each contact method to verify my devices.<br>
Note: Verification does not verify a person, only their devices,
and can be defeated via coercion or other force.</p>
<br>
<p><img class="logo-small" src="img/logo-signal.png" width="40px" height="40px"/> <a class="body-link" href="contact/signal.html">Signal</a><p>

3
contact/signal.html
View File

@ -18,7 +18,8 @@
<br>
<h2>Signal</h2>
<br>
<p>Updated: 2022-06-23 (UTC+00:00)</p>
<p>Updated: 2022-11-14 (UTC+00:00)</p>
<br>
<br>
<code>
+447549902964

15
contact/threema.html
View File

@ -2,27 +2,28 @@
<html>
<head>
<title>Inferencium Network - Contact - Threema</title>
<link rel="stylesheet" href="/infnet.css">
<link rel="stylesheet" href="../infnet.css">
</head>
<div class="sidebar">
<a class="title">Inferencium Network</a><br>
<br>
<br>
<div><a href="/about.html">About</a></div>
<div><a href="/contact.html">Contact</a></div>
<div><a href="/blog.html">Blog</a></div>
<div><a href="/source.html">Source</a></div>
<div><a href="../about.html">About</a></div>
<div><a href="../contact.html">Contact</a></div>
<div><a href="../blog.html">Blog</a></div>
<div><a href="../source.html">Source</a></div>
</div>
<body>
<h1>Contact</h1>
<br>
<h2>Threema</h2>
<br>
<p>Updated: 2022-01-28 (UTC+00:00)</p>
<p>Updated: 2022-11-14 (UTC+00:00)</p>
<br>
<br>
<h3>MD649ERN</h3>
<h4>Key</h4>
<img src="../img/key-threema.png">
<img src="../img/key-threema.png" width="200px" height="200px">
<br>
<br>
</body>

46
contact/xmpp.html
View File

@ -2,55 +2,55 @@
<html>
<head>
<title>Inferencium Network - Contact - XMPP</title>
<link rel="stylesheet" href="/infnet.css">
<link rel="stylesheet" href="../infnet.css">
</head>
<div class="sidebar">
<a class="title">Inferencium Network</a><br>
<br>
<br>
<div><a href="/about.html">About</a></div>
<div><a href="/contact.html">Contact</a></div>
<div><a href="/blog.html">Blog</a></div>
<div><a href="/source.html">Source</a></div>
<div><a href="../about.html">About</a></div>
<div><a href="../contact.html">Contact</a></div>
<div><a href="../blog.html">Blog</a></div>
<div><a href="../source.html">Source</a></div>
</div>
<body>
<h1>Contact</h1>
<br>
<h2>XMPP</h2>
<br>
<p>Updated: 2022-10-13 (UTC+00:00)</p>
<p>Updated: 2022-11-14 (UTC+00:00)</p>
<br>
<p>Whenever possible, open the links to pin the fingerprint directly from this
webpage. If that is not possible, manually verify the fingerprints.</p>
<br>
<br>
<h3>inference@inferencium.net</h3>
<h4>Key</h4>
<h5>Smartphone</h5>
<pre>
<code>
1bd03c6a 5e011655 2fafd697 da4fce70 63de5a83 a264a34a fcce78fe 6b06820c
</code>
</pre>
<a class="body-link" href="xmpp:inference@inferencium.net?omemo-sid-1586888206=1bd03c6a5e0116552fafd697da4fce7063de5a83a264a34afcce78fe6b06820c">xmpp:inference@inferencium.net?omemo-sid-1586888206=1bd03c6a5e0116552fafd697da4fce7063de5a83a264a34afcce78fe6b06820c</a>
<code>
1bd03c6a 5e011655 2fafd697 da4fce70 63de5a83 a264a34a fcce78fe 6b06820c
</code>
<br>
<a class="body-link" href="xmpp:inference@inferencium.net?omemo-sid-1586888206=1bd03c6a5e0116552fafd697da4fce7063de5a83a264a34afcce78fe6b06820c"
>xmpp:inference@inferencium.net?omemo-sid-1586888206=1bd03c6a5e0116552fafd697da4fce7063de5a83a264a34afcce78fe6b06820c</a>
<br>
<br>
<h5>Desktop</h5>
<pre>
<code>
87ffbf5a 40f271c7 4615d84c 5816ef07 b7e7a90a 5406edb1 b2b8378f 0439551d
</code>
</pre>
<code>
87ffbf5a 40f271c7 4615d84c 5816ef07 b7e7a90a 5406edb1 b2b8378f 0439551d
</code>
<br>
<br>
<br>
<h3>inference@plus.st</h3>
<h4>Key</h4>
<h5>Smartphone</h5>
<pre>
<code>
9f9b50e4 3bb5ae5d 886213ad 43015719 7c40aa99 e436445d e0e360a9 24076015
</code>
</pre>
<a class="body-link" href="xmpp:inference@plus.st?omemo-sid-1890454018=9f9b50e43bb5ae5d886213ad430157197c40aa99e436445de0e360a924076015">xmpp:inference@plus.st?omemo-sid-1890454018=9f9b50e43bb5ae5d886213ad430157197c40aa99e436445de0e360a924076015</a>
<code>
9f9b50e4 3bb5ae5d 886213ad 43015719 7c40aa99 e436445d e0e360a9 24076015
</code>
<br>
<a class="body-link" href="xmpp:inference@plus.st?omemo-sid-1890454018=9f9b50e43bb5ae5d886213ad430157197c40aa99e436445de0e360a924076015"
>xmpp:inference@plus.st?omemo-sid-1890454018=9f9b50e43bb5ae5d886213ad430157197c40aa99e436445de0e360a924076015</a>
<br>
<br>
<br>