Details for the issue

When initially installed on MacOS, the checkversion.enabled preference defaults to true. This causes DB4S to attempt to connect to githubusercontent.com to check for a newer version. If you are working at a place with a man-in-the-middle HTTPS proxy, the proxy returns an SSL certificate that is not valid for githubusercontent.com, which causes an error in DB4S that causes it to immediately close. Users in such a situation can not get DB4S to start, so they are unable to change the setting from within DB4S. The workaround for this is to use the command line preferences editor on MacOS. This command will disable the version check:

defaults write "com.sqlitebrowser.sqlitebrowser" checkversion.enabled -bool false

DB4S should catch the SSL certificate error and ignore it. Optionally, when there is an SSL certificate error open a dialog to warn the user and give instructions to disable the new version check.

Useful extra information

I'm opening this issue because:

• DB4S is crashing
• DB4S has a bug
• DB4S needs a feature
• DB4S has another problem

I'm using DB4S on:

• Windows: ( version: ___ )
• Linux: ( distro: ___ )
• Mac OS: ( 10.11.6 El Capitan )
• Other: ___

I'm using DB4S version:

• 3.10.1
• 3.10.0
• 3.9.1
• Other: ___

I have also:

• Tried out the latest nightly version: https://github.com/sqlitebrowser/sqlitebrowser#nightly-builds
• Searched for an existing similar issue: https://github.com/sqlitebrowser/sqlitebrowser/issues?utf8=%E2%9C%93&q=is%3Aissue%20