Matt Godbolt wrote:
>
>
> Matt Godbolt wrote:
>> Hi there,
>>
>> I've just installed BackupPC at my company having happily used it at 
>> home for some time.  In both locations it's used in a mixed OS 
>> environment, but at work we've decided to use SMB shares to read from 
>> everyone's PCs for ease-of-use reasons.  As such we have a backuppc 
>> domain user and this has access to everybody's C$ shares.
>>
> [snip]
>
> After a little more investigation, it would appear this is a known 
> problem.  According to:
> https://bugzilla.samba.org/show_bug.cgi?id=3974 this is fixed in 3.0.23c
>
> However, it's also referenced by 
> https://bugzilla.samba.org/show_bug.cgi?id=2051 and 
> https://bugzilla.samba.org/show_bug.cgi?id=3954 with the implication 
> that a patch applied by Red Hat might have reintroduced the issue.
>
> Sorry for the confusion, I'll go chase Red Hat on this samba issue.
I had the same problem with my server (CentOS 5).  As a workaround until 
Red Hat fixes the issue, this perl script will solve the problem:

#!/usr/bin/perl
$service = shift @ARGV;
unshift @ARGV, $ENV{PASSWD};
unshift @ARGV, $service;
exec "/usr/bin/smbclient", @ARGV;

Just put it in /usr/bin and have backuppc point to it instead of 
smbclient.  It will insert the password from the environment into the 
command string.  There probably should be some checking of it to guard 
against injection attacks, but since I'm the only one with access to the 
backup server, I didn't put much thought into it.  It does fix the 
problem for now though.

--Jason

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

Reply via email to