[pkg-opensc-commit] [pam-p11] 08/66: remove generated html documentation from svn.
Eric Dorland
eric at moszumanska.debian.org
Tue Jun 13 04:06:48 UTC 2017
This is an automated email from the git hooks/post-receive script.
eric pushed a commit to branch master
in repository pam-p11.
commit afab4b1d84ce8d99f3ef05c23623028aed7b92d8
Author: Andreas Jellinghaus <andreas at ionisiert.de>
Date: Thu Sep 1 15:53:10 2005 +0000
remove generated html documentation from svn.
---
doc/MailingLists.html | 45 -----------------
doc/OperatingSystems.html | 11 -----
doc/QuickStart.html | 122 ----------------------------------------------
doc/ResourcesLinks.html | 26 ----------
doc/index.html | 59 ----------------------
5 files changed, 263 deletions(-)
diff --git a/doc/MailingLists.html b/doc/MailingLists.html
deleted file mode 100644
index 53e78cd..0000000
--- a/doc/MailingLists.html
+++ /dev/null
@@ -1,45 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:html="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>MailingLists - simple pam module based on libp11 - Trac</title><style type="text/css">
- @import url(trac.css);
- </style></head><body><div class="wikipage">
- <div id="searchable"><h1>Mailing lists</h1>
-<ul><li>opensc-annouce - Announcements of new releases, bugfixes and security warnings
-</li><li>opensc-devel - Discussion of developement issues for OpenSC, OpenCT and SCB
-</li><li>opensc-user - Discussion of end-user questions for OpenSC, OpenCT and SCB
-</li><li>opensc-commits - commit notifications for all projects hosted at opensc.org
-</li></ul><p>
-To subscribe, unsubscribe or browse the archive, please visit
-our <a class="ext-link" title="http://www.opensc.org/cgi-bin/mailman/listinfo" href="http://www.opensc.org/cgi-bin/mailman/listinfo" shape="rect">mailing list manager</a>.
-</p>
-<p>
-Please:
-</p>
-<ul><li>Post to one of these mailing list.
-</li><li>Do not post to several lists, one is enough, we read all of them.
-</li><li>Do not send carbon copies to the developers. We read all postings on the mailing list.
-</li><li>Do not mail developers directly, we read all the mailing lists and the bugs address.
-</li></ul><p>
-Direct email is more work for us. Also see
-<a class="ext-link" title="http://www.eyrie.org/~eagle/faqs/questions.html" href="http://www.eyrie.org/~eagle/faqs/questions.html" shape="rect">this faq</a> for explanations why.
-</p>
-<p>
-If you are subscribed to the mailing list, your posting will be distributed
-immideatly. If you are not subscribed, it will be put on hold, till someone has
-reviewed it so we can filter spam. We usualy review postings at least once a day,
-so be patient. You can also cancel the posting, subscribe to the mailing list
-and post again.
-</p>
-<h2>Bug reports</h2>
-<p>
-Please file bug reports using the <a class="ext-link" title="http://www.opensc.org/libp11/newticket" href="http://www.opensc.org/libp11/newticket" shape="rect">new ticket</a> link.
-You can also send bug reports to bugs at opensc.org via email.
-</p>
-<h2>Greylisting</h2>
-<p>
-The opensc.org and lists.opensc.org mail servers are protected from spam by using a mechanism
-called greylisting. Usualy this only causes a short delay for the first mail we receive from
-you, and no trouble at all. Still if for whatever reason you cannot send mail to opensc.org,
-please contact Andreas Jellinghaus at aj at dungeon.inka.de. Thanks.
-</p>
-</div>
- </div><div class="footer"><hr></hr><p><a href="index.html">Back to Index</a></p></div></body></html>
diff --git a/doc/OperatingSystems.html b/doc/OperatingSystems.html
deleted file mode 100644
index 78aade6..0000000
--- a/doc/OperatingSystems.html
+++ /dev/null
@@ -1,11 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:html="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>OperatingSystems - simple pam module based on libp11 - Trac</title><style type="text/css">
- @import url(trac.css);
- </style></head><body><div class="wikipage">
- <div id="searchable"><h1>Operating Systems</h1>
-<p>
-Libp11 is still under development, once it works we will add each operating system here.
-So far libp11 is not part of any linux distribution.
-</p>
-</div>
- </div><div class="footer"><hr></hr><p><a href="index.html">Back to Index</a></p></div></body></html>
diff --git a/doc/QuickStart.html b/doc/QuickStart.html
deleted file mode 100644
index 18b0d65..0000000
--- a/doc/QuickStart.html
+++ /dev/null
@@ -1,122 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:html="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>QuickStart - simple pam module based on libp11 - Trac</title><style type="text/css">
- @import url(trac.css);
- </style></head><body><div class="wikipage">
- <div id="searchable"><h1>Installing pam_p11</h1>
-<p>
-Installation is quite easy:
-</p>
-<pre class="wiki" xml:space="preserve">wget http://www.opensc.org/files/pam_p11-0.1.tar.gz
-tar xfvz pam_p11-0.1.tar.gz
-cd pam_p11-0.1
-./configure --prefix=/usr --libdir=/lib/
-make
-make install
-</pre><p>
-is all you need. Pam_p11 depends on pkg-config, openssl, libp11 and pam.
-If you don't have pkg-config installed, please do so and try again.
-If pkg-config is not found, please change your PATH environment setting.
-If openssl is not installed, please do so. If openssl is not found, please
-change your PKG_CONFIG_PATH environment setting to include the directory
-with "openssl.pc" or "libp11.pc" file. Some linux distributions split
-openssl into a runtime package and a development package, you need to
-install both. Same might be true for pam and libp11.
-</p>
-<h1>Using pam_p11_opensc</h1>
-<p>
-To use pam_p11_opensc with some application like login, edit /etc/pam.d/login
-and replace
-</p>
-<pre class="wiki" xml:space="preserve">auth required pam_unix.so nullok
-</pre><p>
-with
-</p>
-<pre class="wiki" xml:space="preserve">auth required pam_p11_opensc.so /usr/lib/opensc-pkcs11.so
-</pre><p>
-Replace <tt>/usr/lib/opensc-pkcs11.so</tt> with your PKCS#11 implementation.
-</p>
-<p>
-Also while testing it is best to keep a door open, i.e. allow also
-login via passwords. To try pam_p11_opensc first and then password put
-into your pam configuration:
-</p>
-<pre class="wiki" xml:space="preserve">auth sufficient pam_p11_opensc.so /usr/lib/opensc-pkcs11.so
-auth required pam_unix.so nullok
-</pre><p>
-Also each user needs to create a <tt>~/.eid/</tt> directory and create
-a file <tt>~/.eid/authorized_certificates</tt>. You can do that via
-</p>
-<pre class="wiki" xml:space="preserve">mkdir ~/.eid
-chmod 0755 ~/.eid
-pkcs15-tool -r 45 > ~/.eid/authorized_certificates
-chmod 0644 ~/.eid/authorized_certificates
-</pre><p>
-This example uses the "pkcs15-tool" command from opensc to read the
-default user certificate (id 45) from the smart card in reader 0.
-</p>
-<p>
-It is very important that only the user of the file can write to it.
-You can have any number of certificates in that file. The certificates
-need to be in "pem" format. "der" format is currently not supported.
-</p>
-<p>
-Pam_p11_opensc is the successor of the OpenSC pam_opensc module (eid mode).
-It is 100% compatible, but has fewer bugs. Using pam_opensc is discouraged.
-</p>
-<h1>Using pam_p11_openssh</h1>
-<p>
-To use pam_p11_openssh with some application like login, edit /etc/pam.d/login
-and replace
-</p>
-<pre class="wiki" xml:space="preserve">auth required pam_unix.so nullok
-</pre><p>
-with
-</p>
-<pre class="wiki" xml:space="preserve">auth required pam_p11_openssh.so /usr/lib/opensc-pkcs11.so
-</pre><p>
-Replace <tt>/usr/lib/opensc-pkcs11.so</tt> with your PKCS#11 implementation.
-</p>
-<p>
-Also while testing it is best to keep a door open, i.e. allow also
-login via passwords. To try pam_p11_opensc first and then password put
-into your pam configuration:
-</p>
-<pre class="wiki" xml:space="preserve">auth sufficient pam_p11_openssh.so /usr/lib/opensc-pkcs11.so
-auth required pam_unix.so nullok
-</pre><p>
-Also each user needs to create a <tt>~/.ssh/</tt> directory and create
-a file <tt>~/.ssh/authorized_keys</tt>. You can do that via
-</p>
-<pre class="wiki" xml:space="preserve">mkdir ~/.ssh
-chmod 0755 ~/.ssh
-ssh-keygen -D 0 > ~/.ssh/authorized_keys
-chmod 0644 ~/.ssh/authorized_keys
-</pre><p>
-This example uses the "ssh-keygen" command from openssh to read the
-default user public key (id 45) from the smart card in reader 0.
-Note that this tool prints the public keys in two formats: ssh v1 and
-ssh v2 format. It is recommended to edit the file and delete one of
-those two lines. Also you might want to add a comment / identifier
-at the end of the line.
-</p>
-<p>
-It is very important that only the user of the file can write to it.
-You can have any number of public keys in that file.
-</p>
-<p>
-Note it is currently not possible to convert existing ssh keys into
-pem format and store them on a smart card. (To be precize: OpenSC
-has no such functionality, not sure about other implementations.)
-</p>
-<h2>Security Note</h2>
-<p>
-Both pam_p11 modules are plain, they simple compare rsa public keys
-and request the cryptographic token to sign some random data and
-verifiy the signature with the public key. No CA chain checking is done,
-no CRL is looked at, and they don't know what OCSP is. This works fine
-for small installations, but if you want any of those features, please
-have a look at <a class="ext-link" title="http://www.opensc.org/pam_pkcs11" href="http://www.opensc.org/pam_pkcs11" shape="rect">Pam_pkcs11</a> for a fully
-fledged pam module for smart card authentication.
-</p>
-</div>
- </div><div class="footer"><hr></hr><p><a href="index.html">Back to Index</a></p></div></body></html>
diff --git a/doc/ResourcesLinks.html b/doc/ResourcesLinks.html
deleted file mode 100644
index 3564679..0000000
--- a/doc/ResourcesLinks.html
+++ /dev/null
@@ -1,26 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:html="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>ResourcesLinks - simple pam module based on libp11 - Trac</title><style type="text/css">
- @import url(trac.css);
- </style></head><body><div class="wikipage">
- <div id="searchable"><h1>Resources, Links</h1>
-<p>
-<a class="ext-link" title="http://www.rsasecurity.com/rsalabs/" href="http://www.rsasecurity.com/rsalabs/" shape="rect">RSA Labs</a> defined the Public Key Cryptography Standards (PKCS).
-</p>
-<p>
-<a class="ext-link" title="http://www.rsasecurity.com/rsalabs/node.asp?id=2133" href="http://www.rsasecurity.com/rsalabs/node.asp?id=2133" shape="rect">PKCS#11</a> defines an API to use software modules
-that give access to cryptographic token hardware.
-</p>
-<p>
-We think PKCS#11 is not easy to use, so we use
-<a class="ext-link" title="http://www.opensc.org/libp11/" href="http://www.opensc.org/libp11/" shape="rect">libp11</a>, a thin layer on top of PKCS#11 API.
-</p>
-<p>
-Pam_p11 is tested with <a class="ext-link" title="http://www.opensc.org/opensc/" href="http://www.opensc.org/opensc/" shape="rect">OpenSC</a>, but should
-work fine with other implementations of PKCS#11, too.
-</p>
-<p>
-[<a class="ext-link" title="http://www.kernel.org/pub/linux/libs/pam/" href="http://www.kernel.org/pub/linux/libs/pam/" shape="rect">http://www.kernel.org/pub/linux/libs/pam/</a> Linux-PAM (Pluggable Authentication
-Modules for Linux)] has the source code and documentation for PAM on linux.
-</p>
-</div>
- </div><div class="footer"><hr></hr><p><a href="index.html">Back to Index</a></p></div></body></html>
diff --git a/doc/index.html b/doc/index.html
deleted file mode 100644
index 47fadbf..0000000
--- a/doc/index.html
+++ /dev/null
@@ -1,59 +0,0 @@
-<html xmlns="http://www.w3.org/1999/xhtml" xmlns:html="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
-<title>simple pam module based on libp11 - Trac</title><style type="text/css">
- @import url(trac.css);
- </style></head><body><div class="wikipage">
- <div id="searchable"><h1>Welcome to pam_p11</h1>
-<p>
-Pam_p11 is a plugable authentication module (pam) package for using
-crpytographic tokes such as smart cards and usb crypto tokens for
-authentication.
-</p>
-<p>
-Pam_p11 uses <a class="ext-link" title="http://www.opensc.org/libp11/" href="http://www.opensc.org/libp11/" shape="rect">libp11</a> to access any
-PKCS#11 module. It should be compatible with any implementation,
-but it is primarely developed using <a class="ext-link" title="http://www.opensc.org/opensc/" href="http://www.opensc.org/opensc/" shape="rect">OpenSC</a>.
-</p>
-<p>
-Pam_p11 implements two authentication modules:
-</p>
-<ul><li>pam_p11_openssh authenticates the user using his openssh
-<tt>~/.ssh/authorized_keys</tt> file.
-</li><li>pam_p11_opensc authenticates the user using certificates found in
-<tt>~/.eid/authorized_certificates</tt>. It is compatible with the
-older opensc "pam_opensc" authentication module (eid mode).
-</li></ul><p>
-Pam_p11 is very simple, it has no config file, no options other than the
-PKCS#11 module file, does not know about certificate chains,
-certificate authorities, revocation lists or OCSP.
-Perfect for the small installation with no frills.
-</p>
-<h2>License</h2>
-<p>
-Libp11 is Open Source software licensed under the <a class="ext-link" title="http://www.gnu.org/licenses/licenses.html#LGPL" href="http://www.gnu.org/licenses/licenses.html#LGPL" shape="rect">GNU LGPL license version 2.1 or later</a>.
-</p>
-<p>
-Pam_p11 uses pam, openssl, libp11 and OpenSC
-(or any other implementation of pkcs11).
-</p>
-<blockquote>
-<p>
-Thanks to all those projects, without it would not be possible.
-</p>
-</blockquote>
-<h2>Authors</h2>
-<p>
-Pam_p11 was written by Andreas Jellinghaus, but the code was mostly assembled
-from several sources. Credit goes to (in alphabetical order)
-</p>
-<p>
-Andreas Jellinghaus, Antti Tapaninen, Juan Antonio Martinez, Juha Yrjölä,
-Kevin Stefanik, Ludovic Rousseau, Mario Strasser, Markus Friedl, Olaf Kirch,
-Tatu Ylonen, Timo Sirainen.
-</p>
-<h2>Starting Points</h2>
-<ul><li><a href="OperatingSystems.html" shape="rect">OperatingSystems</a> -- Pam_p11 should work with any PAM implementation.
-</li><li><a href="QuickStart.html" shape="rect">QuickStart</a> -- How to install pam_p11 and how to use it in your applications.
-</li><li><a href="MailingLists.html" shape="rect">MailingLists</a> -- How to contact us.
-</li><li><a href="ResourcesLinks.html" shape="rect">ResourcesLinks</a> -- Standards, Documents, etc.
-</li></ul></div>
- </div><div class="footer"><hr></hr><p><a href="index.html">Back to Index</a></p></div></body></html>
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-opensc/pam-p11.git
More information about the pkg-opensc-commit
mailing list