Initial commit.

This commit is contained in:
inference 2022-06-27 00:35:36 +01:00
parent 02c5d160ba
commit 27c9957ba8
17 changed files with 688 additions and 3 deletions

View File

@ -1,6 +1,6 @@
MIT License MIT License
Copyright (c) <year> <copyright holders> Copyright (c) 2022 Inference
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

View File

@ -1,2 +1,54 @@
# infnet-www <h1>Inferencium Network - Website</h1>
<p>Inferencium Network website.</p>
<br>
<br>
<h2>Licensing</h2>
<p>All content is licensed under MIT License.</p>
<br>
<br>
<h2>Security</h2>
<p>All files are checked for security issues; however, it is always the<br>
user's responsibility to audit the code before installing and/or executing<br>
it.<br>
<br>
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>
<br>
<h3>stable</h3>
<p>Stable branch. Complete and stable versions of the software are stored<br/>
here.<br/>
<br/>

21
blog/blog.html Normal file
View File

@ -0,0 +1,21 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Blog</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Blog</h1>
<br>
<h2>2022-01-29</h2>
<p>#1 - <a href="systemd-insecurity.html">systemd Insecurity</a></p>
<br>
<br>
<h2>2022-01-27</h2>
<p>#0 - <a href="foss-is-working-against-itself.html">FOSS is Working Against Itself</a></p>
<br>
<br>
<br>
<a href="../index.html">Back</a>
</body>
</html>

View File

