aboutsummaryrefslogtreecommitdiffstats
path: root/doc/examples
Commit message (Collapse)AuthorAgeFilesLines
* Fix tls_server example compilationlloyd2010-11-301-2/+8
|
* Remove incorrect commentlloyd2010-11-291-16/+4
|
* Inherit policy and override check_certlloyd2010-11-292-2/+33
|
* Add X509_Certificate::to_stringlloyd2010-11-291-122/+1
| | | | The x509info example now just calls that
* MemoryRegion::set was removedlloyd2010-11-291-1/+2
|
* New way of specifying key lengthslloyd2010-10-291-1/+6
|
* Remove use of lookupslloyd2010-10-292-6/+10
|
* Make TLS_Client entirely via callbacks, not talking to Socket directlylloyd2010-10-191-1/+3
|
* Use binary I/O where neededlloyd2010-10-1510-11/+11
|
* Fix exampleslloyd2010-10-134-7/+11
|
* Fix compilation of examples; benchmarking and RNG changes mostlylloyd2010-10-125-35/+13
|
* Fix examples for destroy being renamed clearlloyd2010-09-132-2/+2
|
* Remove more uses of vector to pointer implicit conversionslloyd2010-09-131-1/+5
|
* Read input as binarylloyd2010-09-081-1/+1
|
* Specify the target host and port for tls_client on the command linelloyd2010-09-081-3/+18
|
* Big, invasive but mostly automated change, with a further attempt atlloyd2010-09-071-1/+1
| | | | | | | | | | | | | | harmonising MemoryRegion with std::vector: The MemoryRegion::clear() function would zeroise the buffer, but keep the memory allocated and the size unchanged. This is very different from STL's clear(), which is basically the equivalent to what is called destroy() in MemoryRegion. So to be able to replace MemoryRegion with a std::vector, we have to rename destroy() to clear() and we have to expose the current functionality of clear() in some other way, since vector doesn't support this operation. Do so by adding a global function named zeroise() which takes a MemoryRegion which is zeroed. Remove clear() to ensure all callers are updated.
* Oops... renamed this quite a while ago, never updated examplelloyd2010-09-071-6/+6
|
* Allow generating larger keys in rsa_kgen example (up to 16K bits)lloyd2010-08-181-1/+1
|
* Missing include, VC++ complainedlloyd2010-08-121-0/+1
|
* Organize CPUID output a little more nicelylloyd2010-07-281-4/+10
|
* Add support in CPUID for detecting PCMULUDQ and MOVBE instructions.lloyd2010-07-271-5/+4
| | | | Rename CPUID::has_aes_intel to has_aes_ni.
* Modify CPUID so all the check functions are purely inline. Add a newlloyd2010-07-261-2/+4
| | | | | initialize() call which must be called prior to use of any other functions.
* Removed UI herelloyd2010-07-121-3/+1
|
* Rename S2K to PBKDF, because that is by far the most common name - S2Klloyd2010-07-094-35/+37
| | | | | | | | | | | | | really is only used by OpenPGP, and largely it was named S2K here because the OpenPGP S2K was implemented years before the ones in PKCS #5. We have a typedef of PBKDF to S2K, and an inlined get_s2k that calls get_pbkdf for source compatability. There doesn't seem to be any reason to have a forward for the renamed s2k.h header - to actually use a PBKDF, you'd have to either include lookup.h and call get_s2k / get_pbkdf, or else include an algorithm-specific header and use it directly. In either case, including s2k.h is neither necessary nor sufficient.
* Read and save the files in binary mode to avoid weird EOF problemslloyd2010-07-072-2/+2
| | | | on Windows.
* Add detection support for upcoming AVXlloyd2010-06-251-0/+1
|
* Small cleanupslloyd2010-06-021-9/+8
|
* Remove FORK-256; it's obscure and has been definitively broken.lloyd2010-05-251-1/+0
| | | | | More commentary posted to the list: http://lists.randombit.net/pipermail/botan-devel/2010-May/001123.html
* Cleanups. Name our cert for localhost. Used AutoSeeded_RNG.lloyd2010-04-191-12/+16
| | | | Report SNI request, if any.
* Just report total size output at the endlloyd2010-04-191-1/+7
|
* Show as creating an engine insteadlloyd2010-03-241-27/+31
|
* Fix factor wrt rename of primality test functionslloyd2010-03-231-1/+1
|
* Rename PK_Encryptor_MR_with_EME and PK_Decryptor_MR_with_EME tolloyd2010-03-082-2/+2
| | | | | PK_Encryptor_EME and PK_Decryptor_EME; the message recovery is somewhat implicit in the recovery of the plaintext.
* Modify pubkey classes to take names instead of object pointers.lloyd2010-03-088-30/+26
| | | | | Remove use of look_pk from the source and examples, instead instantiate classes directly.
* Update DH example for PK changeslloyd2010-03-081-14/+29
|
* Fix minor errors and warnings in the examples. Remove boost dependency fromlloyd2010-03-0315-120/+78
| | | | rng_test example.
* Add a simple cert validation examplelloyd2010-03-011-0/+35
|
* TLS_Server example - more printfs, configurable portlloyd2010-02-171-3/+13
|
* Various minor SSL fixeslloyd2010-02-142-10/+6
|
* propagate from branch 'net.randombit.botan' (head ↵lloyd2010-02-146-68/+48
|\ | | | | | | | | | | dd33b7150f3f49d795e4eb962d8d41d1ada58d8d) to branch 'net.randombit.botan.ssl' (head 1452205423962b664263fd2a35149122dfc94d37)
| * Further passhash changes before release and things have to belloyd2010-02-051-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | finalized. Move header to passhash9.h and rename the functions to be passhash9 specific ({generator,check}_passhash9) Add an algorithm identifer field. Currently only id 0 is defined, for HMAC(SHA-1), but this opens up for using HMAC(SHA-512) or HMAC(SHA-3) or CMAC(Blowfish) or whatever in the future if necessary. Increase the salt size to 96 bits and the PRF output size to 192 bits. Document in api.tex
| * Prefix passhash with "$9$" in a manner similar with otherlloyd2010-02-021-3/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | password hashing schemes. Increase salt size to 80 bits. Research shows that virtually no other PBKDF2 implementations support anything but SHA-1; for ease of implementation elsehwere switch back from SHA-512 to SHA-1. Should be mostly harmless; it limits total entropy of the password to a maximum of 160 bits, but this is unlikely anyway. Use two bytes to specify the work factor for future-proofing. Add a test.
| * Password hashing is a pretty useful service, really. Move the guts oflloyd2010-02-011-58/+7
| | | | | | | | | | | | | | | | the passhash example to the library. Support variable work factors; default work factor of 10 takes about half a second to do one password on my Core2. Switch to using SHA-512 instead of SHA-1 in PBKDF2. To keep the output evenly sized for base64 purposes, reduce PBKDF2 output size by one byte (to 112 bits).
| * Modify the S2K interface. Instead of being stateful in terms of the saltlloyd2010-02-015-28/+62
| | | | | | | | | | | | | | | | | | | | | | and iteration count, force it to be passed to each call to derive_key. So remove current_salt, set_iterations, new_random_salt, and change_salt functions from S2K interface. Update examples and test application to match. While I was in there, change the passhash example to use 64 bit salts and 128 bit PBKDF2 outputs.
| * Fix cpuid examplelloyd2010-01-191-1/+0
| |
* | Import latest version of Ajisai into src/ssl; once this hits mainlinelloyd2010-01-112-0/+126
|/ | | | | | | | I'll officially kill off Ajisai (instead of it just lingering as a zombine as it is currently). Apparently I broke something (or multiple things) during the import process; servers crash and clients gets MAC errors on connect.
* Clean up exceptions. Remove some unused ones like Config_Error. Makelloyd2010-01-051-2/+2
| | | | | | | Invalid_Argument just a typedef for std::invalid_argument. Make Botan::Exception a typedef for std::runtime_error. Make Memory_Exhaustion a public exception, and use it in other places where memory allocations can fail.
* The first bits of a general toolbox program. Currently does hex and base64lloyd2009-12-311-0/+235
| | | | encoding/decoding, bzip2 and zlib compression/decompression, and hashing.
* Drop test_es.cpp, EntropySources no longer directly available outside librarylloyd2009-12-311-121/+0
|
* Add copyright and license notes to pretty much every file that didn't have them,lloyd2009-12-3150-205/+327
| | | | | | | | including the examples and self-test code. Most of these files had not copyright/license information at all; since a major point of the examples is to allow users to copy and paste code that already does something they want, an ambigious license is not good.