aborsy
I highly recommend Debian. Breath of fresh air and freedom, compared to windows and MacOS.
Those who don't catch up will lose.
I install tailscale on my cloud vps which I use for downloading torrents. I want my laptop to talk to this node, but I don't want this vm talk to my laptop, which is the whole purpose of ACLs. My ACL is deny by default, so that is great and easy to set. But now this node can still send arbitrary files to my laptop. If I don't remember to tag it, I'm vulnerable. If I do, there is still a window that this node can send me files until I tag it (I can't install tailscale to a tag).
Sending a file otherwise normally requires an app listening to a port, so taildrop permissions should be same as network permissions set by ACL.
BTW, last year or so tailscale advertised a position for someone to manage complexity of tailscale. Founder was talking about this issue. They seem to be aware of the problem.
I personally use openssh, but someone else may use tailscale SSH.
I use it extensively, and I would rather pay them a fee if they could review thr code.
A possibility is a lock down mode, disabling risky features.
I just want a VPN for connrctiviy, no taildrop, taildrive, SSH, funnel, services, DNS, node sharing, ...They are disabled in my admin console, but the code runs on my devices and they can be enabled by mistake.
A question. Taildrop enables unauthenticated input and doesn't even obey ACLs. I'm not quite sure about this, but couldn't malware in a low trust device send a file to my Synology NAS, which will then automatically process it for indexing things like thumbnail, leading to potential code execution? Why doesn't it obey ACLs, and why isn't the recipient approval needed before the file exits the sender's device? I use tags, but I'm the owner not the tag.
Or perhaps, as Zack noted, Musk showed them the way?
Some of these vulnerabilities are critical. One compromised node with ssh can get root every other node.
Calling it slop, AI, conveys nothing, 10000 words does not help. They provide practical demonstration, and explain the cause.
In my opinion tailscale needs to focus on secure networking. File sharing, DNS, SSH, Funnel, ... can be handled by dedicated tools.
How many lines of code is tailscale client nowadays?
They went with python and it's just too general and verbose.
If I’m a mathematician, I can write public posts on math. Extensive posts about politics, AI, crypto, … are not useful without expertise in those domains
It seems now he is mobilizing the community to convince taxpayers continue to pay even though AI may do a better job in his profession.
Also, his opinion of AI has continually changed in the past years after the capabilities were demonstrated.
Or will access to internal frontier models provide a big boost?
ZFS send raw encrypted stream from laptop to a server automatically. Encrypted compressed incremental. No need to verify: if snapshot exists at destination, there is no error. If a problem is encountered, restore from redundancy. Errors can be detected and corrected.
Restic has also been working great. The problem is that, it has no redundancy to correct errors. The assumption is that, server holding repository will have redundancy, but then I can replicate directly to that server. I worry that at some point, there will be an error in repository. I may loose 5 years of snapshots (restic has some functionality to remove involved snapshots and rebuild the index, but may not succeed).
Kopia has error correction, with Reed Solomon.
Borg2 has perpetually remained in beta. Looking forward to test it.
I stay away from sync: problems with permissions, git repo, conflict, incomplete sync status in syncthing etc.
GNOME Remote Login runs an RDP server, and RDP indeed isn’t fast enough, although is TLS-encrypted.
How does RustDesk compare with that?