@ -0,0 +1,115 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Blog - FOSS is Working Against Itself</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Blog - #0</h1>
<br>
<h2>FOSS is Working Against Itself</h2>
<br>
<h3>2022-01-27 (UTC+00:00)</h3>
<br>
<h4>Introduction</h4>
<p>The world has become a dangerous, privacy invading, human rights stripping,<br>
totalitarian place; in order to combat this, people are joining a growing,<br>
and dangerous, trend, which I will refer to in this post as the "FOSS<br>
movement".<br>
With that stated, I will now debunk the misinformation being spread inside<br>
of this extremely flawed movement.</p>
<br>
<p>The FOSS movement is an attempt to regain privacy and control over our<br>
devices and data, but the entire concept of FOSS-only, at the current time,<br>
is severely, and dangerously, flawed. What the FOSS community does not seem<br>
to understand is the fact that most FOSS software cares not about security.<br>
"Security"; keep that word in mind as you progress through this article.<br>
What is security? Security is being safe and secure from adversaries and<br>
unwanted consequences; security protects our rights and allows us to<br>
protect ourselves. Without security, we have no protection, and without<br>
protection, we have a lack of certainty of everything else, including<br>
privacy and control, which is what the FOSS movement is seeking.</p>
<br>
<p>FOSS projects rarely take security into account; they simply look at the<br>
surface level, rather than the actual root cause of the issues they are<br>
attempting to fight against. In this case, the focus is on privacy and<br>
control. Without security mechanisms to protect the privacy features and<br>
the ability to control your devices and data, it can be stripped away as<br>
if it never existed in the first place, which, inevitably, leads us back to<br>
the beginning, and the cycle repeats. With this ideology, privacy and<br>
control will *never* be achieved. There is no foundation to build privacy<br>
or control upon. It is impossible to build a solid, freedom respecting<br>
platform on this model.</p>
<br>
<h4>Example: Smartphones</h4>
<p>A FOSS phone, especially so-called "Linux phones" are completely<br>
detrimental to privacy and control, because they do not have the security<br>
necessary to enforce that privacy. Unlocked bootloaders prevent the device<br>
from verifying the integrity of the boot chain, including the OS, meaning<br>
any big tech or government entity can simply inject malicious code into<br>
your software and you wouldn't have any idea it was there. If that's not<br>
enough of a backdoor for you to reconsider your position, how about the<br>
trivial evil maid and data extraction attacks which could be executed on<br>
your device, whether with coercion or not? With Android phones, this is<br>
bad enough to completely break the privacy and control the FOSS movement<br>
seeks, but "Linux phones" take it a step further by implementing barely any<br>
security, if any at all. Privilege escalation is trivial to achieve on any<br>
Linux system, which is the reason Linux hardening strategies often include<br>
restricting access to the root account; if you root your Android phone, or<br>
use a "Linux phone", you've already destroyed the security model, and thus<br>
privacy and control model you were attempting to achieve. Not only are<br>
these side effects of FOSS, so is the absolutely illogical restriction of<br>
not being able to, or making it unnecessarily difficult to, install and<br>
update critical components of the system, such as proprietary firmware,<br>
which just so happens to be almost all of them. "Linux phones" are not as<br>
free as they proclaim to be.</p>
<br>
<p>You may ask "What's so bad about using LineageOS?", to which I answer with<br>
"What's not bad about it?".<br>
<br>
- LineageOS uses debug builds, not safe and secure release builds.<br>
- LineageOS requires an unlocked bootloader.<br>
- LineageOS does not install critically important firmware without manual<br>
flashing.<br>
- LineageOS does not implement rollback protection, meaning any adversary,<br>
including a goverment entity, can simply downgrade the OS to a previous<br>
version in order to exploit known security vulnerabilities.<br>
<br>
LineageOS is not the only Android OS (commonly, and incorrectly, referred<br>
to as a "ROM") with such issues, but it is one of the worst. The only<br>
things such insecure OSes can provide you are customisation abilities, and<br>
a backdoor to your data. They are best suited as a development OS, not a<br>
production OS.</p>
<br>
<h4>Solution</h4>
<p>What can you do about this? The answer is simple; however, it does require<br>
you to use logic, fact, and evidence, not emotion, which is a difficult<br>
pill for most people to swallow. Use your adversaries' weapons against<br>
them. The only way to effectively combat the privacy invasion and lack of<br>
control of our devices and data is to become a renegade and not take sides.<br>
Yes, that means not taking sides with the closed source, proprietary, big<br>
tech and government entities, but it also means not taking sides with any<br>
FOSS entities. The only way to win this war is to take *whatever* hardware<br>
and software you can, and use it tactically.</p>
<br>
<p>The only solution for phone security, privacy, and control, is to use<br>
a Google Pixel (currently, 4 series or newer) running GrapheneOS. Google<br>
Pixel phones allow you complete bootloader freedom, including the ability<br>
to lock the bootloader after flashing a custom OS (GrapheneOS includes a<br>
custom OS signing key to allow locking the bootloader and enabling verified<br>
boot to prevent malware persistence, evil maid attacks, and boot chain<br>
corruption), long device support lifecycles (minimum 3 years for Pixel 3a<br>
series to Pixel 5a, minimum 5 years for Pixel 6 series), and fast,<br>
guaranteed security updates for the entire support timeframe of the<br>
devices.</p>
<br>
<h4>Conclusion</h4>
<p>Use what you can, and do what you can. By neglecting security, you are,<br>
even if unintentionally, neglecting exactly what you are trying to gain;<br>
privacy and control.</p>
<br>
<br>
<br>
<a href="blog.html">Back</a>
</body>
</html>

View File

