7 Commits

Author	SHA1	Message	Date
Richard Levitte	4b16376d51	"UID" is an incorrect lable for the attribute type uniqueIdentifier. ... Furthermore, it create conflicts with LDAP and some RFCs that define "UID" as a lable for the attribute type userId (which we haven't even defined here). The next question is if we should update objects.txt with the added stuff from the main trunk.	2001-12-04 11:10:54 +00:00
Bodo Möller	16712ec35e	Fix: 2.5.29 is "id-ce", not "ld-ce" (sort of a typo in objects.h). ... Fix: Some ip-pda OIDs were incorrect (cf. RFC 3039). Also change Perl scripts to put auto-generation warning in the first lines of the file.	2001-12-03 13:44:24 +00:00
Richard Levitte	accb6063f3	'make update'	2001-10-10 21:52:27 +00:00
Richard Levitte	622ec449e5	Added OIDs from RFC 2247, 1155, and a few from 1700	2000-08-19 08:47:59 +00:00
Richard Levitte	3009458e2f	MD4 implemented. Assar Westerlund provided the digest code itself and the test utility, I added the bits to get a EVP interface, the command line utility and the speed test	2000-08-14 14:05:53 +00:00
Richard Levitte	27d7260075	Corrected small bug that could add ',L' when it shouldn't	2000-07-08 07:56:12 +00:00
Richard Levitte	c2bbf9cf6c	I got sick and tired of having to keep track of NIDs when such a thing ... could be done automagically, much like the numbering in libeay.num and ssleay.num. The solution works as follows: - New object identifiers are inserted in objects.txt, following the syntax given in objects.README. - objects.pl is used to process obj_mac.num and create a new obj_mac.h. - obj_dat.pl is used to create a new obj_dat.h, using the data in obj_mac.h. This is currently kind of a hack, and the perl code in objects.pl isn't very elegant, but it works as I intended. The simplest way to check that it worked correctly is to look in obj_dat.h and check the array nid_objs and make sure the objects haven't moved around (this is important!). Additions are OK, as well as consistent name changes.	2000-07-05 02:45:36 +00:00