Skip to Content.
Sympa Menu

freetds - Re: How to compile SQSH with FreeTDS .60?

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Steve Langasek <vorlon AT netexpress.net>
  • To: TDS Development Group <freetds AT franklin.metalab.unc.edu>
  • Subject: Re: How to compile SQSH with FreeTDS .60?
  • Date: Sun, 6 Oct 2002 15:04:36 -0500

Hmm, I seem to have misplaced a few messages on the list.

On Fri, Oct 04, 2002 at 10:59:28AM -0400, Lowden, James K wrote:
> > From: Jay Sauls [mailto:jaysauls AT hotmail.com]
> > Sent: October 4, 2002 1:52 AM

> > I think I do have my freetds.conf configured correctly; I can run

> > tsql -S <my.machine.name> -U <mydomain\\myuser>

> > and it works perfectly (against a sql server configured for
> > only integrated auth).

> You're at the edge of what I know about this, so I'm not going to be much
> help. FWIW, I think you might be the first guy to use FreeTDS's ct-lib to
> connect to Microsoft's server using a domain login. The ride may be a
> little bumpy. :/ This we know for sure: it's not what Scott Gray had in
> mind when he started sqsh!

Nope, I used sqsh for testing when decoupling FreeTDS from OpenSSL.
Domain logons have definitely been tested with CT-Lib, and work quite
well for me:

$ sqsh -U SQL\\vorlon -S sql
sqsh-2.1 Copyright (C) 1995-2001 Scott C. Gray
This is free software with ABSOLUTELY NO WARRANTY
For more information type '\warranty'
Password:
sql.localetest>

If 'nt domain' is set in freetds.conf for either the [global] section or
the per-server config, the domain can of course be omitted from the
commandline:

$ sqsh -U vorlon -S sql
sqsh-2.1 Copyright (C) 1995-2001 Scott C. Gray
This is free software with ABSOLUTELY NO WARRANTY
For more information type '\warranty'
Password:
sql.localetest>

> If I were trying to do what you're doing, I'd turn on logging. I'd connect
> with tsql, exit, and attempt with sqsh. Post both logs here. Frediano or
> Brian or Steve would be the ones to look at the log and possibly tell you
> what's going on. It could be something silly, you know, like sqsh getting
> surprised by the backslash.

AFAIK, sqsh passes the username string unmodified to ctlib.

> (Memo to file. We should support samba-style //domain/login as well as
> \\domain\login.)

Samba supports neither. :) Anywhere domain names are used on the
commandline in Samba, they're a separate argument -- you're probably
thinking of the \\server\share and //server/share syntax.

Supporting domain/login style usernames in addition to domain\login is a
bit more awkward, because successful autosensing of domain logins then
depends on '/' not being a valid character in a login name -- on *any*
of the server types supported by FreeTDS.

Steve Langasek
postmodern programmer

Attachment: pgpV_scl8IgMv.pgp
Description: PGP signature




Archive powered by MHonArc 2.6.24.

Top of Page