@ -0,0 +1,82 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Blog - systemd Insecurity</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Blog - #1</h1>
<br>
<h2>systemd Insecurity</h2>
<br>
<h3>2022-01-29 (UTC+00:00)</h3>
<br>
<p>Anyone who cares about security may want to switch from systemd as soon as<br>
possible; its lead developer doesn't care about your security at all, and<br>
makes the thing seem like an intentional government backdoor if I've ever<br>
seen one.</p>
<br>
<br>
<p>Poettering:<br>
"You don't assign CVEs to every single random bugfix we do, do you?"</p>
<br>
<p>My thoughts:<br>
Uhh... Yes, if they're security related.</p>
<br>
<p>Source:<br>
<a href="https://github.com/systemd/systemd/pull/5998">https://github.com/systemd/systemd/pull/5998</a></p>
<br>
<br>
<br>
<p>Poettering:<br>
"Humpf, I am not convinced this is the right way to announce this.<br>
We never did that, and half the CVEs aren't useful anyway, hence I am not<br>
sure we should start with that now, because it is either inherently<br>
incomplete or blesses the nonsensical part of the CVE circus which we<br>
really shouldn't bless..."</p>
<br>
<p>My thoughts:<br>
CVEs are supposed to be for security, and a log of when they were<br>
found and their severity, so yes, it *is* the correct way to announce it.<br>
It seems as if over 95 security concious people think the same.</p>
<br>
<p>Source:<br>
<a href="https://github.com/systemd/systemd/pull/6225">https://github.com/systemd/systemd/pull/6225</a></p>
<br>
<br>
<br>
<p>Poettering:<br>
"I am not sure I buy enough into the security circus to do that though for<br>
any minor issue..."</p>
<br>
<p>Source:<br>
<a href="https://github.com/systemd/systemd/issues/5144">https://github.com/systemd/systemd/issues/5144</a></p>
<br>
<br>
<br>
<p>Poettering:<br>
"Yes, as you found out "0day" is not a valid username. I wonder which tool<br>
permitted you to create it in the first place. Note that not permitting<br>
numeric first characters is done on purpose: to avoid ambiguities between<br>
numeric UID and textual user names.<br>
<br>
systemd will validate all configuration data you drop at it, making it hard<br>
to generate invalid configuration. Hence, yes, it's a feature that we don't<br>
permit invalid user names, and I'd consider it a limitation of xinetd that<br>
it doesn't refuse an invalid username.<br>
<br>
So, yeah, I don't think there's anything to fix in systemd here. I<br>
understand this is annoying, but still: the username is clearly not valid."</p>
<br>
<p>My thoughts:<br>
systemd was the thing that allowed root access just because a username<br>
started with a number.</p>
<br>
<p>Source:<br>
<a href="https://github.com/systemd/systemd/issues/6237">https://github.com/systemd/systemd/issues/6237</a></p>
<br>
<br>
<br>
<a href="blog.html">Back</a>
</body>
</html>

View File

@ -0,0 +1,24 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - Briar</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>Briar</h2>
<br>
<p>Updated: 2022-01-28 (UTC+00:00)</p>
<br>
<pre>
<code>
briar://ad6uk4zjzhepynpcgre7vmtt6el5dg2d7e4xtadquxfmf37ajolck
</code>
</pre>
<br>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

View File

@ -0,0 +1,27 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - Matrix</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>Matrix</h2>
<br>
<p>Updated: 2022-01-28 (UTC+00:00)</p>
<br>
<h3>inference:matrix.inferencium.net</h3>
<h4>Key</h4>
<p>Unavailable. Request key via different contact method.</p>
<br>
<br>
<h3>inferenceus:matrix.org</h3>
<h4>Key</h4>
<p>Unavailable. Request key via different contact method.</p>
<br>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

112
contact/contact-pgp.html Normal file
View File

