git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: proxy_windows_386.exe Firewall Notification

From
KKKonstantin Khomoutov <kostix+git@007spb.ru>
Date
Jun 11, 2015, 19:43 UTC
Message-ID
<20150611224305.ac126629f69dbb915bdc8851@domain007.com>
In-Reply-To
<BLUPR0701MB196906E314F2F1083B5DEC2BD7BC0@BLUPR0701MB1969.namprd07.prod.outlook.com>

On Thu, 11 Jun 2015 17:46:58 +0000 BGaudreault Brian <BGaudreault@edrnet.com> wrote:

Show 14 quoted lines
> 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?

Previous: BGaudreault BrianNext: BGaudreault Brian
Message 2 of 3 in “proxy_windows_386.exe Firewall Notification”
  1. BGaudreault BrianJun 11, 2015
  2. Konstantin KhomoutovJun 11, 2015
  3. BGaudreault BrianJun 11, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.