mike.jacobson wrote:
Terrific! another portable app!..but this one worries me a little...it goes like this...I really have no idea about ports, and ma probably holding the wrong end of the stick here, but when I run GNUcash portable it 'requires' access to port 1060 on startup and port 1072 on closedown. If I don't give it access to this on startup, it ends with some obscure runtime error. On closedown it seems to want access to port 1072.
On starting Gnucash portable my firewall says something like
do you want the following access: GNUcash -bin.exe localhost 127.0.0.1 port 1060
..and on exit
do you want the following access: GConf -2.exe localhost 127.0.0.1 port 1072
This makes me suspicious....and probably for no good reason, so sorry if I sound distrustful, it's just that most everything else I use does not require such access. Would you care to put my mind at rest on this one? i run Windows XP pro and an old free version of the kerio firewall.
Mike, this is due to GnuCash using GConf for its configuration settings management. GConf is the Gnome configuration library and it utilizes TCP/IP sockets on the localhost as its chosen method of inter-process communications. I believe this is because sockets are fairly platform independent. Most windows apps use built in windows interprocess communication methods (COM, OLE, DDE, etc) since few are made to be cross-platform, thus the usual lack of warnings from your firewall for most apps. In this case the access is indeed harmless, and necessary for GnuCash to be able to access & save settings.