@ -0,0 +1,112 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - PGP</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>PGP</h2>
<br>
<p>Updated: 2022-03-21 (UTC+00:00)</p>
<br>
<h3>admin@inferencium.net</h3>
<p>For administrative contact only.</p>
<br>
<h4>Key</h4>
<h5>RSA 4096</h5>
<br>
<pre>
<code>
-----BEGIN PGP PUBLIC KEY BLOCK-----<br>
Version: OpenPGP.js v4.10.10<br>
Comment: https://openpgpjs.org<br>
<br>
xsFNBGIw/NgBEACyXsDdt4P9iPLvIAlumO6pINuiYEhDFAQmUOcCngBGmPih<br>
L1gMuGn8I51sPz+ay2KtmlcTkkjTrrEPrEHsJMFcGV64ZENnHOim8+s4COTP<br>
wDBw1Ef25jll0xyV237MiKIc1limIPCKlHJXi/PE2WoZimF9S4xV8daLgQPJ<br>
0LEXxWbYbmcbutah6PzFj3NxvmqqwcNEiwREr7YCOAVeXbVm4/55F/08UJ5y<br>
Pbq14gWn4/Zxif8Oq27PxNsOoFRhVV61v4i/IHWzQbgRjmnbDagO5YI9XkBx<br>
dg70Cmw9dyRRB7HXwZan+TdbJvCU5utUK2+FF4es7VUmX7oKRmfxrU20DLhy<br>
75kRpiGDz1RtsO4JYq6aND2j5i1B16bQyzR0gpGaWa37wQoaF/+Ll3orXas3<br>
tEDIbHnHKdOjKPaz9NQ0vaW5MvGQRypIV8w0lbgBZCnWfYPMNGNbvQhMDFmM<br>
tR6gd4K9okCHZjE4QTTqdU4aajCtzZFJzmYxCnz4b7VOZcfVKlevlWdj7X8p<br>
SdASu8AwCoeMAucHZCr9IShO1+jdbuQ8G/NzhKIQzWPqdTgvk8TGt/3g/d8H<br>
NwS5CQ+A3j3O8j2St3j5QVnEikY4J8KPWwyJTT7pItDqcu1bfba8zqZvfhrZ<br>
3+Z7Vx8Z+rBJShAtkPO9ZBJPj429PE5ojHqfLQARAQABzS1hZG1pbkBpbmZl<br>
cmVuY2l1bS5uZXQgPGFkbWluQGluZmVyZW5jaXVtLm5ldD7CwY0EEAEIACAF<br>
AmIw/NgGCwkHCAMCBBUICgIEFgIBAAIZAQIbAwIeAQAhCRD8ZLRAFZ20kxYh<br>
BDjs0DnY7anWB0RahPxktEAVnbSTlgIP/3KAQNAYnVb42PduGATQwsxCUgsC<br>
/L7spfkMOHkbMMyZmdPAX+T1VB97CgIN9zTylJq81Viqsr5LZvDL+N5HPJoK<br>
vvwM/YJcIqqq3OJRVmhGQbF3Mdd+WKocD7S6nZ6jtG12rnJ6LezosvXd6IT/<br>
5OsYHrSuw7cU5E4cxnyhbvi/DHSLzGqxtQEFoMGRn+nVmLgjQpqKIuWkv13y<br>
yK+9abKkuDUl/WMrvLOvA3mGCsH3lmgbwQifMTUfT0Mvr+wvk9X/dwrx9XA9<br>
76fFrZ93t/N8CuiudpBFhy4RzoefdcERXrmCjEqkQTxU/mUOl2er251yik54<br>
9In38bRYdogz2C+Gb7IVj89Ir68pBn5Equh0jzL+OqyVc2KbwO6mMk1jghe8<br>
8aqlEcKpz3oUc09Rveal04hN7jEwl/pp1c/TlqQLxfKKB3y6xoxOMF7FIaNa<br>
8x3n7WFNltBK2JLWMIkp5xLIN+RWWIWF/YFOz8m4w7rIKRkJTO4AYWUzFWt1<br>
Y8aXX8o4jJ8pKFZRELqGmxFg34RHoXd3xSscg87f/zcHGsZ0/y+p9yeQr/II<br>
iJsBsslM0Ng7JumOrjaWs9z0qp+tCKdL2b5OhSvWe0B4BxZCnEX4KWdXklKC<br>
7uvwn0AF/mmcsiqXgM5nwK6uagy7AXe3GeLeWBCChwGua21xybUfknJrzsFN<br>
BGIw/NgBEACz6/bXKKm9itFmk/nl04ZR1nDWmsELaVMMALiEnd/jBXDyhUdR<br>
zo7i5IDyZzRG9PXPpMTSDLSXXiYtzstrcxIYuvjz6p7i2n8pAPxY817iR2oY<br>
0/ahXilvtUhJjzv95KOQDcw7BaQXZkFHrAPEzkFfvgtwQpDpZ+Z+ZhLNrhuu<br>
4A/PcYR5k/g+4WaeE3y181THR0uromnujkCNPY2HWFuy7GjqZpyyVhxEbt7q<br>
0VSBPQv0pBSTT0UP3VvsWrtjgcC5oZYT346GdZ57Kh9+VKik82AjnQtOzhcM<br>
75HSRmBsrK952377lmQN/mee5d+88Rjt1+kHykPFJmdY5pkaGLPKZYjs4n09<br>
VY5Ul8WxE9lAJlYurGi8bX9F66UVUQVcl+hH7NcfVvuoLBt4NYandV47Q71K<br>
TCri9fmFdjMc/s9I+gXNn6GNz0PF90baHvxQdHjCbXsQAHWsUemLknochUN/<br>
JGCPqa3t+fZ4OqXhXl6Vw1JTF89kRN31QTOdUEUN/BAPr5S8Q20TkUzRm+JD<br>
yfj5DDiqtk1N6BppWQaBh4kgS7SSEuTM81x4SsQj3FsqosWIgDVDr0Yr4goV<br>
gdxlFfKsVXL2nH8ErTx5wPvt1jQgJKgWEoUUEK1T/pFsvrVxhwtO2ojH5N6r<br>
LuLyc+tqXqjHjYn7ad6SnARnL4dMbSwQ5wARAQABwsF2BBgBCAAJBQJiMPzY<br>
AhsMACEJEPxktEAVnbSTFiEEOOzQOdjtqdYHRFqE/GS0QBWdtJPHLg//WiKu<br>
AoWWIRsu4bKkiMqijuvcP3uhD1QHN/9NqIGndpTeYwcWq0FPLuJOI4f6Xfde<br>
Wy94Z2uQeLGaWr0EldV+o1hUivEIqiiVw3HWguOwT/kD01aJKJEgpGepcbDh<br>
Bf4JmA6pQHFS96ZP7r29uY1k4fI2KTnDLmd3TkbdhaI+Dh97LYEOOZJKBclJ<br>
u+lNc5//+qUarJaGWzKda3IaL3KP4SIFcDhgSCu5hkzEsxSN4fbZyAbM591+<br>
7tW9gNkJbG9JanqGWbTU0rsPKcwSrH/oAyM3qPSKAQ8MFBsxUqH/k7V5zcqx<br>
C2T6rNxcy5JU+MPOC5id8dptrwgq0oNV5eLiPPWPbj/kG1yhdzLw4mIOaHEa<br>
+sW6NqQL0yf4insxSBpxTmPe84OFp0IozfJzMkBd18D+vYDGdgXwuZi+hvH7<br>
XY/Xz9F7PUv7mumMhKlxBsQhQaveUyH/6kAG4ipsuPclRRfL1ftVLWPmdDe0<br>
GtcAtX+qjQV5YeeYAjSnCSiPyIbCEAA9jOBB7HtTvcGMj75dfzYMs3pcizXa<br>
weZMwRXzOsJVO6q62r0Sb1tUS0yEj2lObyX7n6idgAaVSIKEGKx1sEPtNHg9<br>
6ESGYDi3hwdX0RfKt/Cv+sNy//gSZsE1Gr4B1/WV8c5MqdpE/cjMkcqC/z6p<br>
0i4j09yHG+UlGIJZUsw=<br>
=2ODK<br>
-----END PGP PUBLIC KEY BLOCK-----<br>
</code>
</pre>
<br>
<h3>social@inferencium.net</h3>
<p>For general contact.</p>
<br>
<h4>Key</h4>
<h5>ECC</h5>
<br>
<pre>
<code>
-----BEGIN PGP PUBLIC KEY BLOCK-----<br>
Version: OpenPGP.js v4.10.10<br>
Comment: https://openpgpjs.org<br>
<br>
xjMEYjD/BxYJKwYBBAHaRw8BAQdALBtIsyLOayEUssxa5f5pLdQxRAQTplB5<br>
ZY9I+ybVUkDNL3NvY2lhbEBpbmZlcmVuY2l1bS5uZXQgPHNvY2lhbEBpbmZl<br>
cmVuY2l1bS5uZXQ+wo8EEBYKACAFAmIw/wcGCwkHCAMCBBUICgIEFgIBAAIZ<br>
AQIbAwIeAQAhCRDlSUqme2RZVhYhBEJf3afVq9MlXLV+U+VJSqZ7ZFlWsGcB<br>
AL8nP1puGfnYZMoYdLft9Ai1QxzGFuDs592DTbWL1RBjAQCb15rr4TK0oKbE<br>
fdI8lGtCzUH1KSaaVoUE6cKXSa38Ds44BGIw/wcSCisGAQQBl1UBBQEBB0Dd<br>
/Ge6qs2PFydKC7GdwNNHBQFnvQvEcaIgseAaRep0BwMBCAfCeAQYFggACQUC<br>
YjD/BwIbDAAhCRDlSUqme2RZVhYhBEJf3afVq9MlXLV+U+VJSqZ7ZFlWrA8A<br>
/ijI1spZ0HAi+B49vorMcBKFi3wiotJ/skwt3CVl4LJwAQC2Pk2ZNyyW+6L4<br>
9RxAJVLmoFsXYnihH0qkYENpeD+wCQ==<br>
=f8Tz<br>
-----END PGP PUBLIC KEY BLOCK-----<br>
</code>
</pre>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

