Loading doc/apps/ca.pod +10 −12 Original line number Diff line number Diff line Loading @@ -517,18 +517,6 @@ A sample configuration file with the relevant sections for B<ca>: commonName = supplied emailAddress = optional =head1 WARNINGS The B<ca> command is quirky and at times downright unfriendly. The B<ca> utility was originally meant as an example of how to do things in a CA. It was not supposed to be used as a full blown CA itself: nevertheless some people are using it for this purpose. The B<ca> command is effectively a single user command: no locking is done on the various files and attempts to run more than one B<ca> command on the same database can have unpredictable results. =head1 FILES Note: the location of all files can change either by compile time options, Loading Loading @@ -593,6 +581,16 @@ create an empty file. =head1 WARNINGS The B<ca> command is quirky and at times downright unfriendly. The B<ca> utility was originally meant as an example of how to do things in a CA. It was not supposed to be used as a full blown CA itself: nevertheless some people are using it for this purpose. The B<ca> command is effectively a single user command: no locking is done on the various files and attempts to run more than one B<ca> command on the same database can have unpredictable results. The B<copy_extensions> option should be used with caution. If care is not taken then it can be a security risk. For example if a certificate request contains a basicConstraints extension with CA:TRUE and the Loading Loading
doc/apps/ca.pod +10 −12 Original line number Diff line number Diff line Loading @@ -517,18 +517,6 @@ A sample configuration file with the relevant sections for B<ca>: commonName = supplied emailAddress = optional =head1 WARNINGS The B<ca> command is quirky and at times downright unfriendly. The B<ca> utility was originally meant as an example of how to do things in a CA. It was not supposed to be used as a full blown CA itself: nevertheless some people are using it for this purpose. The B<ca> command is effectively a single user command: no locking is done on the various files and attempts to run more than one B<ca> command on the same database can have unpredictable results. =head1 FILES Note: the location of all files can change either by compile time options, Loading Loading @@ -593,6 +581,16 @@ create an empty file. =head1 WARNINGS The B<ca> command is quirky and at times downright unfriendly. The B<ca> utility was originally meant as an example of how to do things in a CA. It was not supposed to be used as a full blown CA itself: nevertheless some people are using it for this purpose. The B<ca> command is effectively a single user command: no locking is done on the various files and attempts to run more than one B<ca> command on the same database can have unpredictable results. The B<copy_extensions> option should be used with caution. If care is not taken then it can be a security risk. For example if a certificate request contains a basicConstraints extension with CA:TRUE and the Loading
