On 10/14/2016 12:20 PM, Andy Bradford wrote:
Thus said Ross Berteig on Fri, 14 Oct 2016 12:14:03 -0700:
Something made the Windows Firewall fussier, and I had to reassure it
during both test suite runs that yes, it was ok to let fossil.exe do
something. The prompt came a long ways in to the suite, but I didn't
check the prot file to see what test had prompted it. If that behavior
continues, it will make launching a bunch of builds and walking away a
lot less productive.
Dare you turn off Admin Approval Mode in User Account Control settings
in secpol.msc? (assuming that's where it is still found with Windows
10).
I don't know. I am my own IT department, so I get to decide what risks I
take. I'll have to think about that, but that certainly is one way
around it.
I can say that Windows Firewall's list of programs "allowed to
communicate through Windows Firewall" has a horrifically bad UI. It now
has a bunch of rows in the list that all say just "fossil.exe". A
Details button allows you to discover the full path to it by opening a
box allowing you to edit some of the properties WF knows. But the OK
button in that box re-orders the list of "fossil.exe" entries. Frustrating.
I don't know if there's anything at all that we can do to make that
control more pleasant. Other items in that list have more friendly
names. I'm not sure where those names came from, and if we could have
one too. I'll poke at that sore spot in a while.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