View File

@ -0,0 +1,24 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - Session</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>Session</h2>
<br>
<p>Updated: 2022-01-28 (UTC+00:00)</p>
<br>
<pre>
<code>
05d3f27cf9fafbc82f6e954b5d50f46b1a149ea90f44ff0312c3dff91bdaefb909
</code>
</pre>
<br>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

View File

@ -0,0 +1,24 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - Signal</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>Signal</h2>
<br>
<p>Updated: 2022-06-23 (UTC+00:00)</p>
<br>
<pre>
<code>
+447549902964
</code>
</pre>
<br>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

View File

@ -0,0 +1,22 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - Threema</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>Threema</h2>
<br>
<p>Updated: 2022-01-28 (UTC+00:00)</p>
<br>
<h3>MD649ERN</h3>
<h4>Key</h4>
<img src="key-threema.png">
<br>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

30
contact/contact-wire.html Normal file
View File

@ -0,0 +1,30 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - Wire</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>Wire</h2>
<br>
<p>Updated: 2022-01-28 (UTC+00:00)</p>
<br>
<h3>inferenceus</h3>
<h4>Key</h4>
<pre>
<code>
ID: 9B3FF3698A9B068E<br>
Fingerprint: 3997d980ed11c922bd180a8f9057e4244c992cb3c14f2c297dd461e32fd43f40
<br>
ID: 0DCF3E2C3C088176<br>
Fingerprint: 17eec9631680e918cbd4789012d6da17d62d89c3b21425b1946997ae3ac44c80
</code>
</pre>
<br>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

