PBC Library Manual 0.5.11 - Stanford Crypto Group

More documents

Recommendations

Info

Returns true if t contains key key. void * symtab_at(symtab_t t, const char *key) Returns pointer at key key in t. 8.13. Religious stances I chose C because: • GMP, which PBC requires and is also modeled on, is also written in C. Chapter 8. PBC internals • PBC is intended to be a low-level portable cryptographic library. C is the least common denominator. It should not be difficult to wrap PBC for other languages. • Despite its drawbacks (I would appreciate operator overloading and genericity, and to a lesser extent garbage collection), I’ve found few languages I like better. To quote Rob Pike, C is the desert island language. (I also agree with his statement that OO languages conceptually provide little extra over judicious use of function pointers in C.) With respect to indentation, I’m migrating the code to follow Google C++ Style Guide (http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml) to avoid having to switch styles all the time. The code was originally written using my old style: 4-space indent with 1TBS (One True Brace Style). I’d like to have no library dependencies (except standard C libraries), but then I’d have to write a large integer library. Furthermore, I’d have to write it in assembly, and then port it. To avoid this, I use an existing library. I selected GMP because the library’s focus is on multiprecision arithmetic and nothing else, and it aims to be as fast as possible on many platforms. Another important factor is that GMP is released under a free license. On the other hand, GMP is written to deal with extremely large numbers, while I mostly only need integers that are roughly between 160 and 2048 bits. It is possible a library specializing in numbers of these sizes would be better for PBC. I’m fond of GMP’s method for eliminating the need for the & and * operators most of the time by declaring a typedef on arrays of size 1. I try to do the same with PBC for consistency, though this trick does have drawbacks. 43
Chapter 8. PBC internals I would like to have GMP as the only library dependency, though I do not mind using other libraries so long as they are optional. For example, one of the test programs is much easier to use if compiled with the GNU readline library, but by default compiles without it and is still functional. I dislike the C preprocessor. I like to place platform-specific code in separate files and let the build system work out which one to use. Integer constants can be defined with enum instead. I intend to minimize the number of #include statements in header files for PBC’s internal use as much as possible (they should be in the .c files instead), and later perhaps even remove those annoying #ifndef statements too. I grudgingly accept some macros for PBC’s debugging features. I liberally use nested functions, a GNU C extension. I find their expressiveness so indispensable that I’m willing to sacrifice portability for them. The GNU libc manual (http://www.gnu.org/software/libc/manual/html_node/Reserved-Names.html) states that data types ending in _t should not be used because they are reserved for future additions to C or POSIX. On the other hand, I want to stay consistent with GMP, and ending data types with _t is common practice. 44
Page 1 and 2: PBC Library Manual 0.5.11 Ben Lynn
Page 3 and 4: Table of Contents Preface .........
Page 5 and 6: Preface The PBC library is a free p
Page 7 and 8: Chapter 1. Installing PBC The first
Page 9 and 10: Chapter 2. Tutorial This chapter wa
Page 11 and 12: 2.2. Import/export Chapter 2. Tutor
Page 13 and 14: Chapter 3. Pairing functions An app
Page 15 and 16: Chapter 3. Pairing functions Get re
Page 17 and 18: Chapter 4. Element functions Elemen
Page 19 and 20: void element_set0(element_t e) Set
Page 21 and 22: Chapter 4. Element functions z must
Page 23 and 24: Chapter 4. Element functions void e
Page 25 and 26: size_t element_out_str(FILE * strea
Page 27 and 28: int element_length_in_bytes_x_only(
Page 29 and 30: Chapter 5. Param functions Pairings
Page 31 and 32: Chapter 5. Param functions Generate
Page 33 and 34: Chapter 6. Other functions Random n
Page 35 and 36: Reports informational message. void
Page 37 and 38: nd(G) init_pairing_A(); Other sampl
Page 39 and 40: Chapter 8. PBC internals The source
Page 41 and 42: Additionally, defining PBC_DEBUG ca
Page 43 and 44: The lack of an x term simplifies so
Page 45 and 46: Chapter 8. PBC internals b: E: y^2=
Page 47: Returns the pointer at index i in t
Page 51: Appendix A. Contributors Ben Lynn w

PBC Library Manual 0.5.11 - Stanford Crypto Group

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?