App-DocKnot
view release on metacpan or search on metacpan
t/data/generate/control-archive/docknot.yaml view on Meta::CPAN
server. It is the software that maintains the control message and
newsgroup lists available from ftp.isc.org.
description: |
This package contains three major components:
* All of the configuration used to generate a `control.ctl` file for INN
and the `PGPKEYS` and `README.html` files distributed with pgpcontrol,
along with the script to generate those files.
* Software to process control messages, verify them against that
authorization information, and maintain a control message archive and
list of active newsgroups. Software is also included to generate
reports of recent changes to the list of active newsgroups.
* The documentation files included in the control message archive and
newsgroup lists on ftp.isc.org.
Manual changes to the canonical newsgroup list are supported in a way that
generates the same log messages and uses the same locking structure so
that they can co-exist with automated changes and be included in the same
t/data/generate/control-archive/output/readme view on Meta::CPAN
newsgroup lists available from ftp.isc.org.
DESCRIPTION
This package contains three major components:
* All of the configuration used to generate a control.ctl file for INN
and the PGPKEYS and README.html files distributed with pgpcontrol,
along with the script to generate those files.
* Software to process control messages, verify them against that
authorization information, and maintain a control message archive and
list of active newsgroups. Software is also included to generate
reports of recent changes to the list of active newsgroups.
* The documentation files included in the control message archive and
newsgroup lists on ftp.isc.org.
Manual changes to the canonical newsgroup list are supported in a way
that generates the same log messages and uses the same locking structure
so that they can co-exist with automated changes and be included in the
t/data/generate/control-archive/output/readme-md view on Meta::CPAN
newsgroup lists available from ftp.isc.org.
## Description
This package contains three major components:
* All of the configuration used to generate a `control.ctl` file for INN
and the `PGPKEYS` and `README.html` files distributed with pgpcontrol,
along with the script to generate those files.
* Software to process control messages, verify them against that
authorization information, and maintain a control message archive and
list of active newsgroups. Software is also included to generate
reports of recent changes to the list of active newsgroups.
* The documentation files included in the control message archive and
newsgroup lists on ftp.isc.org.
Manual changes to the canonical newsgroup list are supported in a way that
generates the same log messages and uses the same locking structure so
that they can co-exist with automated changes and be included in the same
t/data/generate/control-archive/output/thread view on Meta::CPAN
\bullet[
All of the configuration used to generate a \code[control.ctl] file for
INN and the \code[PGPKEYS] and \code[README.html] files distributed with
pgpcontrol, along with the script to generate those files.
]
\bullet[
Software to process control messages, verify them against that
authorization information, and maintain a control message archive and
list of active newsgroups. Software is also included to generate
reports of recent changes to the list of active newsgroups.
]
\bullet[
The documentation files included in the control message archive and
newsgroup lists on ftp.isc.org.
t/data/generate/pam-krb5/docknot.yaml view on Meta::CPAN
PAM environment between the calls to `pam_authenticate` and
`pam_setcred`. Most do, but OpenSSH notoriously does not and calls
`pam_authenticate` in a subprocess, so this method is used to pass the
tickets to the `pam_setcred` call in a different process.
`pam_authenticate` does a complete authentication, including checking
the resulting TGT by obtaining a service ticket for the local host if
possible, but this requires read access to the system keytab. If the
keytab doesn't exist, can't be read, or doesn't include the appropriate
credentials, the default is to accept the authentication. This can be
controlled by setting `verify_ap_req_nofail` to true in `[libdefaults]`
in `/etc/krb5.conf`. `pam_authenticate` also does a basic authorization
check, by default calling `krb5_kuserok` (which uses `~/.k5login` if
available and falls back to checking that the principal corresponds to
the account name). This can be customized with several options
documented in the pam_krb5(5) man page.
pam-krb5 treats `pam_open_session` and `pam_setcred(PAM_ESTABLISH_CRED)`
as synonymous, as some applications call one and some call the other.
Both copy the initial credentials from the temporary cache into a
permanent cache for this session and set `KRB5CCNAME` in the
t/data/generate/pam-krb5/output/readme view on Meta::CPAN
environment between the calls to pam_authenticate and pam_setcred. Most
do, but OpenSSH notoriously does not and calls pam_authenticate in a
subprocess, so this method is used to pass the tickets to the
pam_setcred call in a different process.
pam_authenticate does a complete authentication, including checking the
resulting TGT by obtaining a service ticket for the local host if
possible, but this requires read access to the system keytab. If the
keytab doesn't exist, can't be read, or doesn't include the appropriate
credentials, the default is to accept the authentication. This can be
controlled by setting verify_ap_req_nofail to true in [libdefaults] in
/etc/krb5.conf. pam_authenticate also does a basic authorization check,
by default calling krb5_kuserok (which uses ~/.k5login if available and
falls back to checking that the principal corresponds to the account
name). This can be customized with several options documented in the
pam_krb5(5) man page.
pam-krb5 treats pam_open_session and pam_setcred(PAM_ESTABLISH_CRED) as
synonymous, as some applications call one and some call the other. Both
copy the initial credentials from the temporary cache into a permanent
cache for this session and set KRB5CCNAME in the environment. It will
t/data/generate/pam-krb5/output/readme-md view on Meta::CPAN
environment between the calls to `pam_authenticate` and `pam_setcred`.
Most do, but OpenSSH notoriously does not and calls `pam_authenticate` in
a subprocess, so this method is used to pass the tickets to the
`pam_setcred` call in a different process.
`pam_authenticate` does a complete authentication, including checking the
resulting TGT by obtaining a service ticket for the local host if
possible, but this requires read access to the system keytab. If the
keytab doesn't exist, can't be read, or doesn't include the appropriate
credentials, the default is to accept the authentication. This can be
controlled by setting `verify_ap_req_nofail` to true in `[libdefaults]` in
`/etc/krb5.conf`. `pam_authenticate` also does a basic authorization
check, by default calling `krb5_kuserok` (which uses `~/.k5login` if
available and falls back to checking that the principal corresponds to the
account name). This can be customized with several options documented in
the pam_krb5(5) man page.
pam-krb5 treats `pam_open_session` and `pam_setcred(PAM_ESTABLISH_CRED)`
as synonymous, as some applications call one and some call the other.
Both copy the initial credentials from the temporary cache into a
permanent cache for this session and set `KRB5CCNAME` in the environment.
t/data/generate/pgp-sign/docknot.yaml view on Meta::CPAN
format: v1
name: PGP::Sign
maintainer: Russ Allbery <rra@cpan.org>
version: '1.00'
synopsis: create and verify detached PGP signatures
license:
name: Perl
copyrights:
- holder: Russ Allbery <rra@cpan.org>
years: 1997-2000, 2002, 2004, 2018, 2020
build:
type: Module::Build
distribution:
t/data/generate/pgp-sign/docknot.yaml view on Meta::CPAN
Thou canst not then be false to any man.
work: Hamlet
docs:
user:
- name: docs
title: Module documentation
- name: thanks
title: Thanks and credits
blurb: |
PGP::Sign is a Perl module for generating and verifying detached OpenPGP
signatures of textual data using GnuPG. It was written to support Netnews
article signatures for signed control messages and PGPMoose.
description: |
PGP::Sign is a Perl module that can generate and verify OpenPGP signatures
on some data. Currently, only textual data (data that can be processed
using GnuPG's `--textmode` option) is supported. It uses GnuPG under the
hood to do the work.
The original purpose of this module was to factor out common code in a
News::Article class written by Andrew Gierth that handled PGPMoose and
control message signatures. It is used to verify control message
signatures for the ftp.isc.org Netnews metadata archive, and to generate
signed control messages for the Big Eight Usenet hierarchies.
Data to be signed or verified can be passed into PGP::Sign in a wide
variety of formats: scalars, arrays, open files, even code references that
act as generators. Keys with passphrases are supported and the passphrase
is passed to GnuPG securely (although getting the passphrase to the
PGP::Sign module is a problem for the calling application).
This module supports both GnuPG v2 and GnuPG v1 and, when used with GnuPG
v1, supports using OpenPGP keys and generating and verifying signatures
that are backward-compatible with PGP 2.6.2.
PGP::Sign provides both a (recommended) object-oriented API and a (legacy)
function-based API that uses global variables for configuration and is
backward-compatible with earlier versions of PGP::Sign.
requirements: |
Perl 5.20 or later and Module::Build are required to build this module,
and IPC::Run is required to use it. Either GnuPG v2 or GnuPG v1
(selectable at runtime) is also required. It has not been tested with
t/data/generate/pgp-sign/output/readme view on Meta::CPAN
PGP::Sign 1.00
(create and verify detached PGP signatures)
Maintained by Russ Allbery <rra@cpan.org>
Copyright 1997-2000, 2002, 2004, 2018, 2020 Russ Allbery <rra@cpan.org>.
This software is distributed under the same terms as Perl itself.
Please see the section LICENSE below for more information.
BLURB
PGP::Sign is a Perl module for generating and verifying detached OpenPGP
signatures of textual data using GnuPG. It was written to support
Netnews article signatures for signed control messages and PGPMoose.
DESCRIPTION
PGP::Sign is a Perl module that can generate and verify OpenPGP
signatures on some data. Currently, only textual data (data that can be
processed using GnuPG's --textmode option) is supported. It uses GnuPG
under the hood to do the work.
The original purpose of this module was to factor out common code in a
News::Article class written by Andrew Gierth that handled PGPMoose and
control message signatures. It is used to verify control message
signatures for the ftp.isc.org Netnews metadata archive, and to generate
signed control messages for the Big Eight Usenet hierarchies.
Data to be signed or verified can be passed into PGP::Sign in a wide
variety of formats: scalars, arrays, open files, even code references
that act as generators. Keys with passphrases are supported and the
passphrase is passed to GnuPG securely (although getting the passphrase
to the PGP::Sign module is a problem for the calling application).
This module supports both GnuPG v2 and GnuPG v1 and, when used with
GnuPG v1, supports using OpenPGP keys and generating and verifying
signatures that are backward-compatible with PGP 2.6.2.
PGP::Sign provides both a (recommended) object-oriented API and a
(legacy) function-based API that uses global variables for configuration
and is backward-compatible with earlier versions of PGP::Sign.
REQUIREMENTS
Perl 5.20 or later and Module::Build are required to build this module,
and IPC::Run is required to use it. Either GnuPG v2 or GnuPG v1
t/data/generate/pgp-sign/output/readme-md view on Meta::CPAN
[](https://github.com/rra/pgp-sign/blob/master/LICENSE)
[](https://tracker.debian.org/pkg/libpgp-sign-perl)
Copyright 1997-2000, 2002, 2004, 2018, 2020 Russ Allbery <rra@cpan.org>.
This software is distributed under the same terms as Perl itself. Please
see the section [License](#license) below for more information.
## Blurb
PGP::Sign is a Perl module for generating and verifying detached OpenPGP
signatures of textual data using GnuPG. It was written to support Netnews
article signatures for signed control messages and PGPMoose.
## Description
PGP::Sign is a Perl module that can generate and verify OpenPGP signatures
on some data. Currently, only textual data (data that can be processed
using GnuPG's `--textmode` option) is supported. It uses GnuPG under the
hood to do the work.
The original purpose of this module was to factor out common code in a
News::Article class written by Andrew Gierth that handled PGPMoose and
control message signatures. It is used to verify control message
signatures for the ftp.isc.org Netnews metadata archive, and to generate
signed control messages for the Big Eight Usenet hierarchies.
Data to be signed or verified can be passed into PGP::Sign in a wide
variety of formats: scalars, arrays, open files, even code references that
act as generators. Keys with passphrases are supported and the passphrase
is passed to GnuPG securely (although getting the passphrase to the
PGP::Sign module is a problem for the calling application).
This module supports both GnuPG v2 and GnuPG v1 and, when used with GnuPG
v1, supports using OpenPGP keys and generating and verifying signatures
that are backward-compatible with PGP 2.6.2.
PGP::Sign provides both a (recommended) object-oriented API and a (legacy)
function-based API that uses global variables for configuration and is
backward-compatible with earlier versions of PGP::Sign.
## Requirements
Perl 5.20 or later and Module::Build are required to build this module,
and IPC::Run is required to use it. Either GnuPG v2 or GnuPG v1
t/data/generate/pgp-sign/output/thread view on Meta::CPAN
\link[https://git.eyrie.org/?p=perl/pgp-sign.git]
[Git repository] \break
\link[https://metacpan.org/release/PGP-Sign]
[MetaCPAN] \break
\link[https://tracker.debian.org/pkg/libpgp-sign-perl]
[Debian package tracker] \break
]
\h2[Blurb]
PGP::Sign is a Perl module for generating and verifying detached OpenPGP
signatures of textual data using GnuPG. It was written to support Netnews
article signatures for signed control messages and PGPMoose.
\h2[Description]
PGP::Sign is a Perl module that can generate and verify OpenPGP signatures
on some data. Currently, only textual data (data that can be processed
using GnuPG's \code[--textmode] option) is supported. It uses GnuPG under
the hood to do the work.
The original purpose of this module was to factor out common code in a
News::Article class written by Andrew Gierth that handled PGPMoose and
control message signatures. It is used to verify control message
signatures for the ftp.isc.org Netnews metadata archive, and to generate
signed control messages for the Big Eight Usenet hierarchies.
Data to be signed or verified can be passed into PGP::Sign in a wide
variety of formats: scalars, arrays, open files, even code references that
act as generators. Keys with passphrases are supported and the passphrase
is passed to GnuPG securely (although getting the passphrase to the
PGP::Sign module is a problem for the calling application).
This module supports both GnuPG v2 and GnuPG v1 and, when used with GnuPG
v1, supports using OpenPGP keys and generating and verifying signatures
that are backward-compatible with PGP 2.6.2.
PGP::Sign provides both a (recommended) object-oriented API and a (legacy)
function-based API that uses global variables for configuration and is
backward-compatible with earlier versions of PGP::Sign.
\h2[Requirements]
Perl 5.20 or later and Module::Build are required to build this module,
and IPC::Run is required to use it. Either GnuPG v2 or GnuPG v1
t/data/spin/input/software/index.th view on Meta::CPAN
[Remind of possibly periodic tasks via e-mail]
]
\section[mail][Mail][
\package[mdfrm/][mdfrm]
[Summarize the content of a maildir like frm]
]
\section[perl][Perl Modules][
\package[pgp-sign/][PGP::Sign]
[Generate and/or verify detached PGP signatures]
\package[podlators/][podlators]
[Pod::Man and Pod::Text POD formatting modules]
\package[ansicolor/][Term::ANSIColor]
[Easy interface for ANSI color escape sequences]
\package[shadowhash/][Tie::ShadowHash]
[Overlay multiple hashes to form a single logical hash]
]
\section[devel][Software Development][
\package[c-tap-harness/][C TAP Harness]
t/data/spin/input/usefor/index.th view on Meta::CPAN
including certain key headers so that the resulting signature can
be used to check several key header fields and the newsgroups to which
the article was posted. This protocol is used primarily to validate
approvals to moderated groups.
This document is the original README by Greg Rose that accompanied the
reference implementation of PGP Moose. The canonical version is on
\link[http://seer-grog.net/][Greg Rose's web site].
]
\desc[\link[other/pgpverify][Signing Control Messages (pgpverify)]][
The pgpverify protocol is another protocol for signing a Usenet
article that includes a different set of metadata and header fields
than the PGP Moose protocol. It's used primarily (and very widely) to
authenticate control messages.
This document is the FORMAT document for the pgpcontrol software. The
canonical version is in the
\link[ftp://ftp.isc.org/pub/pgpcontrol/FORMAT][pgpcontrol distribution
site].
]
t/data/spin/output/software/index.html view on Meta::CPAN
<table class="software">
<tr>
<td class="package"><strong><a href="mdfrm/">mdfrm</a></strong></td>
<td>Summarize the content of a maildir like frm</td>
</tr></table>
<h2 id="perl"><a name="perl">Perl Modules</a></h2>
<table class="software">
<tr>
<td class="package"><strong><a href="pgp-sign/">PGP::Sign</a></strong></td>
<td>Generate and/or verify detached PGP signatures</td>
</tr>
<tr>
<td class="package"><strong><a href="podlators/">podlators</a></strong></td>
<td>Pod::Man and Pod::Text POD formatting modules</td>
</tr>
<tr>
<td class="package"><strong><a href="ansicolor/">Term::ANSIColor</a></strong></td>
<td>Easy interface for ANSI color escape sequences</td>
t/data/spin/output/usefor/index.html view on Meta::CPAN
the article was posted. This protocol is used primarily to validate
approvals to moderated groups.
</p>
<p>
This document is the original README by Greg Rose that accompanied the
reference implementation of PGP Moose. The canonical version is on
<a href="http://seer-grog.net/">Greg Rose's web site</a>.
</p></dd>
<dt><a href="other/pgpverify">Signing Control Messages (pgpverify)</a></dt>
<dd><p>
The pgpverify protocol is another protocol for signing a Usenet
article that includes a different set of metadata and header fields
than the PGP Moose protocol. It's used primarily (and very widely) to
authenticate control messages.
</p>
<p>
This document is the FORMAT document for the pgpcontrol software. The
canonical version is in the
<a href="ftp://ftp.isc.org/pub/pgpcontrol/FORMAT">pgpcontrol distribution
site</a>.
t/data/update/control-archive/docknot.yaml view on Meta::CPAN
years: '2001'
- holder: UUNET Technologies, Inc.
years: '1996'
description: |
This package contains three major components:
* All of the configuration used to generate a `control.ctl` file for INN
and the `PGPKEYS` and `README.html` files distributed with pgpcontrol,
along with the script to generate those files.
* Software to process control messages, verify them against that
authorization information, and maintain a control message archive and
list of active newsgroups. Software is also included to generate
reports of recent changes to the list of active newsgroups.
* The documentation files included in the control message archive and
newsgroup lists on ftp.isc.org.
Manual changes to the canonical newsgroup list are supported in a way that
generates the same log messages and uses the same locking structure so
that they can co-exist with automated changes and be included in the same
t/data/update/control-archive/old/description view on Meta::CPAN
This package contains three major components:
* All of the configuration used to generate a `control.ctl` file for INN
and the `PGPKEYS` and `README.html` files distributed with pgpcontrol,
along with the script to generate those files.
* Software to process control messages, verify them against that
authorization information, and maintain a control message archive and
list of active newsgroups. Software is also included to generate
reports of recent changes to the list of active newsgroups.
* The documentation files included in the control message archive and
newsgroup lists on ftp.isc.org.
Manual changes to the canonical newsgroup list are supported in a way that
generates the same log messages and uses the same locking structure so
that they can co-exist with automated changes and be included in the same
t/data/update/pam-krb5/docknot.yaml view on Meta::CPAN
environment between the calls to `pam_authenticate` and `pam_setcred`.
Most do, but OpenSSH notoriously does not and calls `pam_authenticate` in
a subprocess, so this method is used to pass the tickets to the
`pam_setcred` call in a different process.
`pam_authenticate` does a complete authentication, including checking the
resulting TGT by obtaining a service ticket for the local host if
possible, but this requires read access to the system keytab. If the
keytab doesn't exist, can't be read, or doesn't include the appropriate
credentials, the default is to accept the authentication. This can be
controlled by setting `verify_ap_req_nofail` to true in `[libdefaults]` in
`/etc/krb5.conf`. `pam_authenticate` also does a basic authorization
check, by default calling `krb5_kuserok` (which uses `~/.k5login` if
available and falls back to checking that the principal corresponds to the
account name). This can be customized with several options documented in
the pam_krb5(5) man page.
pam-krb5 treats `pam_open_session` and `pam_setcred(PAM_ESTABLISH_CRED)`
as synonymous, as some applications call one and some call the other.
Both copy the initial credentials from the temporary cache into a
permanent cache for this session and set `KRB5CCNAME` in the environment.
t/data/update/pam-krb5/old/sections/implementation-notes view on Meta::CPAN
environment between the calls to `pam_authenticate` and `pam_setcred`.
Most do, but OpenSSH notoriously does not and calls `pam_authenticate` in
a subprocess, so this method is used to pass the tickets to the
`pam_setcred` call in a different process.
`pam_authenticate` does a complete authentication, including checking the
resulting TGT by obtaining a service ticket for the local host if
possible, but this requires read access to the system keytab. If the
keytab doesn't exist, can't be read, or doesn't include the appropriate
credentials, the default is to accept the authentication. This can be
controlled by setting `verify_ap_req_nofail` to true in `[libdefaults]` in
`/etc/krb5.conf`. `pam_authenticate` also does a basic authorization
check, by default calling `krb5_kuserok` (which uses `~/.k5login` if
available and falls back to checking that the principal corresponds to the
account name). This can be customized with several options documented in
the pam_krb5(5) man page.
pam-krb5 treats `pam_open_session` and `pam_setcred(PAM_ESTABLISH_CRED)`
as synonymous, as some applications call one and some call the other.
Both copy the initial credentials from the temporary cache into a
permanent cache for this session and set `KRB5CCNAME` in the environment.
( run in 3.750 seconds using v1.01-cache-2.11-cpan-13bb782fe5a )