Skip to Content.
Sympa Menu

freetds - RE: Patch Re: Is a zero-length password OK?

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: RE: Patch Re: Is a zero-length password OK?
  • Date: Thu, 15 Aug 2002 14:49:02 -0400


> From: Harry Felder [mailto:harry AT rentec.com]
> Sent: August 15, 2002 2:30 PM
>
> Sorry, I got distracted and never generated a patch to fix
> the below discussed problem with a zero-length password.
>
> The problem occurs with unixODBC's isql in a call like:
>
> isql DSN UID ''
>
> With the patch I can connnect fine. The patch is against the
> latest cvs.

Thanks for the patch, Harry.

> Also, SQSH 2.1 doesn't seem to compile at the moment since it includes
> tds.h which includes config.h, which isn't installed. Should
> I configure it
> it to be looking directly in the private freetds build
> include directory
> instead of the public directory for installed include files?

Don't point sqsh's build at the FreeTDS source tree. That shouldn't be
necessary, not now not ever.

config.h is generated by the configure script. I just rebuilt last night
around 9:00 PM EST (GMT -4), and my tds.h doesn't include config.h:

http://www.schemamania.org/freetds/cvs/freetds/include/tds.h

What are you seeing?

--jkl


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