From 318e24a093ce8ef682bae49d9293a2710d51cef7 Mon Sep 17 00:00:00 2001
From: forest
- (the tilde ~ here represents the user's home directory, - /home/username on linux, - C:\Users\username on Windows, and - /Users/username on MacOS). -
++ ℹ️ INFO: The tilde ~ here represents the user's home directory, ++
+- Linux: /home/username
+- Windows: C:\Users\username
+- MacOS: /Users/username
+
Also, note that as the .ssh folder's name starts with a period, it is a "hidden" folder. diff --git a/capsulflask/templates/add-ssh-key-to-existing-capsul.html b/capsulflask/templates/add-ssh-key-to-existing-capsul.html new file mode 100644 index 0000000..72b35a4 --- /dev/null +++ b/capsulflask/templates/add-ssh-key-to-existing-capsul.html @@ -0,0 +1,48 @@ +{% extends 'base.html' %} + +{% block title %}Add New SSH Key{% endblock %} + +{% block content %} +
+ We don't offer this feature in the capsul.org web console, and we never will. +
++ Why? See the FAQ on recovery: +
++ Can you recover my passwords/insert new keys? ++Can we? Technically yes. Will we? No, never. It would violate the trust that our users have in us. + We have no interest in touching client VMs after they're running. + We promise to keep your machines running smoothly. + If you lose access to your VM, that's on you.
+
+ If we built this feature, that would represent an additional security risk: anyone who can log into your capsul account + or somehow exploit the capsul web application would be able to then log into your Capsul(s). +
++ None of the big name cloud service providers offer this feature out of the box either, presumably for similar reasons. +
++ So if you want to add a new key to the list of authorized ssh public keys on your capsul, you will have to do it manually: + Just edit the + ~/.ssh/authorized_keys + file on your capsul. You would paste in each additional ssh public key as a new line in that file. +
++ ℹ️ INFO: The tilde ~ here represents the user's home directory, so + /home/cyberian/.ssh/authorized_keys for the default user on your capsul. ++ + + +
There are no hard rules for this sort of thing, but here are some guidelines:
f1-xs: blog, vpn, bot, cgit
f1-s: a bot, owncloud, gitea, popular blog
@@ -20,17 +20,17 @@f1-xx: something gargantuan
ssh to the ip provided to you using the cyberian user.
$ ssh cyberian@1.2.3.4
For more information, see Understanding the Secure Shell Protocol (SSH).
See Troubleshooting SSH.
The cyberian user has passwordless sudo access by default. This should work:
# Linux @@ -40,22 +40,22 @@ $ sudo su - $ doas su -
We do, but right now it's a manual process. Shoot us an email and we'll get it done.
Your VM will eventually be deleted. Capsul will send you a few inoffensive reminders as that termination date approaches.
We associate an email address with every VM so that we can track payment and respond to support requests.
If you pay with a credit card, Stripe stores some additional details about you that we literally cannot delete.
Make it into a mailserver, a tor relay, a VPN host, whatever you'd like - we do have one small request, though.
Crypto mining on capsul is currently considered obnoxious behavior, because the hashrates on our CPUs is so low and because mining crypto consumes entire processor cores that could have otherwise been shared between many dozens of other users.
In the future, if we have plentiful CPU resources, we may come out with a tier more suitable for mining - maybe a high cpu tier or similar, where each VM gets a full dedicated core and sharing them is not anticipated.
@@ -63,32 +63,32 @@ $ doas su -Also, mandatory: our systems exist within the USA, and as such those systems are bound by US law.
Can we? Technically yes. Will we? No, never. It would violate the trust that our users have in us. We have no interest in touching client VMs after they're running. We promise to keep your machines running smoothly. If you lose access to your VM, that's on you.
Not now, but email us and we can probably figure something out.
Capsul runs on a server named Baikal which Cyberia built from scratch & mailed to a datacenter in Georgia called CyberWurx. CyberWurx staff installed it for us in a rack space that Cyberia pays for.
Yep, see our support page.
No, but we normally respond pretty quickly.
Maybe! Email ops@cyberia.club and ask us about it.
Paste the contents of your SSH public key file here. ( Something like ~/.ssh/id_rsa.pub ) -
+
++ ℹ️ INFO: The tilde ~ here represents the user's home directory, +++
+ +- Linux: /home/username
+- Windows: C:\Users\username
+- MacOS: /Users/username
+
The contents of this file should look similar to ssh-rsa AAAAC3NzaC1l...Yqv== me@my-computer
diff --git a/capsulflask/templates/troubleshooting-ssh.html b/capsulflask/templates/troubleshooting-ssh.html
index 2c702e5..87cb5c7 100644
--- a/capsulflask/templates/troubleshooting-ssh.html
+++ b/capsulflask/templates/troubleshooting-ssh.html
@@ -47,10 +47,15 @@
or the server tells it "too many failed attempts" and closes the connection.
- (the tilde ~ here represents the user's home directory,
- /home/username on linux,
- C:\Users\username on Windows, and
- /Users/username on MacOS).
+
+ ℹ️ INFO: The tilde ~ here represents the user's home directory, ++
+ +- Linux: /home/username
+- Windows: C:\Users\username
+- MacOS: /Users/username
+