mirror of https://github.com/openssl/openssl.git
				
				
				
			Update from HEAD.
This commit is contained in:
		
							parent
							
								
									496970b233
								
							
						
					
					
						commit
						f1c65db80b
					
				
							
								
								
									
										10
									
								
								FAQ
								
								
								
								
							
							
						
						
									
										10
									
								
								FAQ
								
								
								
								
							|  | @ -823,11 +823,11 @@ code itself (the hex digits after the second colon). | ||||||
| 
 | 
 | ||||||
| * Why do I get errors about unknown algorithms? | * Why do I get errors about unknown algorithms? | ||||||
| 
 | 
 | ||||||
| This can happen under several circumstances such as reading in an | The cause is forgetting to load OpenSSL's table of algorithms with | ||||||
| encrypted private key or attempting to decrypt a PKCS#12 file. The cause | OpenSSL_add_all_algorithms(). See the manual page for more information. This | ||||||
| is forgetting to load OpenSSL's table of algorithms with | can cause several problems such as being unable to read in an encrypted | ||||||
| OpenSSL_add_all_algorithms(). See the manual page for more information. | PEM file, unable to decrypt a PKCS#12 file or signature failure when | ||||||
| 
 | verifying certificates. | ||||||
| 
 | 
 | ||||||
| * Why can't the OpenSSH configure script detect OpenSSL? | * Why can't the OpenSSH configure script detect OpenSSL? | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
|  | @ -151,10 +151,11 @@ bits is set to zero. | ||||||
| This specifies the format of the ultimate value. It should be followed | This specifies the format of the ultimate value. It should be followed | ||||||
| by a colon and one of the strings B<ASCII>, B<UTF8>, B<HEX> or B<BITLIST>. | by a colon and one of the strings B<ASCII>, B<UTF8>, B<HEX> or B<BITLIST>. | ||||||
| 
 | 
 | ||||||
| If no format specifier is included then B<ASCII> is used. If B<UTF8> is specified | If no format specifier is included then B<ASCII> is used. If B<UTF8> is | ||||||
| then the value string must be a valid B<UTF8> string. For B<HEX> the output must | specified then the value string must be a valid B<UTF8> string. For B<HEX> the | ||||||
| be a set of hex digits. B<BITLIST> (which is only valid for a BIT STRING) is a | output must be a set of hex digits. B<BITLIST> (which is only valid for a BIT | ||||||
| comma separated list of set bits. | STRING) is a comma separated list of the indices of the set bits, all other | ||||||
|  | bits are zero. | ||||||
| 
 | 
 | ||||||
| =back | =back | ||||||
| 
 | 
 | ||||||
|  | @ -172,6 +173,10 @@ An IA5String explicitly tagged using APPLICATION tagging: | ||||||
| 
 | 
 | ||||||
|  EXPLICIT:0A,IA5STRING:Hello World |  EXPLICIT:0A,IA5STRING:Hello World | ||||||
| 
 | 
 | ||||||
|  | A BITSTRING with bits 1 and 5 set and all others zero: | ||||||
|  | 
 | ||||||
|  |  FORMAT=BITLIST,BITSTRING:1,5 | ||||||
|  | 
 | ||||||
| A more complex example using a config file to produce a | A more complex example using a config file to produce a | ||||||
| SEQUENCE consiting of a BOOL an OID and a UTF8String: | SEQUENCE consiting of a BOOL an OID and a UTF8String: | ||||||
| 
 | 
 | ||||||
|  |  | ||||||
		Loading…
	
		Reference in New Issue