Send inn-committers mailing list submissions to
inn-committers@lists.isc.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.isc.org/mailman/listinfo/inn-committers
or, via email, send a message with subject or body 'help' to
inn-committers-requ...@lists.isc.org
You can reach the person managing the list at
inn-committers-ow...@lists.isc.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-committers digest..."
Today's Topics:
1. INN commit: trunk/doc/pod (checklist.pod ckpasswd.pod)
(INN Commit)
2. INN commit: branches/2.5/doc/pod (checklist.pod ckpasswd.pod)
(INN Commit)
----------------------------------------------------------------------
Message: 1
Date: Wed, 12 Jun 2013 11:36:49 -0700 (PDT)
From: INN Commit <r...@isc.org>
To: inn-committ...@isc.org
Subject: INN commit: trunk/doc/pod (checklist.pod ckpasswd.pod)
Message-ID: <20130612183649.ecff567...@hope.eyrie.org>
Date: Wednesday, June 12, 2013 @ 11:36:49
Author: iulius
Revision: 9488
document htpasswd and perl commands to generate the auth newsusers database
Modified:
trunk/doc/pod/checklist.pod
trunk/doc/pod/ckpasswd.pod
---------------+
checklist.pod | 21 +++++++++++++++------
ckpasswd.pod | 22 ++++++++++++++++------
2 files changed, 31 insertions(+), 12 deletions(-)
Modified: checklist.pod
===================================================================
--- checklist.pod 2013-06-08 14:55:08 UTC (rev 9487)
+++ checklist.pod 2013-06-12 18:36:49 UTC (rev 9488)
@@ -283,13 +283,22 @@
default: "<unauthenticated>"
}
-There is a Perl script in the ckpasswd(8) man page if you want to do
-authentications by password and have the appropriate libraries. Copy it
-to I<pathbin>, name the file something like F<makepasswd.pl> and change the
-internal paths to whatever you're using and wherever you're putting the
-newsusers database. The standard Apache B<htpasswd> tool also works
-just fine to create INN password files.
+There is a Perl script in the ckpasswd(8) man page if you want to
+do authentications by password and have the appropriate libraries.
+Copy it to I<pathbin>, name the file something like F<makepasswd.pl> and
+change the internal paths to whatever you're using and wherever you're
+putting the newsusers database. The standard Apache B<htpasswd> tool
+also works just fine to create INN password files, as well as pure Perl.
+For instance, a line for the newsusers database corresponding to the
+user C<user> with the password C<pass> would be C<user:LIfOpbjNaEQYE>
+as obtained by the following commands::
+ % htpasswd -nbd user pass
+ user:LIfOpbjNaEQYE
+
+ % perl -e 'print "user:".crypt("pass", "LI")."\n";'
+ user:LIfOpbjNaEQYE
+
Follow with the access stanzas. Something for people with passwords:
access "generalpeople" {
Modified: ckpasswd.pod
===================================================================
--- ckpasswd.pod 2013-06-08 14:55:08 UTC (rev 9487)
+++ ckpasswd.pod 2013-06-12 18:36:49 UTC (rev 9488)
@@ -84,13 +84,23 @@
username:pdIh9NCNslkq6
(and each line may have an additional colon after the encrypted password
-and additional data; that data will be ignored by B<ckpasswd>). Lines
-starting with a number sign (C<#>) are ignored. INN does not come with a
-utility to create the encrypted passwords, but B<htpasswd> (which comes
-with Apache) can do so and it's a quick job with Perl (see the example
-script under B<-d>). If using Apache's B<htpasswd> program, be sure to
-give it the B<-d> option so that it will use crypt(3).
+and additional data; that data will be ignored by B<ckpasswd>).
+Lines starting with a number sign (C<#>) are ignored. INN does not
+come with a utility to create the encrypted passwords, but B<htpasswd>
+(which comes with Apache) can do so and it's a quick job with Perl
+(see the example script under B<-d>, or also below). If using Apache's
+B<htpasswd> program, be sure to give it the B<-d> option so that it
+will use crypt(3).
+A line in I<filename> for the user C<user> with the password C<pass>
+would be C<user:LIfOpbjNaEQYE> as obtained by the following commands:
+
+ % htpasswd -nbd user pass
+ user:LIfOpbjNaEQYE
+
+ % perl -e 'print "user:".crypt("pass", "LI")."\n";'
+ user:LIfOpbjNaEQYE
+
=item B<-g>
Attempt to look up system group corresponding to username and return a
------------------------------
Message: 2
Date: Wed, 12 Jun 2013 11:37:33 -0700 (PDT)
From: INN Commit <r...@isc.org>
To: inn-committ...@isc.org
Subject: INN commit: branches/2.5/doc/pod (checklist.pod ckpasswd.pod)
Message-ID: <20130612183733.5c8cd67...@hope.eyrie.org>
Date: Wednesday, June 12, 2013 @ 11:37:33
Author: iulius
Revision: 9489
document htpasswd and perl commands to generate the auth newsusers database
Modified:
branches/2.5/doc/pod/checklist.pod
branches/2.5/doc/pod/ckpasswd.pod
---------------+
checklist.pod | 21 +++++++++++++++------
ckpasswd.pod | 22 ++++++++++++++++------
2 files changed, 31 insertions(+), 12 deletions(-)
Modified: checklist.pod
===================================================================
--- checklist.pod 2013-06-12 18:36:49 UTC (rev 9488)
+++ checklist.pod 2013-06-12 18:37:33 UTC (rev 9489)
@@ -283,13 +283,22 @@
default: "<unauthenticated>"
}
-There is a Perl script in the ckpasswd(8) man page if you want to do
-authentications by password and have the appropriate libraries. Copy it
-to I<pathbin>, name the file something like F<makepasswd.pl> and change the
-internal paths to whatever you're using and wherever you're putting the
-newsusers database. The standard Apache B<htpasswd> tool also works
-just fine to create INN password files.
+There is a Perl script in the ckpasswd(8) man page if you want to
+do authentications by password and have the appropriate libraries.
+Copy it to I<pathbin>, name the file something like F<makepasswd.pl> and
+change the internal paths to whatever you're using and wherever you're
+putting the newsusers database. The standard Apache B<htpasswd> tool
+also works just fine to create INN password files, as well as pure Perl.
+For instance, a line for the newsusers database corresponding to the
+user C<user> with the password C<pass> would be C<user:LIfOpbjNaEQYE>
+as obtained by the following commands::
+ % htpasswd -nbd user pass
+ user:LIfOpbjNaEQYE
+
+ % perl -e 'print "user:".crypt("pass", "LI")."\n";'
+ user:LIfOpbjNaEQYE
+
Follow with the access stanzas. Something for people with passwords:
access "generalpeople" {
Modified: ckpasswd.pod
===================================================================
--- ckpasswd.pod 2013-06-12 18:36:49 UTC (rev 9488)
+++ ckpasswd.pod 2013-06-12 18:37:33 UTC (rev 9489)
@@ -84,13 +84,23 @@
username:pdIh9NCNslkq6
(and each line may have an additional colon after the encrypted password
-and additional data; that data will be ignored by B<ckpasswd>). Lines
-starting with a number sign (C<#>) are ignored. INN does not come with a
-utility to create the encrypted passwords, but B<htpasswd> (which comes
-with Apache) can do so and it's a quick job with Perl (see the example
-script under B<-d>). If using Apache's B<htpasswd> program, be sure to
-give it the B<-d> option so that it will use crypt(3).
+and additional data; that data will be ignored by B<ckpasswd>).
+Lines starting with a number sign (C<#>) are ignored. INN does not
+come with a utility to create the encrypted passwords, but B<htpasswd>
+(which comes with Apache) can do so and it's a quick job with Perl
+(see the example script under B<-d>, or also below). If using Apache's
+B<htpasswd> program, be sure to give it the B<-d> option so that it
+will use crypt(3).
+A line in I<filename> for the user C<user> with the password C<pass>
+would be C<user:LIfOpbjNaEQYE> as obtained by the following commands:
+
+ % htpasswd -nbd user pass
+ user:LIfOpbjNaEQYE
+
+ % perl -e 'print "user:".crypt("pass", "LI")."\n";'
+ user:LIfOpbjNaEQYE
+
=item B<-g>
Attempt to look up system group corresponding to username and return a
------------------------------
_______________________________________________
inn-committers mailing list
inn-committers@lists.isc.org
https://lists.isc.org/mailman/listinfo/inn-committers
End of inn-committers Digest, Vol 52, Issue 4
*********************************************