50
contact/contact-xmpp.html Normal file
View File

@ -0,0 +1,50 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact - XMPP</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>XMPP</h2>
<br>
<p>Updated: 2022-05-30 (UTC+00:00)</p>
<br>
<p>Whenever possible, open the links to pin the fingerprint directly from<br>
this webpage. If that is not possible, manually verify the fingerprints.</p>
<br>
<h3>inference@xmpp.inferencium.net</h3>
<h4>Key</h4>
<h5>Smartphone</h5>
<pre>
<code>
b27950b8-8b514a6a-003a8de2-e23d7180-f2fd2eb5-9affe331-276e3281-f43b8271
</code>
</pre>
<a href="xmpp:inference@xmpp.inferencium.net?omemo-sid-89840358=b27950b88b514a6a003a8de2e23d7180f2fd2eb59affe331276e3281f43b8271">xmpp:inference@xmpp.inferencium.net?omemo-sid-89840358=b27950b88b514a6a003a8de2e23d7180f2fd2eb59affe331276e3281f43b8271</a>
<br>
<br>
<h5>Desktop</h5>
<pre>
<code>
87ffbf5a-40f271c7-4615d84c-5816ef07-b7e7a90a-5406edb1-b2b8378f-0439551d
</code>
</pre>
<br>
<br>
<h3>inference@creep.im</h3>
<h4>Key</h4>
<h5>Smartphone</h5>
<pre>
<code>
6678c6ec-6e7eb26f-cf093493-440576e9-48bafb65-d16cc63c-2370c2ab-0a00d576
</code>
</pre>
<a href="xmpp:inference@creep.im?omemo-sid-1167352551=6678c6ec6e7eb26fcf093493440576e948bafb65d16cc63c2370c2ab0a00d576">xmpp:inference@creep.im?omemo-sid-1167352551=6678c6ec6e7eb26fcf093493440576e948bafb65d16cc63c2370c2ab0a00d576</a>
<br>
<br>
<br>
<a href="contact.html">Back</a>
</body>
</html>

