Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problems with microphone input and establishing SSL/TLS connections #57

Closed
CodingArctic-zz opened this issue Feb 9, 2021 · 4 comments
Closed

Problems with microphone input and establishing SSL/TLS connections #57

CodingArctic-zz opened this issue Feb 9, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@CodingArctic-zz
Copy link

Describe the bug

I just used the script, didn't choose any crazy options. but now no programs get input from my mic? I need to do zoom classes, and this is kind of a big problem.

OS

windows 10 20h2 19042.746

Scripts

privacy-script.zip

this was the script i ran (in zip form cause i cant upload .bat)

To Reproduce

Steps to reproduce the problem:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.
@CodingArctic-zz CodingArctic-zz added the bug Something isn't working label Feb 9, 2021
@CodingArctic-zz
Copy link
Author

CodingArctic-zz commented Feb 9, 2021 •
edited
Loading

this resolved itself?? also having another issue where my image is failing to upload in ShareX (my screenshotting program) (this issue wasn't present before)

image

@undergroundwires
Copy link
Owner

Hi @CodingArctic,

For first problem: it's probably Deny app access to microphone script as Zoom is probably . It should be solved if you revert it by searching for it, clicking on "revert" next to it and run the generated script. I'll add a warning icon next to those "breaking" scripts just to make it more clear.

For second problem: it seems like ShareX is using insecure protocols (see ShareX/ShareX#4518). You may want to revert "SMBv1 protocol" script and "Increase cryptography on ISS" category. However those protocols are deprecated, insecure and have known vulnerabilities enabling different attacks.

@undergroundwires undergroundwires changed the title help!! Problems with microphone input and establishing SSL/TLS connections Feb 12, 2021
@undergroundwires
Copy link
Owner

Closing this as this is not a bug caused by privacy.sexy but a problem with the project where it uses insecure protocol. I'd be happy if you could get back on whether the reverting the scripts mentioned in my last comment has solved your problem or re-open the issue if any additional help is needed.

undergroundwires added a commit that referenced this issue Apr 5, 2024
@undergroundwires
win: improve and document secret key scripts
49f22f0 
- Consolidate secret key improvement scripts into a single category.
- Simplify script names to improve user understanding.
- Expand and refine documentation, adding cautionary notes for clarity
  and helping users make informed decisions (addresses issues #57, #131,
  #175, #183).
- Adjust recommendation levels for scripts to 'Standard' to reflect
  their adoption in modern Windows and align with security standards:
  - Set Diffie-Hellman key exchange minimum to 2048 bits, matching
    modern Windows defaults
  - Align RSA key size with Microsoft's upcoming deprecation of 1024-bit
    keys.
- Improve the revert process by suppressing false error messages using
  `2>nul` in `reg delete` commands.
- Introduce a unified approach to adjust key sizes in key exchange
  algorithms with `RequireMinimumKeySize` function.
- Modify the Diffie-Hellman key exchange to a 2048-bit minimum instead
  of 4096 bits to balance security with broader software compatibility.
  This attempts to reduce side-effects on third-party software as
  reported in #57, #131, #183).
- Replace hexadecimal values with decimal equivalents in registry edits
  to facilitate better maintainability and readability.
undergroundwires added a commit that referenced this issue Apr 17, 2024
@undergroundwires
win: organize and document network disablement
2eed6f4 
Reorganize and document scripts for disabling network features,
enhancing their discoverability and manageability. This commit
categorizes scripts related to disabling insecure network connections,
improves documentation, and makes these scripts more accessible.

- Group scripts under `Disable insecure connections` category.
- Move SMBv1 and NetBios disablement scripts to this new category.
- Improve documentation, highlighting the security improvements
  and potential compatibility issues with older systems.

Addresses issues #57, #115, #183, #175, and #185 by simplifying the
process of troubleshooting and reversing changes if necessary.
undergroundwires added a commit that referenced this issue Apr 21, 2024
@undergroundwires
win: doc, improve, encourage cipher disabling
8b224ee 
- Introduce 'Disable insecure ciphers' category to organize and group
  cipher disabling scripts.
- Expand documentation, adding cautionary notes to help users make
  informed decisions, addressing issues #57, #131, #175, and #183.
- Implement `DisableCipherAlgorithm` function to standardize the
  approach to disabling cipher algorithms, enhancing maintainability
  and promoting code reuse.
- Replace hexadecimal numbers with decimals in scripts to improve
  readability.
- Add comments to generated code for better understandability.
- Update revert codes to avoid incorrect error messages when
  operations are successful, using `2>nul` in `reg delete` commands.
- Rename scripts for consistency, incorporating 'insecure' in titles.
- Adjust recommendations to disable all insecure ciphers in 'Strict'
  mode due to security risks, and recommend disabling `NULL` in
  'Standard' mode as it removes encryption.
- Remove disabling of `DES 56`, correcting a redundancy as this cipher
  configuration does not exist.
undergroundwires added a commit that referenced this issue Apr 27, 2024
@undergroundwires
win: improve disabling insecure hashes #131
d19dde6 
This commit addresses reports in issue #131 about third-party cloud
services like MEGA and Dropbox being affected by hash disabling. It
updates the documentation to guide users on the potential impact,
adjusts the recommendation levels along with other minor improvements.

- Recommend hash disabling scripts in 'Strict'.
- Expand and refine documentation, adding warnings to inform user
  decisions (addressing issues #57, #131, #175, #183).
- Add a new shared function to standardize hash disabling, increasing
  code maintainability.
- Change from hexadecimal to decimal in scripts for clarity.
- Improve code comments for better understanding.
- Add comments in generated to code to make it easier to follow.
- Fix revert codes showing errors by using `2>nul` in `reg delete`
  commands.
- Rename scripts for consistent naming conventions.

Supporting changes in other SSL/TLS handshake scripts:

- Update documentation for consistency.
- Rename shared functions for consistency and clarity.
- Improve generated code comments for clarity.
undergroundwires added a commit that referenced this issue May 1, 2024
@undergroundwires
win: improve disabling protocols
4ef16ce 
This commit groups scripts related to disabling protocols under same
category, streamlining the process for disabling protocols like NetBios,
SMBv1, and various TLS/SSL versions. It improves the documentation and
scripts of the related scripts.

Key changes:

- Introduce new category for disabling insecure protocols and move
  related scripts under it.
- Remove .NET configuration from TLS 1.0 disabling to prevent unwanted
  side effects on .NET applications, maintaining system integrity.
- Remove the script disabling DTLS 1.1 as this protocol does not exist.
- Recommend previously not recommended scripts:
  - SSL 2.0 in 'Standard' because it's already removed from Windows.
  - SSL 3.0 in 'Standard' because it's already disabled by default.
  - TLS 1.0 in 'Strict' as it's deprecated on Windows.
  - TLS 1.1 in 'Strict' as it's deprecated on Windows.
- Rename and reorder scripts for consistency and enhanced readability.
- Fix revert codes to accurately reflect successful operations, by
  adding `2>nul` on `reg delete` commands.
- Expand documentation to include detailed precautions and references,
  aiding users in understanding the implications of their actions
  (addressing user feedback from #57, #131, #183, #185).

Other supporting changes:

- Convert hexadecimal values to decimal to enhance script readability.
- Refactor scripts to utilize shared functions, improving maintainability.
- Add detailed comments within the scripts to aid in comprehension.
- Minor updates to other crypto scripts for consistency.
- Reorganize protocol listing by age for a logical script flow.
- Standardize comments across various TLS configuration scripts for
  clarity.
- Fix enabling DTLS 1.3 being categorized as disabling insecure
  connection.
@undergroundwires
Copy link
Owner

I've reworked network-related scripts completely in 0.13.3, it should solve this issue along with others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@undergroundwires @CodingArctic-zz