Skip to Content.
Sympa Menu

freetds - RE: md4 implementation

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Castellano, Nicholas" <Nicholas_Castellano AT acml.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: md4 implementation
  • Date: Sat, 28 Sep 2002 16:18:43 -0400


I have seen hints on Sybase's web site that OpenClient 12.5 supports SSL
connections to the dataserver. Maybe we should think about the potential
consequences of removing OpenSSL support, before doing anything hasty.

If the only issue here is that the same binary distribution can't contain
both OpenSSL and readline, perhaps all we really need to do is:

- Distribute tsql.c as it is, with an LGPL copyright
- Add a notice to tsql.c and top-level README type files, stating that if
you link tsql with readline, it will then fall under GPL because of the
distribution terms of GNU readline
- Add autoconf checks that disallow linking with OpenSSL and GNU readline at
the same time.

Does that resolve all the license conflicts, or did I forget something?

Cheers,
--nick

-----Original Message-----
From: bounce-freetds-145195 AT franklin.oit.unc.edu
[mailto:bounce-freetds-145195 AT franklin.oit.unc.edu]
Sent: Saturday, September 28, 2002 2:27 PM
To: TDS Development Group
Subject: [freetds] md4 implementation


I founded this implementation of md4...

http://www-adele.imag.fr/~donsez/cours/exemplescourstechnoweb/js_securehash/
md4src.html

Quite simple...

freddy77




---
You are currently subscribed to freetds as: [Nicholas_Castellano AT acml.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above. If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.






Archive powered by MHonArc 2.6.24.

Top of Page