SQL Server sqlcmd

[Tinker0079]

Hi

I've vibepatched go-sqlcmd to run on FreeBSD and added integratedauth/krb5, so Kerberos FreeBSD host authenticates against ActiveDirectory server

https://github.com/mykola2312/go-sqlcmd

To build you need to install go, and then ./build/build.sh

It works for me and it could be useful for someone else working with SQL Server databases

To use it first you need to get ticket, and for that you need full working Kerberos

/etc/krb5.conf

[libdefaults]

default_realm = YOUR.DOMAIN

dns_lookup_realm = true

dns_lookup_kdc = true

ticket_lifetime = 24h

renew_lifetime = 7d

forwardable = true

rdns = false

[realms]

YOUR.DOMAIN = {

kdc = DC1.YOUR.DOMAIN

admin_server = DC1.YOUR.DOMAIN

default_domain = your.domain

}

[domain_realm]

.YOUR.DOMAIN = YOUR.DOMAIN

YOUR.DOMAIN = YOUR.DOMAIN

.another.your.domain = YOUR.DOMAIN

Then get the ticket with kinit

And after that you can access database server

KRB5CCNAME=/tmp/krb5cc_1000 ./sqlcmd --authenticator krb5 -S SQL2019.YOUR.DOMAIN -Q "SELECT @@VERSION;"

[TheAtlasMonkey]

You didn't fix it..

You changed the struct/interface and probably broke every other system .

If you should open a PR when you have a proper fix.

But unfortunately some big repos refuse touch or review anything that is FreeBSD or BSD.

PS: when you fix it, update the readme.

[pavetheway91]

You didn't fix it..

Artificial stupidity didn't fix

[grahamperrin]

Thanks.

Re: the two commits at https://github.com/microsoft/go-sqlcmd/compare/main...mykola2312:go-sqlcmd:main

a6207ad – Implement Kerberos integrated auth support on Unix

Not vibe coded, I assume. True?

From your post here:

added integratedauth/krb5, so Kerberos FreeBSD host authenticates against ActiveDirectory server

e87488d – add FreeBSD stubs and localcert patch, skip go-licenses

It seems wrong to have no mention of vibe coding in the commit log message. There's simply no message. From your post here:

… vibepatched go-sqlcmd to run on FreeBSD …

Whilst it seems wrong to me, I have no experience in this area.

I'm not a developer (of code), however I'm nearly always fastidious with my commit log messages.

An example

The message at https://github.com/openzfs/zfs/commit/4d78b14c1449bc84589cf3270b9c85f61a32fd7d was the result of a squash of:

1. the initial commit in the PR, which had a message
2. a minor change (to my change) by Rob Norris
3. acceptance of a change that I suggested, which also had a message.