Azure / Azure/azure-functions-core-tools
func asks for a firewall exception with publisher: Unknown
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.5k
- Forks
- 498
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 16
Description
I just installed the Azure Functions CLI on my machine, and running it for the first time I got a request to add a firewall exception, which I might have been happy to do if the publisher were identified.
I've been told there's a problem with signing the CLI because of self-modifying code, but there's no way to verify that the tool I've got should be trusted with a firewall bypass:
- I downloaded it through
npm(which has good cause for needing signing) funcitself seems to give no indication of who's written or is responsible for it (there's no "Microsoft logo")- Windows does not recognise it as signed
- Running it for the first time asks for firewall access...
My fundamental issue is that the func CLI needs some way to establish a chain of trust, because (1) an npm typo is a pretty easy exploit and there's currently no way to effectively differentiate the legitimate product from an alternative, and (2) there are going to be users with Windows setups that won't be able to just run an unsigned thing and func is in the dependency chain for a few things.
Environment Information
Azure Functions Core Tools (2.4.419 Commit hash: c9c1724d002bd90b2e6b41393915ea3a26bcf0ce)
Function Runtime Version: 2.0.12332.0
> [System.Environment]::OSVersion
Platform ServicePack Version VersionString
-------- ----------- ------- -------------
Win32NT 10.0.18845.0 Microsoft Windows NT 10.0.18845.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Azure Functions Core Tools 2.4.419 and a Windows firewall prompt but no source file, test, or entry point. Start by locating the code that triggers the first-run firewall request; done means the CLI’s publisher can be verified and the trust concern is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- cli, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100