Richard, I'm sorry that your experience with EPIC5 did not meet your expectations.
As with so many free, source available software packages, you have found that those with unusual system configurations may need to do some tweaking to get things working "just so". If you'd like to contribute your patches to the project for inclusion, please email them on to me, and I'll do what I can. However, please note that OpenSSL is an important, ubiquitous software package that provides functionality beyond just https and encryption. It is unlikely that going forward EPIC5 will be able to work without openssl. I recommend EPIC4 for your needs, if you are still interested in giving epic a try. Thanks, Jeremy [You wrote] >dear epic developers, > >i had a very hard time compiling this very client on a >vanilla ubuntu x86_64 box. > >Linux linda 2.6.32-35-generic #78-Ubuntu SMP Tue Oct 11 16:11:24 UTC 2011 x86_ 64 GNU/Linux > >Ubuntu 10.04.3 LTS > >your ssl code is absolutely broken, as is the configure script. >i had to fix the configure script by hand to disable the broken >default ssl code. > >tcl wasnt detected aswell, had to fix the generated Makefile >by hand. > >please fix the broken ssl code and configure script asap. >this renders the client totally unuzbl. > >epic version used: >epic5-1.1.2 > >using the broken ssl code by default is absolutely wrong. >especially in 3rd world countries like germany and north korea where >the use of strong crypto is unwanted and therefore strictly prohibited. > >how should a german script kid like me use this client if >even the configure script is broken ? > >or is the client developed for a different kind of user base ? >the 1337 h4x0r and s3CuRiTY Xp3rT ? for the g33x and n3rdz ? > >best regards, > >Richard Koumbos > > >----- End forwarded message ----- _______________________________________________ List mailing list List@epicsol.org http://epicsol.org/mailman/listinfo/list
