[Verifying my OpenPGP key: openpgp4fpr:FED82F1C73FF53FB1EE9926336615E0FD12833CF]

  • 0 Posts
  • 16 Comments
Joined 4 years ago
cake
Cake day: February 18th, 2021

help-circle

  • What is safe on Nuckear Power Plants?

    It’s enough for hundredthousand of years, if only one time happens a SuperGAU. Only once is enough.

    And the nuclear waste is dangerous as fuck for also hundredthousand of years.

    And you can produce 30, 40 or maybe 50 years electric energy, and it needs the same time to decontaminate and dismantle a nuclear powerplant. And before it takes 20, 30 or mor years, to build such a plant… This is not cheap, not safe and not sustainable.





  • I run my own funkwhale. But i’m not happy with it. It has so many bugs and drawbacks. Searching for remote content does not work well. Sometimes it finds it, sometimes it needs 2, 3 or 5 tries of searching for. Sometimes it does not find it. Searching is inconsistent. The UI is also inconsistent. To find what you want to click, you have to search a lot… It’s not possible to modify metadata from already uploaded music. Change mp3-tags locally an upload it again is the way… You csn not move audios between channrls and libraries. The permissions-concept is broken.

    And the devs want to discuss about how to write about bigs, not about the bugs.

    I will drop funkwhale. It does not make me happy.






  • The services should be able, to talk to each other via ssh?

    Or do you have groups of servers?

    How many we are talking about?

    They are all virtual servers?

    Where is the hub located?

    In our company we have many services and many servers. We are talking about hundrets of services and servers. Snd they are very secure.

    So we have the servers on a big esxi (more than one) in 3 datacenters.

    There is one jumphost (high available… several instances). Direct connection from our workstations to a server is not possible. We have to use this jumphost. Login on the jumphost is not possible, only for jumping (ssh option -J).

    On the jumphost is for each user the publickey from a hardwaretoken. (Yubikey, etoken, nitrokey, name it) on its user in authorized-keys file. Only one pubkey.

    So you are not able to jump over the jumphost to a server, without a valid hardwaretoken.

    A NAT-Rule gives each user a individual source-IP…

    Then you can see in auditlog on each server who did the shit… even if he made sudo su… the source-ip is individualized for each user.

    And services run in different subnets and VLAN without connection to each other. So only services can talk together, who must talk.

    Another server is an ansible machine. This can connect to every single server too and fo good and really bad things… so this ansible-machine and the jumphost are in a physically secured zone in the Datacenter.

    You need an extra permission and an extra physical key, to come to this machines…

    And if one Service gets compromized, maximum the servers in the same vlan or subnet can be affected too. And the servers, which got an extra firewall-hole.

    So… if you are afraid of using ssh in your environment…

    Use hardware-keys for the ssh privatekey. No softwarekeys! If machines need to talk together via ssh, make smallest possible jails with subnets or vlans around them. Think about allowed commands in ssh-config/authorized_keys file!!! Think about a jumphost and allow different users only machines which they need. Think about physically protection about the jumphost. Think about serverinitiated backups…

    👍





  • If there’s a community serverA/tiki, you can search on serverB for serverA/tiki and join the community serverA/tiki from serverB. Content ist replicated to serverB and back.

    serverB/tiki@serverA is the replica you can fully use on serverB. This can exist beside serverB/tiki, which is a different community.

    If someone writes a posting or comment on serverA/tiki, you can see it in serverB/tiki@serverA.

    If someone writes a posting or comment on serverB/tiki@serverA, you can see it in serverA/tiki. (And even on serverC/tiki@serverA)