NoiseTorch

Summary

We finally fixed the update mechanism for good. This time the updater REALLY works and all future updates will be available through the UI. Please update a last time manually. Sorry for the issues with v0.12.1

What's Changed

• fix(update): strip 'v' from version string by @ZyanKLee, @AXDOOMER in http...

What's Changed

• Readme Modifications by @RiemaruKarurosu in https://github.com/noisetorch/NoiseTorch/pull/309
• Bump github.com/BurntSushi/toml from 0.4.1 to 1.1.0 by @dependabot in https://github.com/noisetorch/NoiseTorch/pull/294
• fix(dependabot): correct dir for submods & actions by @ZyanKLee in https://github.com/noisetorch/NoiseTorch/pull/313
• Bump david-a-wheeler/flawfinder from 2....

What's Changed

• update README.md by @ZyanKLee in https://github.com/noisetorch/NoiseTorch/pull/261
• feat(ci): run golangci-lint action by @ZyanKLee in https://github.com/noisetorch/NoiseTorch/pull/258
• feat(ci): add flawfinder action by @ZyanKLee in https://github.com/noisetorch/NoiseTorch/pull/259
• Update README.md by @Rififia in https://github.com/noisetorch/NoiseTorch/pull/280
• Min...

I HAVE REASON TO BELIEVE AT LEAST ONE OF MY SYSTEMS HOLDING KEY MATERIAL HAS BEEN COMPROMISED.

DO. NOT. TRUST. THE. BINARIES.

I'm deeply sorry about this, but it's better to be safe than sorry.

To make clear to everyone that I'm absolutely not joking:

$ base64 private.key 
RBjU5k0Dfdqtyzx4ox6PfQoqrdCft/aFJieD2DQvloY=

I'm publically leaking the key myself now. Don't trust...

• Update GUI dependency
• Update toml dependency
• Fix a warning with the Makefile, thank you @AdelKS
• The virtual device is now named "Noisetorch Microphone of [original device name]" in order to distinguish them in case you end up with multiple of them active.