GPG

 view release on metacpan or  search on metacpan

GPG.html  view on Meta::CPAN

<H1><A NAME="INSTALLATION">INSTALLATION</A></H1>
<P>
<PRE> % perl Makefile.PL
 % make
 % make test
 % make install
</PRE>
<P>
<PRE>  Tips :
  - if you want secure memory, do not forget :
    % chown root /usr/local/bin/gpg ; chmod 4755 /usr/local/bin/gpg
</PRE>
<P>
<HR>
<H1><A NAME="METHODS">METHODS</A></H1>
<P>
Look at the ``test.pl'' and ``quick_test.pl'' for examples and futher
explanations.

<P>
You can set ``VERBOSE'' in ``test.pl'' to ``1'' and restart the test, to

GPG.html  view on Meta::CPAN

<P>
<PRE> Q: How does it work ?
 A: it uses IPC::Open3 to connect the 'gpg' program. 
IPC::Open3 is executing the fork and managing the filehandles for you.
</PRE>
<P>
<PRE>  Q: How secure is GPG ?
  A: As secure as you want... Be carefull. First, GPG is no 
more securer than 'gpg'. 
Second, all passphrases are stored in non-secure memory, unless
you &quot;chown root&quot; and &quot;chmod 4755&quot; your script first. Third, your
script probably store passpharses somewhere on the disk, and 
this is *not* secure.
</PRE>
<P>
<PRE>  Q: Why using GPG, and not GnuPG or GnuPG::Interface ??
  A: Because of their input/output facilities, 
GnuPG.pm only works on filenames. 
GnuPG::Interface works with fileshandles, but is hard to use - all filehandle
management is left up to the user. GPG is working with $scalar only for both
input and output. Since I am developing for a web interface, I don't want to

GPG.pm  view on Meta::CPAN

=head1 INSTALLATION

 % perl Makefile.PL
 % make
 % make test
 % make install

  Tips :
  - if you want secure memory, do not forget :
    % chown root /usr/local/bin/gpg ; chmod 4755 /usr/local/bin/gpg

=head1 METHODS

Look at the "test.pl" and "quick_test.pl" for examples and futher explanations.

You can set "VERBOSE" in "test.pl" to "1"  and restart the test, to see more extensive output.

=over 4

=item I<new %params>

GPG.pm  view on Meta::CPAN

=head1 FAQ

 Q: How does it work ?
 A: it uses IPC::Open3 to connect the 'gpg' program. 
IPC::Open3 is executing the fork and managing the filehandles for you.

  Q: How secure is GPG ?
  A: As secure as you want... Be carefull. First, GPG is no 
more securer than 'gpg'. 
Second, all passphrases are stored in non-secure memory, unless
you "chown root" and "chmod 4755" your script first. Third, your
script probably store passpharses somewhere on the disk, and 
this is *not* secure.

  Q: Why using GPG, and not GnuPG or GnuPG::Interface ??
  A: Because of their input/output facilities, 
GnuPG.pm only works on filenames. 
GnuPG::Interface works with fileshandles, but is hard to use - all filehandle
management is left up to the user. GPG is working with $scalar only for both
input and output. Since I am developing for a web interface, I don't want to
write new files each time I need to communicate with gnupg.

README.txt  view on Meta::CPAN

      my $sigd = $gpg->list_sig();

INSTALLATION
     % perl Makefile.PL
     % make
     % make test
     % make install

      Tips :
      - if you want secure memory, do not forget :
        % chown root /usr/local/bin/gpg ; chmod 4755 /usr/local/bin/gpg

METHODS
    Look at the "test.pl" and "quick_test.pl" for examples and
    futher explanations.

    You can set "VERBOSE" in "test.pl" to "1" and restart the test,
    to see more extensive output.

    *new %params*
         Parameters are :

README.txt  view on Meta::CPAN

FAQ
     Q: How does it work ?
     A: it uses IPC::Open3 to connect the 'gpg' program. 
    IPC::Open3 is executing the fork and managing the filehandles for you.

      Q: How secure is GPG ?
      A: As secure as you want... Be carefull. First, GPG is no 
    more securer than 'gpg'. 
    Second, all passphrases are stored in non-secure memory, unless
    you "chown root" and "chmod 4755" your script first. Third, your
    script probably store passpharses somewhere on the disk, and 
    this is *not* secure.

      Q: Why using GPG, and not GnuPG or GnuPG::Interface ??
      A: Because of their input/output facilities, 
    GnuPG.pm only works on filenames. 
    GnuPG::Interface works with fileshandles, but is hard to use - all filehandle
    management is left up to the user. GPG is working with $scalar only for both
    input and output. Since I am developing for a web interface, I don't want to
    write new files each time I need to communicate with gnupg.