sean darcy <seandarcy2@xxxxxxxxx> writes: > On 06/12/2010 09:34 AM, Wolfgang S. Rupprecht wrote: >> >> Craig White<craigwhite@xxxxxxxxxxx> writes: >>> sounds like you created the file elsewhere (or even on another computer) >>> and moved it into place thereby creating SELinux issue. >> >> That would be my guess too, seeing how it happens to me regularly when I >> do clean installs and then try to copy the customized files from an NFS >> server. It is a real pain in the neck that a cp(1) from an NFS-ed >> fileystem doesn't preserve the selinux bits. >> >> -wolfgang > > I did copy id_rsa.pub to the new machine. Then cat id_rsa.pub >> > authorized_keys > > Is there another/better way to do it? In the past I just copied as normal and then ran "restorecon -v <filename>" to set the selinux context. Just recently I've been trying to just sync the important files across my machines via "rsync -axHAX <filename_or_dirname>". I norrmally try to have only one authorized_keys file per user account that I distribute to all machines. It makes life much simpler that way. -wolfgang -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
