|
|
Does anyone have the solution to stopping FileZilla from phoning home?
I don't want any app updating or phoning home unless/until I ask it to.
(Which is pretty much, never.) Yet, FileZilla keeps trying to update. http://i.cubeupload.com/P3qVra.jpg I keep trying to stop it from updating. But it's not working. Does anyone have the solution to stopping FileZilla from phoning home? |
Does anyone have the solution to stopping FileZilla from phoninghome?
Ragnusen Ultred wrote:
I don't want any app updating or phoning home unless/until I ask it to. (Which is pretty much, never.) Yet, FileZilla keeps trying to update. http://i.cubeupload.com/P3qVra.jpg I keep trying to stop it from updating. But it's not working. Does anyone have the solution to stopping FileZilla from phoning home? Looking up a solution, says to: 1) Edit : Settings : Updates and set to Never. And who knows where that is actually stored. If it's in Filezilla.xml, it might be better to implement both fixes as a text edit of the XML. 2) Filezilla.xml Setting name="Update Check New Version" Change the string so it no longer matches. Setting name="Update Check New Version2" 3) In the Help menu, *don't* select Check For Updates because it will "heal" the Filezilla.xml file. I think the idea is, when it checks for updates in Step 1, it records the result in Filezilla.xml. It will then continue attempting to download a new EXE, no matter what (based on the shopping list stored in the entry in [2] ). Once the downloaded EXE loads, it will "heal" the Filezilla.xml. Setting the Update to Never, followed by preventing the app from seeing "queued up Update to process", may get you off the update squirrel cage, which is only there to generate advertising views. Paul |
Does anyone have the solution to stopping FileZilla from phoning home?
Am Fri, 13 Apr 2018 23:36:13 -0400, schrieb Paul:
Looking up a solution, says to: 1) Edit : Settings : Updates and set to Never. Thanks Paul for all your very helpful information! (which will help others also - so I will try every valid suggestion and report back the results to save everyone else the effort) As you will soon be aware, the setting above doesn't work. It's the first thing anyone tries, and I tried it, long ago, many times, but it keeps resetting itself. Why? I don't know why. That's why I'm asking. :) And who knows where that is actually stored. If it's in Filezilla.xml, it might be better to implement both fixes as a text edit of the XML. Yup. On some programs, like Opera, you can kill the updater executable. But on FileZilla, I don't know what the update executable is. http://i.cubeupload.com/wU5CNM.jpg 2) Filezilla.xml Setting name="Update Check New Version" Change the string so it no longer matches. Setting name="Update Check New Version2" Hmmmm.... that looks like a good answer. Let me look for this "xml" file. dir c:\app\network\filezilla\ /s/b c:\tmp\filezilla.txt Using "vi" to search for a case-insensitive xml, I only find: :set ignorecase /xml next == I wish Windows 10 had an "easy" grep! :( Which results in these dozen files: c:\app\network\filezilla\docs\fzdefaults.xml.examp le c:\app\network\filezilla\resources\defaultfilters. xml c:\app\network\filezilla\resources\blukis\theme.xm l c:\app\network\filezilla\resources\classic\theme.x ml c:\app\network\filezilla\resources\cyril\theme.xml c:\app\network\filezilla\resources\default\theme.x ml c:\app\network\filezilla\resources\flatzilla\theme .xml c:\app\network\filezilla\resources\lone\theme.xml c:\app\network\filezilla\resources\minimal\theme.x ml c:\app\network\filezilla\resources\opencrystal\the me.xml c:\app\network\filezilla\resources\sun\theme.xml c:\app\network\filezilla\resources\tango\theme.xml There are xml files elesewhere though. dir c:\ /b/s c:\tmp\xmlfiles.txt Such as: C:\Users\ultred\AppData\Roaming\FileZilla\bookmark s.xml C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml C:\Users\ultred\AppData\Roaming\FileZilla\layout.x ml C:\Users\ultred\AppData\Roaming\FileZilla\recentse rvers.xml 3) In the Help menu, *don't* select Check For Updates because it will "heal" the Filezilla.xml file. Hmmmmm... maybe *that* is why the setting has been useless for so long! I hadn't noticed if I'm doing that, but I certainly keep telling FileZilla to stop checking for updates until I finally gave up on the setting since the setting wasn't being honored. Is there an easy way to "lock" the xml file so that it can't "heal"? C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml I think the idea is, when it checks for updates in Step 1, it records the result in Filezilla.xml. It will then continue attempting to download a new EXE, no matter what (based on the shopping list stored in the entry in [2] ). Once the downloaded EXE loads, it will "heal" the Filezilla.xml. This may be the case Paul, because FileZilla does *not* respect the setting, that's for sure. Setting the Update to Never, followed by preventing the app from seeing "queued up Update to process", may get you off the update squirrel cage, which is only there to generate advertising views. You understand that I want out of the hamster cage! Here's the update setting in "filezilla.xml" before I changed it: C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml Setting name="Update Check"0/Setting Setting name="Update Check Interval"7/Setting Setting name="Last automatic update check"2018-04-13 17:28:21/Setting Setting name="Last automatic update version"3.31.0/Setting Setting name="Update Check New Version"nightly 2018-04-13 http://filezilla-project.org/nightli...la_3_setup.exe (long set of hex characters) https://dl3.cdn.filezilla-project.or...in64-setup.exe (more long set of hex characters) I only added the words "DO NOT" to the following: Setting name="Update DO NOT Check New Version" I left the rest alone. Is that what you were suggesting? |
Does anyone have the solution to stopping FileZilla from phoning home?
Am Fri, 13 Apr 2018 23:36:13 -0400, schrieb Paul:
Looking up a solution, says to: 1) Edit : Settings : Updates and set to Never. Thanks Paul for all your very helpful information! (which will help others also - so I will try every valid suggestion and report back the results to save everyone else the effort) As you will soon be aware, the setting above doesn't work. It's the first thing anyone tries, and I tried it, long ago, many times, but it keeps resetting itself. Why? I don't know why. That's why I'm asking. :) And who knows where that is actually stored. If it's in Filezilla.xml, it might be better to implement both fixes as a text edit of the XML. Yup. On some programs, like Opera, you can kill the updater executable. But on FileZilla, I don't know what the update executable is. http://i.cubeupload.com/wU5CNM.jpg 2) Filezilla.xml Setting name="Update Check New Version" Change the string so it no longer matches. Setting name="Update Check New Version2" Hmmmm.... that looks like a good answer. Let me look for this "xml" file. dir c:\app\network\filezilla\ /s/b c:\tmp\filezilla.txt Using "vi" to search for a case-insensitive xml, I only find: :set ignorecase /xml next == I wish Windows 10 had an "easy" grep! :( Which results in these dozen files: c:\app\network\filezilla\docs\fzdefaults.xml.examp le c:\app\network\filezilla\resources\defaultfilters. xml c:\app\network\filezilla\resources\blukis\theme.xm l c:\app\network\filezilla\resources\classic\theme.x ml c:\app\network\filezilla\resources\cyril\theme.xml c:\app\network\filezilla\resources\default\theme.x ml c:\app\network\filezilla\resources\flatzilla\theme .xml c:\app\network\filezilla\resources\lone\theme.xml c:\app\network\filezilla\resources\minimal\theme.x ml c:\app\network\filezilla\resources\opencrystal\the me.xml c:\app\network\filezilla\resources\sun\theme.xml c:\app\network\filezilla\resources\tango\theme.xml There are xml files elesewhere though. dir c:\ /b/s c:\tmp\xmlfiles.txt Such as: C:\Users\ultred\AppData\Roaming\FileZilla\bookmark s.xml C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml C:\Users\ultred\AppData\Roaming\FileZilla\layout.x ml C:\Users\ultred\AppData\Roaming\FileZilla\recentse rvers.xml 3) In the Help menu, *don't* select Check For Updates because it will "heal" the Filezilla.xml file. Hmmmmm... maybe *that* is why the setting has been useless for so long! I hadn't noticed if I'm doing that, but I certainly keep telling FileZilla to stop checking for updates until I finally gave up on the setting since the setting wasn't being honored. Is there an easy way to "lock" the xml file so that it can't "heal"? C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml I think the idea is, when it checks for updates in Step 1, it records the result in Filezilla.xml. It will then continue attempting to download a new EXE, no matter what (based on the shopping list stored in the entry in [2] ). Once the downloaded EXE loads, it will "heal" the Filezilla.xml. This may be the case Paul, because FileZilla does *not* respect the setting, that's for sure. Setting the Update to Never, followed by preventing the app from seeing "queued up Update to process", may get you off the update squirrel cage, which is only there to generate advertising views. You understand that I want out of the hamster cage! Here's the update setting in "filezilla.xml" before I changed it: C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml Setting name="Update Check"0/Setting Setting name="Update Check Interval"7/Setting Setting name="Last automatic update check"2018-04-13 17:28:21/Setting Setting name="Last automatic update version"3.31.0/Setting Setting name="Update Check New Version"nightly 2018-04-13 http://filezilla-project.org/nightli...la_3_setup.exe (long set of hex characters) https://dl3.cdn.filezilla-project.or...in64-setup.exe (more long set of hex characters) I only added the words "DO NOT" to the following: Setting name="Update DO NOT Check New Version" I left the rest alone. Is that what you were suggesting? |
Does anyone have the solution to stopping FileZilla from phoning home?
On 14 Apr 2018, Ragnusen Ultred wrote in
alt.comp.os.windows-10: As you will soon be aware, the setting above doesn't work. I've used Filezilla for years on many computers, and it has always respected the "Never check for updates" setting. It has never "reset" itself. |
Does anyone have the solution to stopping FileZilla from phoninghome?
Ragnusen Ultred wrote:
Am Fri, 13 Apr 2018 23:36:13 -0400, schrieb Paul: Looking up a solution, says to: 1) Edit : Settings : Updates and set to Never. Thanks Paul for all your very helpful information! (which will help others also - so I will try every valid suggestion and report back the results to save everyone else the effort) As you will soon be aware, the setting above doesn't work. It's the first thing anyone tries, and I tried it, long ago, many times, but it keeps resetting itself. Why? I don't know why. That's why I'm asking. :) And who knows where that is actually stored. If it's in Filezilla.xml, it might be better to implement both fixes as a text edit of the XML. Yup. On some programs, like Opera, you can kill the updater executable. But on FileZilla, I don't know what the update executable is. http://i.cubeupload.com/wU5CNM.jpg 2) Filezilla.xml Setting name="Update Check New Version" Change the string so it no longer matches. Setting name="Update Check New Version2" Hmmmm.... that looks like a good answer. Let me look for this "xml" file. dir c:\app\network\filezilla\ /s/b c:\tmp\filezilla.txt Using "vi" to search for a case-insensitive xml, I only find: :set ignorecase /xml next == I wish Windows 10 had an "easy" grep! :( Which results in these dozen files: c:\app\network\filezilla\docs\fzdefaults.xml.examp le c:\app\network\filezilla\resources\defaultfilters. xml c:\app\network\filezilla\resources\blukis\theme.xm l c:\app\network\filezilla\resources\classic\theme.x ml c:\app\network\filezilla\resources\cyril\theme.xml c:\app\network\filezilla\resources\default\theme.x ml c:\app\network\filezilla\resources\flatzilla\theme .xml c:\app\network\filezilla\resources\lone\theme.xml c:\app\network\filezilla\resources\minimal\theme.x ml c:\app\network\filezilla\resources\opencrystal\the me.xml c:\app\network\filezilla\resources\sun\theme.xml c:\app\network\filezilla\resources\tango\theme.xml There are xml files elesewhere though. dir c:\ /b/s c:\tmp\xmlfiles.txt Such as: C:\Users\ultred\AppData\Roaming\FileZilla\bookmark s.xml C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml C:\Users\ultred\AppData\Roaming\FileZilla\layout.x ml C:\Users\ultred\AppData\Roaming\FileZilla\recentse rvers.xml 3) In the Help menu, *don't* select Check For Updates because it will "heal" the Filezilla.xml file. Hmmmmm... maybe *that* is why the setting has been useless for so long! I hadn't noticed if I'm doing that, but I certainly keep telling FileZilla to stop checking for updates until I finally gave up on the setting since the setting wasn't being honored. Is there an easy way to "lock" the xml file so that it can't "heal"? C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml I think the idea is, when it checks for updates in Step 1, it records the result in Filezilla.xml. It will then continue attempting to download a new EXE, no matter what (based on the shopping list stored in the entry in [2] ). Once the downloaded EXE loads, it will "heal" the Filezilla.xml. This may be the case Paul, because FileZilla does *not* respect the setting, that's for sure. Setting the Update to Never, followed by preventing the app from seeing "queued up Update to process", may get you off the update squirrel cage, which is only there to generate advertising views. You understand that I want out of the hamster cage! Here's the update setting in "filezilla.xml" before I changed it: C:\Users\ultred\\AppData\Roaming\FileZilla\filezil la.xml Setting name="Update Check"0/Setting Setting name="Update Check Interval"7/Setting Setting name="Last automatic update check"2018-04-13 17:28:21/Setting Setting name="Last automatic update version"3.31.0/Setting Setting name="Update Check New Version"nightly 2018-04-13 http://filezilla-project.org/nightli...la_3_setup.exe (long set of hex characters) https://dl3.cdn.filezilla-project.or...in64-setup.exe (more long set of hex characters) I only added the words "DO NOT" to the following: Setting name="Update DO NOT Check New Version" I left the rest alone. Is that what you were suggesting? Having done that, removed its queued info, shouldn't you be able to start it and notice it is silent now ? The idea is, once you've done the two steps, it should stop with the updates. Paul |
Does anyone have the solution to stopping FileZilla from phoning home?
Am Sat, 14 Apr 2018 03:01:22 -0400, schrieb Paul:
Having done that, removed its queued info, shouldn't you be able to start it and notice it is silent now ? The idea is, once you've done the two steps, it should stop with the updates. Well, it already has the update. So it complained, when I just started it, asking me to install the updates. So, nothing has changed. I should mention that I've turned off updates so many times that I've given up turning off updates. I asked here in desperation... Maybe what I'll do is uninstall it, and then re-install it (so that the new update isn't always waiting). Or maybe just delete the new update. Let me see where it went (since I didn't ask for it). Ok. I found it in C:\Users\Ultred\Downloads\FileZilla_3.32.0_win64-setup.exe I deleted that. When I restarted FileZilla, it still popped up that damn form. I was hoping it would fail so I hit the only button available, but it seems to have tricked me (yet again0 and updated. Sigh. I checked the XML file, and it *changed* it, dammit. Setting name="Update Check New Version" This is so frustrating because it updates even when you tell it not to. |
Does anyone have the solution to stopping FileZilla from phoning home?
Am Sat, 14 Apr 2018 01:24:10 -0400, schrieb Nil:
I've used Filezilla for years on many computers, and it has always respected the "Never check for updates" setting. It has never "reset" itself. What version are you on? |
Does anyone have the solution to stopping FileZilla from phoninghome?
Ragnusen Ultred wrote:
Am Sat, 14 Apr 2018 03:01:22 -0400, schrieb Paul: Having done that, removed its queued info, shouldn't you be able to start it and notice it is silent now ? The idea is, once you've done the two steps, it should stop with the updates. Well, it already has the update. So it complained, when I just started it, asking me to install the updates. So, nothing has changed. I should mention that I've turned off updates so many times that I've given up turning off updates. I asked here in desperation... Maybe what I'll do is uninstall it, and then re-install it (so that the new update isn't always waiting). Or maybe just delete the new update. Let me see where it went (since I didn't ask for it). Ok. I found it in C:\Users\Ultred\Downloads\FileZilla_3.32.0_win64-setup.exe I deleted that. When I restarted FileZilla, it still popped up that damn form. I was hoping it would fail so I hit the only button available, but it seems to have tricked me (yet again0 and updated. Sigh. I checked the XML file, and it *changed* it, dammit. Setting name="Update Check New Version" This is so frustrating because it updates even when you tell it not to. You can place an entry in the HOSTS file to prevent it from reaching its destination. In retaliation, expect it to take longer starting up. To understand what to block, fire up Wireshark, start a trace, then start FileZilla and see what URLs it sends out. Then you can block those in the HOSTS file and try again. Paul |
Does anyone have the solution to stopping FileZilla from phoninghome?
On 4/14/2018 1:03 AM, Paul wrote:
Ragnusen Ultred wrote: Am Sat, 14 Apr 2018 03:01:22 -0400, schrieb Paul: Having done that, removed its queued info, shouldn't you be able to start it and notice it is silent now ? The idea is, once you've done the two steps, it should stop with the updates. Well, it already has the update. So it complained, when I just started it, asking me to install the updates. So, nothing has changed. I should mention that I've turned off updates so many times that I've given up turning off updates. I asked here in desperation... Maybe what I'll do is uninstall it, and then re-install it (so that the new update isn't always waiting). Or maybe just delete the new update. Let me see where it went (since I didn't ask for it). Ok. I found it in C:\Users\Ultred\Downloads\FileZilla_3.32.0_win64-setup.exe I deleted that. When I restarted FileZilla, it still popped up that damn form. I was hoping it would fail so I hit the only button available, but it seems to have tricked me (yet again0 and updated. Sigh. I checked the XML file, and it *changed* it, dammit. Â*Setting name="Update Check New Version" This is so frustrating because it updates even when you tell it not to. You can place an entry in the HOSTS file to prevent it from reaching its destination. In retaliation, expect it to take longer starting up. To understand what to block, fire up Wireshark, start a trace, then start FileZilla and see what URLs it sends out. Then you can block those in the HOSTS file and try again. Â*Â* Paul I used to use FileZilla, but at that time (not sure if it's still true) it saved passwords unencrypted, so I switched to FileZilla Secure, I don't know if it phones home or not. http://www.filezillasecure.com/ |
Does anyone have the solution to stopping FileZilla from phoninghome?
On 4/13/2018 11:36 PM, Paul wrote:
Setting the Update to Never, followed by preventing the app from seeing "queued up Update to process", may get you off the update squirrel cage, which is only there to generate advertising views. Â*Â* Paul What "advertising views" are you seeing? I let FileZilla update whenever it wants to, and only see the repairs and modifications, never any ads. -- best regards, Neil |
Does anyone have the solution to stopping FileZilla from phoninghome?
On 04/14/2018 12:33 AM, Ragnusen Ultred wrote:
Using "vi" to search for a case-insensitive xml, I only find: :set ignorecase /xml next == I wish Windows 10 had an "easy" grep!:( Any good text editor will let you search, ctrl+F normally, and case insensitive. http://gnuwin32.sourceforge.net/packages/grep.htm Seems to look favorable. Windows 10 has a Linux shell now and it should have the simple commands like grep. Or at least it's in the Insider only maybe, not sure, I don't keep up with it more than an occasional paragraph to skip over as I read. Al. |
Does anyone have the solution to stopping FileZilla from phoning home?
"Ragnusen Ultred" wrote
| | I've used Filezilla for years on many computers, and it has always | respected the "Never check for updates" setting. It has never "reset" | itself. | | What version are you on? I'm on 3.7.3. I've never seen any attempt to update. For the record, I'm entering that info as my current contribution to your tribe's collective data trove. :) |
Does anyone have the solution to stopping FileZilla from phoninghome?
Neil wrote:
On 4/13/2018 11:36 PM, Paul wrote: Setting the Update to Never, followed by preventing the app from seeing "queued up Update to process", may get you off the update squirrel cage, which is only there to generate advertising views. Paul What "advertising views" are you seeing? I let FileZilla update whenever it wants to, and only see the repairs and modifications, never any ads. It's in the OPs picture. https://i.cubeupload.com/P3qVra.jpg Paul |
Does anyone have the solution to stopping FileZilla from phoninghome?
On 04/14/2018 10:09 AM, Paul wrote:
It'sÂ*inÂ*theÂ*OPsÂ*picture. https://i.cubeupload.com/P3qVra.jpg Â*Â*Â*Paul How long does cubeupload.com save this pics? I've been looking for that simple place to put temp images. This looks easy to get to and use. I like that it leaves no link to "me". |
| All times are GMT +1. The time now is 07:11 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright © 2004 - 2006 PCbanter
Comments are property of their posters