# proxy_windows_386.exe Firewall Notification 3 messages from 2015-06-11 to 2015-06-11. Participants: BGaudreault Brian, Konstantin Khomoutov. Thread: https://gitlist.dev/t/39603 ## BGaudreault Brian, 2015-06-11 17:46 Subject: proxy_windows_386.exe Firewall Notification Message-ID: URL: https://gitlist.dev/e/BLUPR0701MB196906E314F2F1083B5DEC2BD7BC0%40BLUPR0701MB1969.namprd07.prod.outlook.com ``` Hello, when connecting to a Vagrant Shared VM via SSH, I'm getting a Windows Firewall prompt about 'proxy_windows_386.exe' (in C:\Program Files\hashicorp\vagrant\embedded\gems\gems\vagrant-share-1.1.0\localbin\), which looks like a malware-type name. Here's the message: "Windows Security Alert. Windows Firewall has blocked some features of this app. Windows Firewall has blocked some features of proxy_windows_386.exe on all public and private networks.". So I did a quick search for this file name on the Internet as well as the Git-SCM.com/community site and haven't found any clear explinations about what this file is and if it's safe. If this is a legitimate safe file, I think it's important that this is clearly documented in the Git documentation. Can someone verify the details about this file? Thanks, BRIAN ``` ## Konstantin Khomoutov, 2015-06-11 19:43 Subject: Re: proxy_windows_386.exe Firewall Notification Message-ID: <20150611224305.ac126629f69dbb915bdc8851@domain007.com> URL: https://gitlist.dev/e/20150611224305.ac126629f69dbb915bdc8851%40domain007.com In-Reply-To: ``` On Thu, 11 Jun 2015 17:46:58 +0000 BGaudreault Brian wrote: > Hello, when connecting to a Vagrant Shared VM via SSH, I'm getting a > Windows Firewall prompt about 'proxy_windows_386.exe' (in C:\Program > Files\hashicorp\vagrant\embedded\gems\gems\vagrant-share-1.1.0 > \localbin\), which looks like a malware-type name. Here's the > message: "Windows Security Alert. Windows Firewall has blocked some > features of this app. Windows Firewall has blocked some features of > proxy_windows_386.exe on all public and private networks.". > > So I did a quick search for this file name on the Internet as well as > the Git-SCM.com/community site and haven't found any clear > explinations about what this file is and if it's safe. If this is a > legitimate safe file, I think it's important that this is clearly > documented in the Git documentation. Can someone verify the details > about this file? I fail to get how did you manage to connect "proxy_windows_386.exe" with Git. Care to elaborate on this? ``` ## BGaudreault Brian, 2015-06-11 19:57 Subject: RE: proxy_windows_386.exe Firewall Notification Message-ID: URL: https://gitlist.dev/e/BLUPR0701MB1969F0D63174D70566496694D7BC0%40BLUPR0701MB1969.namprd07.prod.outlook.com In-Reply-To: <20150611224305.ac126629f69dbb915bdc8851@domain007.com> ``` Lol, sorry. I meant to post in the Vagrant forums. Too many projects going on at the same time! -----Original Message----- From: Konstantin Khomoutov [mailto:kostix+git@007spb.ru] Sent: Thursday, June 11, 2015 3:43 PM To: BGaudreault Brian Cc: git@vger.kernel.org Subject: Re: proxy_windows_386.exe Firewall Notification On Thu, 11 Jun 2015 17:46:58 +0000 BGaudreault Brian wrote: > Hello, when connecting to a Vagrant Shared VM via SSH, I'm getting a > Windows Firewall prompt about 'proxy_windows_386.exe' (in C:\Program > Files\hashicorp\vagrant\embedded\gems\gems\vagrant-share-1.1.0 > \localbin\), which looks like a malware-type name. Here's the > message: "Windows Security Alert. Windows Firewall has blocked some > features of this app. Windows Firewall has blocked some features of > proxy_windows_386.exe on all public and private networks.". > > So I did a quick search for this file name on the Internet as well as > the Git-SCM.com/community site and haven't found any clear > explinations about what this file is and if it's safe. If this is a > legitimate safe file, I think it's important that this is clearly > documented in the Git documentation. Can someone verify the details > about this file? I fail to get how did you manage to connect "proxy_windows_386.exe" with Git. Care to elaborate on this? ```