It seems like servers automatically trust clients that respond to them, and likewise, clients automatically trust the first server they “see” on a network.
Is there a way to configure servers to “find” but not automatically “adopt” new clients? Like, some way to moderate or approve new clients before allowing them to backup to my server?
I’m setting up UrBackup on a large network, and I only want to backup computers we set up in our department. If another department decides to do something similar, I don’t want to risk us adopting their computers, or our computers finding their server first.
Stopping it, I am not sure, but you can take the server_idents.txt file that is normally found on the clients connected to your server and apply them to your new clients.
Also, if you are not accepting anymore clients then you can set your maximum the server will take to the amount you have. That way new clients can find your server but be automatically rejected.
Someone probably knows more about situations like this, but a good fall-back would to just replace (or add) the server_idents file on the client to associate it with the correct server.
I would say if you are worried about stuff like this, it is better to just use the Internet mode for the local clients. That is, put a firewall in front of UrBackup only allowing the UrBackup Internet port and perhaps the HTTP port and then manually add all the clients.
I don’t mind the way it works now, but I do wish I was given the opportunity to approve the client. As it is now, all you need to effectively disable backups is a machine on the LAN and piles of data that doesn’t compress well (like someone’s pirated movie collection).
What i do is set the default backup folder to something that doesn’t exists.
And i set up configurations only using group , so when a new client appear i need to manually put it in a group for backups to be done.
That stop the backup from auto-starting, but that wont stop the key to be auto-registered