I could not see any communication with 68.142.91.87, or any other external IP during a first setup and running of gnucash-2.2.1.
I did a fresh install of Windows XP, installed Wireshark and started to capture packages. Then I ran the gnucash-2.2.1 intallation while capturing. Installation went fine, I stopped capturing, and when I checked the packets that Wireshark had cought. I could not see the IP 68.142.91.87, or any other suspicious IP address. I continued to capture packets and ran the newly installed gnucash-2.2.1 for the very first time, went through the druid for new accounts, saved and exited the program. Neither this time I could see any suspicious IP in the Wireshark capture. If the program was infected with a trojan/virus/worm/whatever, it could of course choose to run randomly, but personally I suspect that your connection to 68.142.91.87 came from another program. /Patrik On 8/31/07, Wm Stewart <[EMAIL PROTECTED]> wrote: > > I will file this as a new item once I find out where. Please note again > this is not a duplicate of the known issue you reference -- that issue does > not refer to surreptitious external IP connection as a requirement for > operation of the application. > > Christian Stimming wrote: > > If you want to discuss a bugzilla item, please keep this discussion on > > bugzilla. This is what this is for. > > > > Quoting Wm Stewart <[EMAIL PROTECTED]>: > >> Can someone explain why this bug has been closed, ignored? I honestly > >> thought after my first notification of surreptitious external IP > >> connection > >> three months ago that this would have been considered seriously by the > >> development team. Rather disillusioning - not sure why I would report > >> bugs > >> in the future if they are going to be treated like this... > >> > >> http://bugzilla.gnome.org/show_bug.cgi?id=407458#c14 > >> Please advise (a) why would you close a bug that indicates something > > > > 1. You added your comments to the wrong bug: The initial report is about > > the gconf-editor program, not gnucash. And I already explained this in > > comment 10 but you didn't react on this. > > > > 2. The data that has been provided so far indicates to me this is a > > DUPLICATE of a known issue, > > http://wiki.gnucash.org/wiki/Windows#GConf.2FORBit_COMM_FAILURE , and > > this is being discussed in other bugzilla items already. Hence, this bug > > must be closed to avoid duplicated discussions. > > > > 3. If you think you have discovered a bug that is not yet covered by the > > bug numbers mentioned in that wiki page, please file this as a *new* > > item. Thanks. > > > > Christian > > > _______________________________________________ > gnucash-devel mailing list > gnucash-devel@gnucash.org > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
