Re: Update docs for encryption configuration

Marc Abramowitz <[email protected]>
Newsgroups gmane.comp.db.tds.freetds
Message-ID <[email protected]>
I'm guessing that you got an error because the branch was merged to master and then deleted. 

So the change in question was a documentation correction. Corrected a typo related to the "encryption" setting. I think it would be nice to update this, even though there has not been a released change, because the current docs have a typo that tells the user to use a setting for encryption that doesn't exist and then their connection is unencrypted and they may not realize it, so it's a little dangerous for folks who are relying in security. 

Not sure if it's practical to update that one aspect of the docs without doing it whole-hog and pushing unreleased stuff. It's sort of a docs hotfix if you will and maybe you don't want to get into the business of doing that. 

-Marc
http://marc-abramowitz.com
Sent from my iPhone 4S


On Nov 16, 2013, at 7:14 AM, "James K. Lowden" <[email protected]> wrote:

> On Sun, 10 Nov 2013 12:07:47 -0800
> Marc Abramowitz <[email protected]> wrote:
> 
>> You might remember that I submitted a merge request to correct the
>> documentation for the "encryption" setting:
>> 
>> https://gitorious.org/freetds/freetds/merge_requests/9
>> 
>> and it was merged on 2013-10-19.
>> 
>> I just noticed that the documentation online never got updated:
>> 
>> http://www.freetds.org/userguide/freetdsconf.htm
>> 
>> Maybe someone needs to rerun a job to build and publish the docs?
> 
> Online docs refer to the current release.  Did your change affect the
> current release, or the git master branch?  
> 
> I tried to check that myself, but the "c8d6202" link on
> https://gitorious.org/freetds/freetds/merge_requests/9 -- which I
> assume should show a diff -- returns an nginx error to my browser.  
> 
> --jkl
> 
> _______________________________________________
> FreeTDS mailing list
> [email protected]
> http://lists.ibiblio.org/mailman/listinfo/freetds
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.