LEleakbang·Jun 8, 2022Submission
1 points · Open discussionlawl
NoiseTorch
Security & Privacy2020–2022
lawl / NoiseTorch · Archived
NoiseTorch
Project dead (security breach)
21Distinct people
26Mentions
1Explicit recommenders
20GitHub stars
What to know before exploring
What it is
Project dead (security breach)
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
Not the OP, but I'd say noisetorch already works pretty good for that use case. Especially with the recent additions of pre-selecting the last device and stuff like that, I…
Dumbdo used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month26 dated mentions
Observed mentions: 2020-07-18 09:32:17 UTC to 2022-06-08 17:15:27 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Jul 2020 | 2020-07-01 00:00:00 UTC | 2020-08-01 00:00:00 UTC | 2 | 1 | 1 |
| Aug 2020 | 2020-08-01 00:00:00 UTC | 2020-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2020 | 2020-09-01 00:00:00 UTC | 2020-10-01 00:00:00 UTC | 2 | 0 | 2 |
| Oct 2020 | 2020-10-01 00:00:00 UTC | 2020-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2020 | 2020-11-01 00:00:00 UTC | 2020-12-01 00:00:00 UTC | 1 | 0 | 1 |
| Dec 2020 | 2020-12-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 1 | 0 |
| Jan 2021 | 2021-01-01 00:00:00 UTC | 2021-02-01 00:00:00 UTC | 5 | 0 | 5 |
| Feb 2021 | 2021-02-01 00:00:00 UTC | 2021-03-01 00:00:00 UTC | 1 | 0 | 1 |
| Mar 2021 | 2021-03-01 00:00:00 UTC | 2021-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2021 | 2021-04-01 00:00:00 UTC | 2021-05-01 00:00:00 UTC | 1 | 0 | 1 |
| May 2021 | 2021-05-01 00:00:00 UTC | 2021-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2021 | 2021-06-01 00:00:00 UTC | 2021-07-01 00:00:00 UTC | 0 | 0 | 0 |
| Jul 2021 | 2021-07-01 00:00:00 UTC | 2021-08-01 00:00:00 UTC | 0 | 0 | 0 |
| Aug 2021 | 2021-08-01 00:00:00 UTC | 2021-09-01 00:00:00 UTC | 0 | 0 | 0 |
| Sep 2021 | 2021-09-01 00:00:00 UTC | 2021-10-01 00:00:00 UTC | 0 | 0 | 0 |
| Oct 2021 | 2021-10-01 00:00:00 UTC | 2021-11-01 00:00:00 UTC | 0 | 0 | 0 |
| Nov 2021 | 2021-11-01 00:00:00 UTC | 2021-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2021 | 2021-12-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 2 | 1 | 1 |
| Jan 2022 | 2022-01-01 00:00:00 UTC | 2022-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2022 | 2022-02-01 00:00:00 UTC | 2022-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2022 | 2022-03-01 00:00:00 UTC | 2022-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2022 | 2022-04-01 00:00:00 UTC | 2022-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2022 | 2022-05-01 00:00:00 UTC | 2022-06-01 00:00:00 UTC | 10 | 4 | 6 |
| Jun 2022 | 2022-06-01 00:00:00 UTC | 2022-07-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
26 sourcesBetter link would be https://github.com/lawl/NoiseTorch
> At least one of my sytems has probably been compromised, dont use the source either. One could hide things in a large diff.
> If the community can help review ALL of the code, maybe we can trust the codw again and work from there.
> To help go here: #254 (comment)
#254 is what the submission link links to, but it's missing the context that the README has.
In NoiseTorch pauses development due to compromised workstationNoiseTorch pauses development due to compromised workstation
3 points · Open discussionAlso what is the reason behind packing open-source project with UPX ?
https://github.com/lawl/NoiseTorch/issues/254#issuecomment-1...
Also this is very good example, why everyone should use VM for browsing internet, or better yet - different machine.
If you're popular enough, there alway be people who will use that $1mil RCE on you.
In A key-infra open-source project can get compromisedThe actual content is here: https://github.com/lawl/NoiseTorch
The article just (badly) sums up what you can find in the release notes, the issues, and the readme.
In A key-infra open-source project can get compromisedThere is more detail in the related repo issue. My read was the devs computer was compromised but doesn't know if/what else was done.
https://github.com/lawl/NoiseTorch/issues/254#issuecomment-1...
In A key-infra open-source project can get compromised> 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 it.
What?
https://github.com/lawl/NoiseTorch/releases/tag/0.11.6
In A key-infra open-source project can get compromisedLooks like the dev's computer got compromised, maybe by someone looking for bitcoin wallets. See here: https://github.com/lawl/NoiseTorch/issues/254
In A key-infra open-source project can get compromisedAsk HN: Noisetorch could be compromised, what can be done to audit it right?
As the maintainer pointed out, one of his systems was compromised.
What can be done to audit it properly? I would love some feedback from people in security area, however any tip (even if you are not experienced is welcome).
Related issue in this audit: https://github.com/lawl/NoiseTorch/issues/254
3 points · Open discussionNoisetorch Possibly Compromised
6 points · Open discussionReal-time microphone noise suppression on Linux
3 points · Open discussionEarlier this year I got a ReSpeaker mic for video conferencing, and it's been working great! I did have to upload the latest firmware once I got it. I then combined it with NoiseTorch for a basically perfect video chatting experience.
NoiseTorch detects speech and mutes the mic when you aren't speaking. I had tried Hushboard, which mutes the mic when you are typing, but sometimes I talk when I type. ReSpeaker is a microphone array, and it has a speaker output and can do noise cancelling on the mic from what is sent to the speaker. It was about $60.
https://www.seeedstudio.com/ReSpeaker-USB-Mic-Array-p-4247.h...
https://github.com/lawl/NoiseTorch
https://www.kryogenix.org/code/hushboard/
In Mico: A PDM to USB Microphone Based on the Raspberry Pi RP2040(NoiseTorch maintainer here)
This is a limitation that will likely be lifted with the pipewire version. Pipewire 0.3.25 released yesterday which added some of the things we require, still some other things missing, but it seems like things are happening.
In the meantime it is possible to configure NoiseTorch as a systemd service[0], but it's not recommended because it constantly uses CPU even if no application is actually using the microphone. Afaik PipeWire uses a pull model where it pulls data when it needs it, so it shouldn't use CPU to denoise the microphone when it's not in use.
So it is currently possible to do that, but I'm deliberately not making it easy via the UI, because I don't want to deal with complaints about NoiseTorch killing people's laptop batteries or whatever.
[0]: https://github.com/lawl/NoiseTorch/wiki/Start-automat
Read the rest
Just tried the pulseaudio https://github.com/lawl/NoiseTorch and I must say it makes an astonishing difference:
https://www.youtube.com/watch?v=5rAfyMrE49o&feature=youtu.be
Though basics of getting dynamic microphone close to my mouse is probably bigger, hah
In Show HN: Alsa_rnnoise – RNNoise-based noise removal plugin for ALSAShowing the 15 most recent of 26 sources. Enable JavaScript to search and browse every indexed mention.