Reputation
202
Top tag
Next privilege 250 Rep.
View close votes
Badges
3 16
Newest
 Yearling
Impact
~24k people reached

  • 0 posts edited
  • 0 helpful flags
  • 18 votes cast
Aug
4
comment High quality software video telephony
No, I just need a working combination of both. For now I do not have one where sip works with video (and I do not know the precise reason why it does not).
Aug
4
comment High quality software video telephony
Ok. I assume Google Talk would give me the same poor quality as I experienced it before. But I could try with sip. Something there I do not understand is whether video with sip poses requirements for the sip-provider or is it rather that the endpoints need to support the same standard? I didn't get sip to work with video so-far but have not tried empathy.
Aug
4
asked High quality software video telephony
Jul
9
awarded  Yearling
May
8
awarded  Popular Question
Apr
18
comment Whitelist for migration of kubuntu configuration files
This is what I am usually doing. For many dot files a kubuntu/ubuntu version change will indeed be irrelevant because there is only a minor or no version change of the applications they configure. The ones you mentioned, I would copy immediately because I don't expect any trouble. On the other hand, especially for kde applications, it is particularly tempting to copy them (because they have plenty of options) but the risk to introduce errors is much higher and problems would often not pop up immediately.
Apr
17
accepted Add resolution mode for xorg-dummy
Apr
17
asked Whitelist for migration of kubuntu configuration files
Oct
28
awarded  Popular Question
Oct
4
awarded  Popular Question
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.