On Tue, 2011-01-04 at 15:19 -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/04/2011 11:54 AM, Matthew Saltzman wrote:
> > On Tue, 2011-01-04 at 11:45 -0500, Daniel J Walsh wrote:
> >> You would need the combination of relabeling the homedir and searching
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/2011 11:54 AM, Matthew Saltzman wrote:
> On Tue, 2011-01-04 at 11:45 -0500, Daniel J Walsh wrote:
>> You would need the combination of relabeling the homedir and searching
>> /var/lib/amanda.
>>
>> WHich is what we will be adding to policy.
>
On Tue, 2011-01-04 at 11:45 -0500, Daniel J Walsh wrote:
> You would need the combination of relabeling the homedir and searching
> /var/lib/amanda.
>
> WHich is what we will be adding to policy.
Ah, I don't think that was in your earlier message. If the policy is
published someplace, I'd be ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/2011 11:33 AM, Matthew Saltzman wrote:
> On Tue, 2011-01-04 at 09:11 -0500, Daniel J Walsh wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 01/04/2011 04:08 AM, Gordon Messmer wrote:
>>> On 01/02/2011 06:45 AM, Matthew Salt
On Tue, 2011-01-04 at 09:11 -0500, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 01/04/2011 04:08 AM, Gordon Messmer wrote:
> > On 01/02/2011 06:45 AM, Matthew Saltzman wrote:
> >> Aha! In /var/log/messages, on the other hand, this happens:
> >>
> >> Jan
On 01/04/2011 06:11 AM, Daniel J Walsh wrote:
> On 01/04/2011 04:08 AM, Gordon Messmer wrote:
>> # semanage fcontext -a -t user_home_dir_t /var/lib/amanda
>> # semanage fcontext -a -t user_home_t "/var/lib/amanda/.*"
>> # restorecon -r /var/lib/amanda
> No This would probably cause amanda to break
On Tue, 2011-01-04 at 01:08 -0800, Gordon Messmer wrote:
> On 01/02/2011 06:45 AM, Matthew Saltzman wrote: > Aha! In
> /var/log/messages, on the other hand, this happens: > > Jan 2
> 09:40:36 yankee setroubleshoot: SELinux is preventing /usr/sbin/sshd
> from search access on the director
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/04/2011 04:08 AM, Gordon Messmer wrote:
> On 01/02/2011 06:45 AM, Matthew Saltzman wrote:
>> Aha! In /var/log/messages, on the other hand, this happens:
>>
>> Jan 2 09:40:36 yankee setroubleshoot: SELinux is preventing
>> /usr/sbin/ssh
On 01/02/2011 06:45 AM, Matthew Saltzman wrote:
> Aha! In /var/log/messages, on the other hand, this happens:
>
> Jan 2 09:40:36 yankee setroubleshoot: SELinux is preventing
> /usr/sbin/sshd from search access on the directory /var/lib/amanda. For
> complete SELinux messages. run sealer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01/02/2011 11:43 AM, Matthew Saltzman wrote:
> On Sun, 2011-01-02 at 10:09 +0100, François Patte wrote:
> Le 02/01/2011 02:14, Matthew Saltzman a crit :
I'm trying to set up amanda using the amaddclient command. That
requires that user a
On Sun, 2011-01-02 at 10:09 +0100, François Patte wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Le 02/01/2011 02:14, Matthew Saltzman a crit :
> > I'm trying to set up amanda using the amaddclient command. That
> > requires that user amandabackup be able to log into the client mac
On Sun, 2011-01-02 at 09:45 -0500, Matthew Saltzman wrote:
> On Sun, 2011-01-02 at 00:14 -0800, Gordon Messmer wrote:
> > On 01/01/2011 05:14 PM, Matthew Saltzman wrote:
> > >
> > > ssh with keys by a normal user works fine. No error messages to be
> > > found in /var/log/secure on the client or
On Sun, 2011-01-02 at 00:14 -0800, Gordon Messmer wrote:
> On 01/01/2011 05:14 PM, Matthew Saltzman wrote:
> >
> > ssh with keys by a normal user works fine. No error messages to be
> > found in /var/log/secure on the client or with ssh -v on the server.
>
> Does the output from "ssh -v" indicat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 02/01/2011 02:14, Matthew Saltzman a écrit :
> I'm trying to set up amanda using the amaddclient command. That
> requires that user amandabackup be able to log into the client machine
> using ssh keys.
>
> I've generated the keys on the server mac
On 01/01/2011 05:14 PM, Matthew Saltzman wrote:
>
> ssh with keys by a normal user works fine. No error messages to be
> found in /var/log/secure on the client or with ssh -v on the server.
Does the output from "ssh -v" indicate that the correct key file is
being offered?
--
users mailing list
15 matches
Mail list logo