[523] in WWW Security List Archive

home help back first fref pref prev next nref lref last post

Terisa's libshttp.a

daemon@ATHENA.MIT.EDU (Bryan J. Ischo)
Thu Mar 16 23:23:10 1995

Date: Thu, 16 Mar 1995 19:08:03 -0500 (EST)
From: "Bryan J. Ischo" <bi04+@andrew.cmu.edu>
To: www-security@ns2.rutgers.edu
Errors-To: owner-www-security@ns2.rutgers.edu


Hi.  I'm new to this list.

Has anyone out there purchased Terisa's SHTTP library?  If so, could you
perhaps drop me a line giving me your opinions on it?  My company has
purchased this library and I am having a really hard time getting any
support for it - and it needs ALOT of support, considering the
horrendous quality of the documentation (not to mention the fact that
I'm getting linker errors when I try to use it).  I'd be interested in
knowing how other people have overcome these difficulties.

Also, I'd be interested in hearing whether or not people are just
writing their own implementations of SHTTP rather than buying the
library.  We thought about writing our own but we decided that it would
save alot of time and effort to buy Terisa's library.  So far it hasn't.

Furthermore, I would like to voice an opinion on SHTTP and SSL as
competing Web security protocols:  as a software developer incorporating
both protocols into our product, without ANY previous knowledge of
security protocols, I have to say that without a doubt SSL makes more
sense and is easier to implement.  Even with Terisa's library and
without ever looking at Netscape's reference SSL implementation, SSL has
been easier to implement.  I suppose it has alot to do with the
complexity of SHTTP on a parsing level and in the ambiguity of the
documentation.

Thank you,
Bryan


home help back first fref pref prev next nref lref last post