Brony: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
(created brony)
 
m (nicer long code format)
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{servers}}
Brony is a VPS located in Los Angeles, dedicated to the server known as [[Stallion]].
Brony is a VPS located in Los Angeles, dedicated to the server known as [[Stallion]].
It is a sibling of of [[Unicorn]].
It is a sibling of of [[Unicorn]].
Line 4: Line 6:


== How is this different from Unicorn? ==
== How is this different from Unicorn? ==
Los Angeles data center running Debian 11 Bullseye with 5.10x kernel
Los Angeles data center running Debian 11 Bullseye with 5.10.0-9-amd64


== Brony Currently Hosts ==
== Brony Currently Hosts ==
Add a service here.
no public services yet. maintainers needed<br /s>
 
tmux <br /s>
Podman <br /s>
Podman-compose <br /s>
ufw <br /s>
docker <br /s>


== Request a Service ==
== Request a Service ==
wireguard or tailscale -- https://www.linuxbabe.com/debian/wireguard-vpn-server-debian <br /s>
cockpit https://cockpit-project.org/ <br /s>
glances https://nicolargo.github.io/glances/ <br /s>
nginx proxy manager <br /s>
Ansible -- for reproducible builds <br /s>
minetest -- migrate from Unicorn <br /s>
minetest -- migrate from Unicorn <br /s>
ssb -- migrate scuttlebutt from Unicorn <br /s>
ssb -- migrate scuttlebutt from Unicorn <br /s>
minio -- migrate s3-compatible storage from Unicorn <br /s>


== SSH Config ==
== SSH Config ==
Note this SSH Config has been hardened.<br /s>
Note this SSH Config has been hardened.<br /s>
Public Keys required.<br /s>
'''No Passwords supported'''.<br /s>
'''No Passwords supported'''.<br /s>
[https://www.unixtutorial.org/how-to-generate-ed25519-ssh-key/ ed25519] protocol supported]! Successor to rsa<br /s>
[https://www.unixtutorial.org/how-to-generate-ed25519-ssh-key/ ed25519] protocol supported! <br /s>
rsa is still fine if you prefer it.
Successor to rsa, which is also fine<br /s>


<code>
<code>
Line 27: Line 40:
Consider generating a new, passwordless SSH key pair with
Consider generating a new, passwordless SSH key pair with


'''ec25519 key''' -- Requires recent openssh client software
'''ed25519 key''' -- Requires recent openssh client software
<code>$ ssh-keygen -b ed25519</code>
<code>$ ssh-keygen -t ed25519</code>


'''RSA Key'''
'''RSA Key'''
Line 35: Line 48:
then calling it, say, <code>brony-nb</code>, then add this to your <code>~/.ssh/config</code> file:
then calling it, say, <code>brony-nb</code>, then add this to your <code>~/.ssh/config</code> file:


<code>
<pre>
Host brony-nb<br />
Host brony-nb
User noisebridge<br />
User noisebridge
Hostname 199.241.139.224<br />
Port 1235
PreferredAuthentications publickey<br />
Hostname 199.241.139.224
IdentityFile ~/.ssh/brony-nb<br />
PreferredAuthentications publickey
</code>
IdentityFile ~/.ssh/brony-nb
</pre>


If your SSH pub key (<code>~/.ssh/brony-nb.pub</code>) has been added to <code>brony-nb:~/.ssh/authorized_keys</code>, you should now be able to shell in by typing
If your SSH pub key (<code>~/.ssh/brony-nb.pub</code>) has been added to <code>brony-nb:~/.ssh/authorized_keys</code>, you should now be able to shell in by typing
Line 48: Line 62:


...and thanks to the <code>~/.ssh/config</code> entry, the name of the server you're trying to SSH into -- namely <code>brony-nb</code> in this case -- should autocomplete!  Add your name to the access list below!
...and thanks to the <code>~/.ssh/config</code> entry, the name of the server you're trying to SSH into -- namely <code>brony-nb</code> in this case -- should autocomplete!  Add your name to the access list below!


== SSH Access ==
== SSH Access ==


* [[User:James|@James]] - James
* [[User:James|@James]]
* mana
* [[User:SuperQ|@SuperQ]]
* TJ
* evildan
* Danny
* [[User:Senoraraton|@Senoraraton]] - Claus
* Woz

Latest revision as of 21:25, 4 September 2022

Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Resources | Events | Projects | 5MoF | Meetings | Donate | (Edit)
Resources | Where to find things | Network | AV | Audio | Library | Servers | Printers | Sustenance | Edit
Servers | DevOps | Pegasus | Unicorn | Shed | Brony | Secretaribot | edit

Brony is a VPS located in Los Angeles, dedicated to the server known as Stallion. It is a sibling of of Unicorn. It has no guaranteed uptime or functionality; it is up to you to keep the services you want running, running. Like a stallion.

How is this different from Unicorn?[edit]

Los Angeles data center running Debian 11 Bullseye with 5.10.0-9-amd64

Brony Currently Hosts[edit]

no public services yet. maintainers needed

tmux
Podman
Podman-compose
ufw
docker

Request a Service[edit]

wireguard or tailscale -- https://www.linuxbabe.com/debian/wireguard-vpn-server-debian
cockpit https://cockpit-project.org/
glances https://nicolargo.github.io/glances/
nginx proxy manager
Ansible -- for reproducible builds
minetest -- migrate from Unicorn
ssb -- migrate scuttlebutt from Unicorn
minio -- migrate s3-compatible storage from Unicorn

SSH Config[edit]

Note this SSH Config has been hardened.
No Passwords supported.
ed25519 protocol supported!
Successor to rsa, which is also fine

I can haz access? Yes, but you are agreeing to help setup and maintain this!

Consider generating a new, passwordless SSH key pair with

ed25519 key -- Requires recent openssh client software $ ssh-keygen -t ed25519

RSA Key $ ssh-keygen -b 4096

then calling it, say, brony-nb, then add this to your ~/.ssh/config file:

Host brony-nb
User noisebridge
Port 1235
Hostname 199.241.139.224
PreferredAuthentications publickey
IdentityFile ~/.ssh/brony-nb

If your SSH pub key (~/.ssh/brony-nb.pub) has been added to brony-nb:~/.ssh/authorized_keys, you should now be able to shell in by typing

$ ssh brony-nb

...and thanks to the ~/.ssh/config entry, the name of the server you're trying to SSH into -- namely brony-nb in this case -- should autocomplete! Add your name to the access list below!

SSH Access[edit]