Skip to Content.
Sympa Menu

freetds - RE: [freetds] Domain Login Support, connecting to MSSQL issue

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Domain Login Support, connecting to MSSQL issue
  • Date: Mon, 4 Aug 2003 14:44:14 -0400

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafone.com]
> Sent: August 4, 2003 11:56 AM
> >
> > I like that idea. If the username has either of the the forms:
> >
> > domain\username
> > \\domain\username
> >
> > we know to use a domain login. If there's an "nt domain"
> > entry, we know to use a domain login. Else we use a normal
> > server login. That's unambiguous, nonredundant, and declarative.
>
> And already in CVS (from 0.60, I think... perhaps not well
> documented...)

Excellent! What is the effect of "nt domain"?

> IMHO \\domain\username is not as good cause it usually refer to file
> names, not username.

Acknowledged. Forget I mentioned it.

> > Microsoft logins may contain a '/', so we can't easily
> > support "domain/username".
>
> Why '/' ? '\\' is not good ?

I think Samba allows '/', but I see no reason we should. Backslashes tend
to be a support problem, because people often overlook the need for single
quotes or other escapes.

What about username@domain? Microsoft's rule as of 7.0 was that '@' could
not appear in a username, so if we see '@' we're safe inferring a domain
login.

> In all tests I did it run (I never change a line...) so it work...
> So, we should remove "try server login", "try domain login"
> and "domain"
> entry from FreeTDS (I suggest to leave and document as obsolete)

Agreed.

--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 we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page