view release on metacpan or search on metacpan
t/data/generate/control-archive/docknot.yaml view on Meta::CPAN
- name: process-control
title: process-control manual page
- name: update-control
title: update-control manual page
blurb: |
This software generates an INN control.ctl configuration file from
hierarchy configuration fragments, verifies control messages using GnuPG
where possible, processes new control messages to update a newsgroup list,
archives new control messages, and exports the list of newsgroups in a
format suitable for synchronizing the newsgroup list of a Netnews news
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.
t/data/generate/control-archive/output/readme view on Meta::CPAN
<eagle@eyrie.org>. Copyright 2001 Marco d'Itri. Copyright 1996 UUNET
Technologies, Inc.. This software is distributed under a BSD-style
license. Please see the section LICENSE below for more information.
BLURB
This software generates an INN control.ctl configuration file from
hierarchy configuration fragments, verifies control messages using GnuPG
where possible, processes new control messages to update a newsgroup
list, archives new control messages, and exports the list of newsgroups
in a format suitable for synchronizing the newsgroup list of a Netnews
news 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.
t/data/generate/control-archive/output/readme-md view on Meta::CPAN
Copyright 2001 Marco d'Itri. Copyright 1996 UUNET Technologies, Inc..
This software is distributed under a BSD-style license. Please see the
section [License](#license) below for more information.
## Blurb
This software generates an INN control.ctl configuration file from
hierarchy configuration fragments, verifies control messages using GnuPG
where possible, processes new control messages to update a newsgroup list,
archives new control messages, and exports the list of newsgroups in a
format suitable for synchronizing the newsgroup list of a Netnews news
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.
t/data/generate/control-archive/output/thread view on Meta::CPAN
\link[https://git.eyrie.org/?p=usenet/control.archive.git]
[Git repository] \break
]
\h2[Blurb]
This software generates an INN control.ctl configuration file from
hierarchy configuration fragments, verifies control messages using GnuPG
where possible, processes new control messages to update a newsgroup list,
archives new control messages, and exports the list of newsgroups in a
format suitable for synchronizing the newsgroup list of a Netnews news
server. It is the software that maintains the control message and
newsgroup lists available from ftp.isc.org.
\h2[Description]
This package contains three major components:
\bullet[
All of the configuration used to generate a \code[control.ctl] file for
t/data/generate/pam-krb5/docknot.yaml view on Meta::CPAN
putting something like:
```
password sufficient pam_krb5.so minimum_uid=1000
password required pam_unix.so try_first_pass obscure md5
```
in `/etc/pam.d/common-password` will change users' passwords in Kerberos
by default and then only fall back on Unix if that doesn't work. (You
can make this tighter by using the more complex new-style PAM
configuration.) If you instead want to synchronize local and Kerberos
passwords and change them both at the same time, you can do something
like:
```
password required pam_unix.so obscure sha512
password required pam_krb5.so use_authtok minimum_uid=1000
```
If you have multiple environments that you want to synchronize and you
don't want password changes to continue if the Kerberos password change
fails, use the `clear_on_fail` option. For example:
```
password required pam_krb5.so clear_on_fail minimum_uid=1000
password required pam_unix.so use_authtok obscure sha512
password required pam_smbpass.so use_authtok
```
In this case, if `pam_krb5` cannot change the password (due to password
t/data/generate/pam-krb5/output/readme view on Meta::CPAN
If your users should normally all use Kerberos passwords exclusively,
putting something like:
password sufficient pam_krb5.so minimum_uid=1000
password required pam_unix.so try_first_pass obscure md5
in /etc/pam.d/common-password will change users' passwords in Kerberos
by default and then only fall back on Unix if that doesn't work. (You
can make this tighter by using the more complex new-style PAM
configuration.) If you instead want to synchronize local and Kerberos
passwords and change them both at the same time, you can do something
like:
password required pam_unix.so obscure sha512
password required pam_krb5.so use_authtok minimum_uid=1000
If you have multiple environments that you want to synchronize and you
don't want password changes to continue if the Kerberos password change
fails, use the clear_on_fail option. For example:
password required pam_krb5.so clear_on_fail minimum_uid=1000
password required pam_unix.so use_authtok obscure sha512
password required pam_smbpass.so use_authtok
In this case, if pam_krb5 cannot change the password (due to password
strength rules on the KDC, for example), it will clear the stored
password (because of the clear_on_fail option), and since pam_unix and
t/data/generate/pam-krb5/output/readme-md view on Meta::CPAN
putting something like:
```
password sufficient pam_krb5.so minimum_uid=1000
password required pam_unix.so try_first_pass obscure md5
```
in `/etc/pam.d/common-password` will change users' passwords in Kerberos
by default and then only fall back on Unix if that doesn't work. (You can
make this tighter by using the more complex new-style PAM configuration.)
If you instead want to synchronize local and Kerberos passwords and change
them both at the same time, you can do something like:
```
password required pam_unix.so obscure sha512
password required pam_krb5.so use_authtok minimum_uid=1000
```
If you have multiple environments that you want to synchronize and you
don't want password changes to continue if the Kerberos password change
fails, use the `clear_on_fail` option. For example:
```
password required pam_krb5.so clear_on_fail minimum_uid=1000
password required pam_unix.so use_authtok obscure sha512
password required pam_smbpass.so use_authtok
```
In this case, if `pam_krb5` cannot change the password (due to password
t/data/update/control-archive/docknot.yaml view on Meta::CPAN
---
blurb: |
This software generates an INN control.ctl configuration file from
hierarchy configuration fragments, verifies control messages using GnuPG
where possible, processes new control messages to update a newsgroup list,
archives new control messages, and exports the list of newsgroups in a
format suitable for synchronizing the newsgroup list of a Netnews news
server. It is the software that maintains the control message and
newsgroup lists available from ftp.isc.org.
build:
install: false
type: make
copyrights:
- holder: Russ Allbery <eagle@eyrie.org>
years: 2002-2004, 2007-2014, 2016-2018
- holder: Marco d'Itri
years: '2001'
t/data/update/control-archive/old/blurb view on Meta::CPAN
This software generates an INN control.ctl configuration file from
hierarchy configuration fragments, verifies control messages using GnuPG
where possible, processes new control messages to update a newsgroup list,
archives new control messages, and exports the list of newsgroups in a
format suitable for synchronizing the newsgroup list of a Netnews news
server. It is the software that maintains the control message and
newsgroup lists available from ftp.isc.org.
t/data/update/pam-krb5/docknot.yaml view on Meta::CPAN
putting something like:
```
password sufficient pam_krb5.so minimum_uid=1000
password required pam_unix.so try_first_pass obscure md5
```
in `/etc/pam.d/common-password` will change users' passwords in Kerberos
by default and then only fall back on Unix if that doesn't work. (You can
make this tighter by using the more complex new-style PAM configuration.)
If you instead want to synchronize local and Kerberos passwords and change
them both at the same time, you can do something like:
```
password required pam_unix.so obscure sha512
password required pam_krb5.so use_authtok minimum_uid=1000
```
If you have multiple environments that you want to synchronize and you
don't want password changes to continue if the Kerberos password change
fails, use the `clear_on_fail` option. For example:
```
password required pam_krb5.so clear_on_fail minimum_uid=1000
password required pam_unix.so use_authtok obscure sha512
password required pam_smbpass.so use_authtok
```
In this case, if `pam_krb5` cannot change the password (due to password
t/data/update/pam-krb5/old/sections/configuring view on Meta::CPAN
putting something like:
```
password sufficient pam_krb5.so minimum_uid=1000
password required pam_unix.so try_first_pass obscure md5
```
in `/etc/pam.d/common-password` will change users' passwords in Kerberos
by default and then only fall back on Unix if that doesn't work. (You can
make this tighter by using the more complex new-style PAM configuration.)
If you instead want to synchronize local and Kerberos passwords and change
them both at the same time, you can do something like:
```
password required pam_unix.so obscure sha512
password required pam_krb5.so use_authtok minimum_uid=1000
```
If you have multiple environments that you want to synchronize and you
don't want password changes to continue if the Kerberos password change
fails, use the `clear_on_fail` option. For example:
```
password required pam_krb5.so clear_on_fail minimum_uid=1000
password required pam_unix.so use_authtok obscure sha512
password required pam_smbpass.so use_authtok
```
In this case, if `pam_krb5` cannot change the password (due to password