openssl/crypto/objects
Shane Lontis 9537fe5757 Single step kdf implementation
Reviewed-by: Paul Dale <paul.dale@oracle.com>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/8230)
2019-03-19 11:03:45 +00:00
..
build.info unified build scheme: add build.info files 2016-02-01 12:46:58 +01:00
o_names.c Following the license change, modify the boilerplates in crypto/objects/ 2018-12-06 15:07:30 +01:00
obj_dat.c Following the license change, modify the boilerplates in crypto/objects/ 2018-12-06 15:07:30 +01:00
obj_dat.h Single step kdf implementation 2019-03-19 11:03:45 +00:00
obj_dat.pl Update generator copyright year. 2019-01-07 14:01:58 -05:00
obj_err.c Following the license change, modify the boilerplates in crypto/objects/ 2018-12-06 15:07:30 +01:00
obj_lcl.h Following the license change, modify the boilerplates in crypto/objects/ 2018-12-06 15:07:30 +01:00
obj_lib.c Following the license change, modify the boilerplates in crypto/objects/ 2018-12-06 15:07:30 +01:00
obj_mac.num Single step kdf implementation 2019-03-19 11:03:45 +00:00
obj_xref.c Following the license change, modify the boilerplates in crypto/objects/ 2018-12-06 15:07:30 +01:00
obj_xref.h Support SM2 certificate verification 2019-03-13 15:29:39 +08:00
obj_xref.txt Support SM2 certificate verification 2019-03-13 15:29:39 +08:00
objects.pl Update generator copyright year. 2019-01-07 14:01:58 -05:00
objects.txt Single step kdf implementation 2019-03-19 11:03:45 +00:00
objxref.pl Update generator copyright year. 2019-01-07 14:01:58 -05:00
README Many spelling fixes/typo's corrected. 2017-11-11 19:03:10 -05:00

objects.txt syntax
------------------

To cover all the naming hacks that were previously in objects.h needed some
kind of hacks in objects.txt.

The basic syntax for adding an object is as follows:

	1 2 3 4		: shortName	: Long Name

		If Long Name contains only word characters and hyphen-minus
		(0x2D) or full stop (0x2E) then Long Name is used as basis
		for the base name in C. Otherwise, the shortName is used.

		The base name (let's call it 'base') will then be used to
		create the C macros SN_base, LN_base, NID_base and OBJ_base.

		Note that if the base name contains spaces, dashes or periods,
		those will be converted to underscore.

Then there are some extra commands:

	!Alias foo 1 2 3 4

		This just makes a name foo for an OID.  The C macro
		OBJ_foo will be created as a result.

	!Cname foo

		This makes sure that the name foo will be used as base name
		in C.

	!module foo
	1 2 3 4		: shortName	: Long Name
	!global

		The !module command was meant to define a kind of modularity.
		What it does is to make sure the module name is prepended
		to the base name.  !global turns this off.  This construction
		is not recursive.

Lines starting with # are treated as comments, as well as any line starting
with ! and not matching the commands above.