This is really frustrating. I'm trying to figure out how to use this damn ecash software to setup a prototype ecash-accepting remailer. For one thing, there's no documention. Secondly, from what I can tell, it's like PGP. To integrate it into other software you have to do all sorts of nasty output parsing. why the hell can't it just produce nice, terse, informative, UNIX-like output? it's late, i'm tired, I'm going to sleep. (the party was fun, btw, thanks to everyone who showed up.) -- sameer Voice: 510-601-9777 Community ConneXion FAX: 510-601-9734 The Internet Privacy Provider Dialin: 510-658-6376 http://www.c2.org/ (or login as "guest") sameer@c2.org
Secondly, from what I can tell, it's like PGP. To integrate it into other software you have to do all sorts of nasty output parsing. why the hell can't it just produce nice, terse, informative, UNIX-like output?
This will change with PGP 3. There is a very nice, easy API for PGP 3 which I have been working on for over the last month. In fact, the main processing code is done. After Tranksgiving I will be working on an API document which explains the design and implementation of the API. IMHO, the API is REALLY EASY to use -- I have a PGP encryption program which has all of the main functionality of PGP w.r.t. creating messages, and the program is only 250 lines of commented C code. The current work is far from complete, but it is getting close! It should make integrating PGP into other programs very simple -- just link against libpgp.a. :) Enjoy! -derek
Cool! I'm really glad you're working in this. Now if only digicash would release libecash.a, we'd have the infrastructure for some killer apps.
Secondly, from what I can tell, it's like PGP. To integrate it into other software you have to do all sorts of nasty output parsing. why the hell can't it just produce nice, terse, informative, UNIX-like output?
This will change with PGP 3. There is a very nice, easy API for PGP 3 which I have been working on for over the last month. In fact, the main processing code is done. After Tranksgiving I will be working on an API document which explains the design and implementation of the API.
IMHO, the API is REALLY EASY to use -- I have a PGP encryption program which has all of the main functionality of PGP w.r.t. creating messages, and the program is only 250 lines of commented C code.
The current work is far from complete, but it is getting close! It should make integrating PGP into other programs very simple -- just link against libpgp.a. :)
Enjoy!
-derek
-- sameer Voice: 510-601-9777 Community ConneXion FAX: 510-601-9734 The Internet Privacy Provider Dialin: 510-658-6376 http://www.c2.org/ (or login as "guest") sameer@c2.org
-----BEGIN PGP SIGNED MESSAGE-----
This will change with PGP 3. There is a very nice, easy API for PGP 3 which I have been working on for over the last month. In fact, the main processing code is done. After Tranksgiving I will be working on an API document which explains the design and implementation of the API.
IMHO, the API is REALLY EASY to use -- I have a PGP encryption program which has all of the main functionality of PGP w.r.t. creating messages, and the program is only 250 lines of commented C code.
The current work is far from complete, but it is getting close! It should make integrating PGP into other programs very simple -- just link against libpgp.a. :)
This is SUCH good news! May your coding be swift and sure. Let no bug delay that wonderful day of public distribution. Regards, Bryce -----BEGIN PGP SIGNATURE----- Version: 2.6.2 Comment: Auto-signed under Unix with 'BAP' Easy-PGP v1.01 iQCVAwUBMK/KF/WZSllhfG25AQG+1gP/apI7RmfRne74IhYf7UELMH0Bm1gTIMe5 JibSxLtVhUE+WsAn5dn/Hwt797M11hc/DqpfDgeWlw7xIUxQKEWKLDGoeChHzFBG T/7xc4+6H3DA4ZZZSMWDPvM1aJG71u+thnHU4r+fMOO3k9tKJ5YAsfcRD0l4+JL4 3Lp5IjKJbm8= =vDu5 -----END PGP SIGNATURE-----
participants (3)
-
Bryce -
Derek Atkins -
sameer