Config-OpenSSH-Authkey
    
    
  
  
  
view release on metacpan or search on metacpan
lib/Config/OpenSSH/Authkey.pm view on Meta::CPAN
Shared systems require caution; foreign keys must not be wiped out.
The easiest method is to include the target C<authorized_keys> file as
one of the sources for valid key material. A comment should be added
into to the C<authorized_keys> file, noting what keys are managed by
the software.
=back
Rotating C<authorized_keys> data is difficult, as the entries contain
no date related metadata like X.509 certificates do. Solutions would be
to schedule a yearly calendar event during which all the keys are
rotated, or maintain the keys in a database that includes a creation
date field on the record.
=head1 CLASS METHODS
=over 4
=item B<new>
Constructor method. Accepts a hash reference containing L</"OPTIONS">
( run in 0.256 second using v1.01-cache-2.11-cpan-5dc5da66d9d )