39
contact/contact.html Normal file
View File

@ -0,0 +1,39 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network - Contact</title>
<link rel="stylesheet" href="../infnet.css">
</head>
<body>
<h1>Contact</h1>
<br>
<h2>E2EE contact methods</h2>
<br>
<h3>Preferred</h3>
<p>Whenever possible, use the following contact methods;<br>
they allow verification to mitigate man-in-the-middle attacks,<br>
have solid security, and reasonable privacy.<br>
<br>
<p>Use the keys for each contact method to verify my devices.<br>
Note that verification does not verify a person, only their devices,<br>
and can be defeated via coercion or other force.</p>
<br>
<p>- <a href="contact-pgp.html">PGP</a><br>
- <a href="contact-signal.html">Signal</a><br>
- <a href="contact-xmpp.html">XMPP</a><br>
- <a href="contact-wire.html">Wire</a><br>
- <a href="contact-threema.html">Threema</a></p>
<br>
<h3>Metadata-free</h3>
<p>If metadata leakage is an issue for you, you can use the following<br>
contact methods. Note that these services do not have verification<br>
functionality, and will be treated as less secure.</p>
<br>
<p>- <a href="contact-briar.html">Briar</a></p>
<p>- <a href="contact-session.html">Session</a></p>
<br>
<br>
<br>
<a href="../index.html">Back</a>
</body>
</html>

BIN
contact/key-threema.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 35 KiB

13
index.html Normal file
View File

@ -0,0 +1,13 @@
<!DOCTYPE html>
<html>
<head>
<title>Inferencium Network</title>
<link rel="stylesheet" href=infnet.css>
</head>
<body>
<h1>Inferencium Network</h1>
<br>
<p>- <a href="contact/contact.html">Contact</a></p>
<p>- <a href="blog/blog.html">Blog</a></p>
</body>
</html>

50
infnet.css Normal file
View File

@ -0,0 +1,50 @@
body {
font-family: Roboto, sans-serif;
background-color: #262626;
}
h1 {
font-family: Roboto, sans-serif;
font-size: 24px;
color: #ffffff;
}
h2 {
font-family: Roboto, sans-serif;
font-size: 22px;
color: #ffffff;
}
h3 {
font-family: Roboto, sans-serif;
font-size: 20px;
color: #ffffff;
}
h4 {
font-family: Roboto, sans-serif;
font-size: 18px;
color: #ffffff;
}
h5 {
font-family: Roboto, sans-serif;
font-size: 16px;
color: #ffffff;
}
p {
font-family: Roboto, sans-serif;
font-size: 16px;
color: #ffffff;
}
code {
font-size: 14px;
color: #ffffff;
}
a {
font-family: Roboto, sans-serif;
color: #ffffff;
}