175 reputation
213
bio website
location
age
visits member for 2 years, 4 months
seen yesterday

Aug
17
comment How to run backintime as a user
The reason is that some users may be using the machines to be backed up very irregularly and the backup over network would often be interrupted as the user switches off. In these cases it would be better if the user starts the backup consciously and waits until it is finished. I cannot boot the machines remotely to ensure a regular backup.
Aug
15
comment How to run backintime as a user
I understand, but I could use sudo to allow only a specific backintime command which includes the backup option (or write a script which performs this command, make it write protected, and add it to the sudoers configuration).
Aug
13
comment How to run backintime as a user
I do not really find the bug right now, but it exists and I saw that you had already answered with the patch. I applied the patch successfully. Only the question if letting the user run the command line backintime manually with sudo would be save is open for me. But perhaps it is not easy to know this.
Jul
24
comment How to run backintime as a user
I had similar problems with commandline backintime (actually I had created a bug for it). Is there a patch for it as well?
Jul
24
accepted How to run backintime as a user
Jul
24
comment How to run backintime as a user
Currently I do not have this option. My ssh server is one with restricted capabilities on an energy saving android device and allows only a single user.
Jul
23
comment How to run backintime as a user
If I would allow password less backup for all users (with ssh-key) this would still imply that they gain access to the server if not I restrict this server-side, right?
Jul
23
comment How to run backintime as a user
Thanks! I have version 1.0.34-0.1, so I seem to be affected indeed. The security issue you describe, is it because users with these privileges users may change the configuration within backintime-kde4 such as to backup the root to their own target and then read the files? Would this be different if I would allow them to run only the command line version backintime with specified config file in /root?
Jul
20
revised How to run backintime as a user
added 278 characters in body
Jul
20
comment How to run backintime as a user
One reason why the configuration can't be entirely global is that I don't want to give all users access to the server therefore the private ssh-key should be only root-readable. I don't want to complicate the configuration by restricting rights on the server (can't do it anyway). Also, I think, backintime may store a root-readable password. When I perform the backup as described there are apparently incorrect errors like "Not configured!". The backups finish however gracefully.
Jul
20
comment How to run backintime as a user
The ways it doesn't work are plentiful and so are the error messages. Depending on what I try (local or with ssh, user directory or root, backintime or backintime-kde, with ssh-agent or without, ...). The ultimate goal is to backup a specific machine (data from several users directories) automatically to a server via ssh (without asking the user). Therefore the solution to have the configuration in root makes some sense. In summary: I don't want to change the way I do the backup because it is the result of a painful optimization process. The question is if there is a solution which simplifies.
Jul
20
comment How to run backintime as a user
If I run su on my system it expects a password which I don't know (not configured?). sudo -i would work, but by itself it does not seem to solve the problem.
Jul
20
asked How to run backintime as a user
Jul
2
awarded  Curious
May
3
accepted Getting older packages from ppa
Apr
25
awarded  Nice Question
Mar
20
revised svn SQLite compiled for 3.7.17, but running with 3.6.1
added details
Mar
20
comment svn SQLite compiled for 3.7.17, but running with 3.6.1
I wanted to give you the chance to edit your answer ... I am grateful for your answer, but accepting it would not be entirely correct, I think. I can edit the question a bit if you want.
Mar
20
comment svn SQLite compiled for 3.7.17, but running with 3.6.1
Not the precise problem, but it helped me to find the solution quickly. I had installed Mathematica which apparently brings it's own version of libsqlite. Since I had to add the Mathematica libdir to $LD_LIBRARY_PATH svn seemingly tried to use this version. How would I force it to use the default sqlite version assuming that I want to continue using the old version with Mathematica?
Mar
20
comment svn SQLite compiled for 3.7.17, but running with 3.6.1
Maybe also noteworthy. This kind of operation usually works with kdesvn on my system. However it has a bug which leads to locks if there are version conflicts. No my working copy is locked and I cannot do a cleanup, because it produces a similar error as the update command.