Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[BackupPC\-users\]\s+can\s+run\s+su\s+backuppc\s+user\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[BackupPC\-users\]\s+can\s+run\s+su\s+backuppc\s+user\s*$/: 7 ]

Total 7 documents matching your query.

1. [BackupPC-users] can run su backuppc user (score: 1): Author: draccusfly <backuppc-forum AT backupcentral DOT com>; Date: Tue, 11 Dec 2012 04:38:19 -0800; I inherited an existing backuppc system which is working in the main but there are a couple of issues that I am troubleshooting. 1 is email not going out, so I logged on to the server and tried to ru; /usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2012-12/msg00034.html (12,892 bytes)
2. Re: [BackupPC-users] can run su backuppc user (score: 1): Author: Richard Shaw <hobbes1069 AT gmail DOT com>; Date: Tue, 11 Dec 2012 07:48:13 -0600; Two ideas: 1. Try "su backuppc" as root since it shouldn't ask for a password. 2. Make sure the password is right by resetting it, "passwd backuppc". On a side note, system accounts shouldn't have sh; /usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2012-12/msg00035.html (13,264 bytes)
3. Re: [BackupPC-users] can run su backuppc user (score: 1): Author: Jim Kyle <jim AT jimkyle DOT com>; Date: Tue, 11 Dec 2012 08:25:35 -0600; This is definitely worth emphasizing. The only time I've been invaded in the past decade was a result of allowing backuppc to have shell access, together with other security failures such as allowing; /usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2012-12/msg00036.html (13,239 bytes)
4. Re: [BackupPC-users] can run su backuppc user (score: 1): Author: "Michael Stowe" <mstowe AT chicago.us.mensa DOT org>; Date: Tue, 11 Dec 2012 07:57:49 -0600; Let's stop right there -- you either know the backuppc password, or you don't. You can always "su -" first (to root), or use the root account to reset the backuppc password, but if you're getting an; /usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2012-12/msg00037.html (13,205 bytes)
5. Re: [BackupPC-users] can run su backuppc user (score: 1): Author: "Tyler J. Wagner" <tyler AT tolaris DOT com>; Date: Tue, 11 Dec 2012 16:12:52 +0000; I bet one donut that he knows the "backuppc" HTTPauth password, not the system user password. Regards, Tyler -- Commander Harken: "Seems odd youd name your ship after a battle you were on the wrong s; /usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2012-12/msg00040.html (12,776 bytes)
6. Re: [BackupPC-users] can run su backuppc user (score: 1): Author: "Tyler J. Wagner" <tyler AT tolaris DOT com>; Date: Tue, 11 Dec 2012 16:32:54 +0000; Sorry, that came out less pleasant than I intended. The next step is to reset the backuppc system user password and login that way: sudo su passwd backuppc (enter your sudo password) (enter the backu; /usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2012-12/msg00041.html (13,091 bytes)
7. Re: [BackupPC-users] can run su backuppc user (score: 1): Author: Koen Vermeer <koen AT vermeer DOT tv>; Date: Wed, 12 Dec 2012 23:37:17 +0100; I've been trying to figure out a way to prevent having to allow shell access for backuppc on the clients it needs to backup through ssh/rsync. I consider the backuppc account on the clients to be a s; /usr/local/webapp/mharc-adsm.org/html/BackupPC-users/2012-12/msg00044.html (12,840 bytes)

Current List: 1 - 7
Page: [1]