Hi, > I will try to push for upstream to keep the default value to false. A > compromise position might be to have the first run dialog suggest that > it be enabled, but if the setting is ever deleted manually or corrupted > or unable to read in any way, it should always default to disabled. >
I've noticed this problem again on my current octave install. Triggering it is a little tricky, as it does not always pop up, but perhaps only launches if there is a change on the remote server. Do we know if there is a particular commit that upstream applied to fix this? Here is the info from my system $ octave --version GNU Octave, version 4.0.3 Copyright (C) 2016 John W. Eaton and others. This is free software; see the source code for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ... $ grep allow_web_connection ~/.config/octave/qt-settings $ $ head ~/.config/octave/qt-settings [General] connectOnStartup=true showMessageOfTheDay=true showTopic=true customFileEditor=emacs +%l %f autoIdentification=false useProxyServer=false proxyType= proxyHostName=none proxyPort=8080 $ $ apt show octave | head -n 5 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. Package: octave Version: 4.0.3-3 Priority: optional Section: math Maintainer: Debian Octave Group <pkg-octave-de...@lists.alioth.debian.org> $ In the QT UI, the "Allow Octave to connect to the Octave web site...." is unchecked, however periodically, I still receive updates from their remote website (new versions available). Is it an option to just patch out their network access entirely in the debian package? This would seem the much safer route, as accessing a random network resource on untrusted networks (even if you do have https, which I am unsure if it is the case), seems non-ideal, and contrary to policy. Thanks!
