I agree wholeheartedly. In fact, to make it easier to find libraries, I created a page with links to 7 libraries with at least one pubic key system & one private key system included. www.homeport.org/~adam/crypto The tools are out there. Adam attila@primenet.com wrote: | In <328E8BEC.2D76@gte.net>, on 11/16/96 | at 07:52 PM, Dale Thorn <dthorn@gte.net> said: | | ::Point 2: I've said something like this before, but here's a place where | ::it could mean something. If c-punks and others could divvy up as many | ::of the supporting functions of "strong" crypto as possible, and issue | ::them in a set of commonly-available libraries for any and all programmers, | ::along with source code, then an application programmer (theoretically) | ::could order up some of these libraries and write some useful crypto code | ::in short order. | :: | one of the best proposals in many years --we have all made good | use of library code over the years, unless the simpleton coder has a | obsessive-compulsive masochistic need to write an extra 20-50,000 | lines of 'reinvent the wheel' code. | | there are several linkable libraries floating around, with | multiple types, etc. the only one I looked at a couple of years | ago needed some extensive work on its calling and return | conventions --ever hear of structures? -- "It is seldom that liberty of any kind is lost all at once." -Hume