• 1 Post
  • 15 Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle



  • Not true. I’ve been involved in litigation with both AWS and Google over unsecured comms that were defined as being TLS secured in SLA/SLO contracts and found not to be. Not that anything nefarious was happening necessarily, but the expectation is clear.

    Whether these asshats even check for such requirements with a Musk run company right now 🤷

    It COULD possibly be that they are logging every exchange happening at the network fabric between the service layers, but nobody knows unless they intentionally take steps to investigate or accidentally prove it.






  • Well, firstly, it’s not what Tailscale is meant for. I’m getting downvoted by the people using the wrong tool for the wrong job.

    You don’t install a VPN on all your local machines just to talk to each other. That’s insane. You especially don’t install one that, while misconfigured, is sending all of its traffic OUTSIDE of your local network, then back in. This is what Tailscale on a number of local machines will do by default.

    The way Tailscale works is by installing a Wireguard client on a machine. It then checks in with their DERP servers to figure out it’s network situation (behind NAT, peers in the network, routing tables…etc). So when you have more than one client on the Tailscale network, it automagically assumes some things, the first being that these two machines dont have a more direct route to talk to each other.

    So then it will attempt to bridge a path between the DERP server each client is checked into, and pass traffic that way. Which means you then have two machines on the same local network sending traffic OUTSIDE of that network, then back in to complete a VPN network.

    This is stupid.

    You setup multiple different networks and use exit nodes to bridge two networks together with Tailscale. That’s the entire point. This means setting up routes to let the orchestration layer know that a set of certain machines exist in the same network, and shouldn’t use Tailscale to communicate with each other. Then it will only be using routes for REMOTE networks, where other clients exist, to pass traffic over the Tailscale network.

    May I ask what you were planning on doing with Tailscale? I can point you in the right direction.





  • So…CCC seems to be a very basic inventory management solution. What this generally describes is a system compromised of a database with a front-ends that makes sense of whatever the particular project is (car repair), and provides an easy to interact with the database.

    What you’re using now is simply for workflow management of projects in a simplified way, which is probably not what you want.

    So you need a database, and you also want an easy way to interface with it, so you can check out the plethora of inventory management solutions in the FOSS space, but if you want something pretty simple that you can more easily customize for your needs and workflow, have a look at the FOSS alternatives to Airtable like nocobase. You set up a simple data structure, then can slap together quick forms to work inside of with whatever fields and data you choose. Dead simple, but very extensible.

    Edit: Also check out Baserow maybe