password-manager-resources
msquic
Our great sponsors
password-manager-resources | msquic | |
---|---|---|
19 | 19 | |
4,020 | 3,833 | |
1.4% | 2.0% | |
7.8 | 9.6 | |
17 days ago | 4 days ago | |
JavaScript | C | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
password-manager-resources
-
Don't Fuck with Paste
Even Apple was so annoyed at this themselves that they actually went for a full open-source open-for-contributions GitHub repository at https://github.com/apple/password-manager-resources to get around these issues.
> Many password managers generate strong, unique passwords for people so that they aren't tempted to create their passwords by hand, which leads to easily guessed and reused passwords. Every time a password manager generates a password that isn't compatible with a website, a person not only has a bad experience but a reason to be tempted to create their password. Compiling password rule quirks helps fewer people run into issues like these while also documenting that a service's password policy is too restrictive for people using password managers, which may incentivize the services to change.
-
Ask HN: Where's the website that shows password requirements for other sites?
Check out https://github.com/apple/password-manager-resources
-
Suggestion: Collect every website possible info about how long could be a password on that site and suggest the longest possible password for it
Apple has already created the database for this and made it open source: https://github.com/apple/password-manager-resources
- I’m really sick of keychain password suggestion NOT WORKING on more than half the internet. WHY!!
-
I hate password rules!
Something like this?
-
what is the most practical password length?
Password rules are really all over the place. Based on the sampling available on Apple's password rules database, seems that the majority of sites would accept a 12-character password (although ironically, most websites that restrict the password to be shorter than 12 characters seem to be banks...).
-
Easily move all your passwords from Bitwarden to iCloud Keychain
There are still some things in Keychain that feel stupid. For example, Keychain won't merge https://www.google.co.uk and https://www.google.com accounts into one and you can't do it by yourself, and it will even warn about duplicated passwords for these two websites — that's very stupid especially because Apple maintains open database for password managers which solves the problem of alias domains. But that's the most annoying thing for me.
-
YouTubePluginReplacement.cpp: YouTube-specific code in WebKit
https://github.com/apple/password-manager-resources/blob/mai...
For being "quite obscure", I've at least heard of most of these sites before. Banks with "maxlength: 8", you love to see it.
-
Why does Apple’s “Strong Password” not meet most websites’ criteria
FWIW, Apple asks users to tell them the password requirements to websites they notice the "Strong Password" feature doesn't work correctly.
-
How to use iCloud Keychain, Apple's built-in and free password manager
The password complexity rule set is open source, you can contribute requirements for specific sites: https://github.com/apple/password-manager-resources
msquic
- Msquic: Cross-platform C implementation of QUIC protocol for C, C++, C#, Rust
-
Avoiding HTTP/3 (for a while) as a pragmatic default
I referred to sockets as an API design, not to express an opinion on whether you should place your protocol implementations inside or outside the kernel. (Although that’s undeniably an interesting question that by all rights should have been settled by now, but isn’t.)
Even then, I didn’t mean you should reproduce the Berkeley socket API verbatim (ZeroMQ-style); multiple streams per connection does not sound like a particularly good fit to it (although apparently people have managed to fit SCTP into it[1]?). I only meant that with the current mainstream libraries[2,3,4], establishing a QUIC connection and transmitting bytestreams or datagrams over it seems quite a bit more involved than performing the equivalent TCP actions using sockets.
[1] https://datatracker.ietf.org/doc/html/rfc6458
[2] https://quiche.googlesource.com/quiche
[3] https://github.com/microsoft/msquic
[4] https://github.com/litespeedtech/lsquic
-
My plan for making 256bit signed and unsigned integers in C. Please help me understand this concept better.
The documentation of MS QUIC says it is cross-platform, it should work on Linux, it has a CMake preset for Linux and you can download the prebuilt binary releases for Linux.
- Best performing quic implementation?
-
Show HN: Protect Your CI/CD from SolarWinds-Type Attacks with This Agent
Hello HN, my name is Varun, and I am the co-founder of StepSecurity. Here is the backstory about Harden-Runner. We thoroughly researched past software supply chain security incidents. The devastating breaches of SolarWinds, Codecov, and others, have one thing in common – they attacked the CI/ CD pipeline or the build server.
These incidents made it clear that a purpose-built security agent was needed for CI/ CD. While there are numerous agents available for desktops and servers, such as from CrowdStrike and Lacework, none have been tailored specifically to address the unique risks present in CI/CD pipelines.
With the understanding that a specialized solution was needed to secure CI/CD environments, we developed Harden-Runner, an open-source solution tailored specifically for GitHub Actions hosted runners. It can be seamlessly integrated into your workflow by simply adding a step. The agent installation process is also lightning-fast, taking no more than 5 seconds to complete.
Harden-Runner's security agent is designed to closely monitor all aspects of the workflow run, including DNS, network, file, and process events. This allows for real-time identification of any potential security breaches. To prevent incidents like the Codecov breach, where exfiltration of credentials occurred, Harden-Runner allows you to set policies that restrict outbound traffic at both the DNS and network layers. Additionally, we are actively working on implementing further restrictions at the application layer, such as using HTTP verbs and paths, to provide an even more comprehensive security solution.
An excellent example of how Harden-Runner effectively blocks outbound traffic can be found in the following link: https://app.stepsecurity.io/github/microsoft/msquic/actions/.... As you can see, all traffic to unauthorized endpoints is highlighted in red, indicating that it has been blocked; this is because these endpoints are not included in the allowed list defined in the GitHub Actions workflow file, which can be viewed here: https://github.com/microsoft/msquic/blob/aaecb0fac5a3902dd24....
One of the key features of Harden-Runner's monitoring capabilities is its ability to detect any tampering or alteration of files during the build process, similar to the SolarWinds incident. To further enhance security and protect against potential malicious tools or attempts to disable the agent, Harden-Runner includes a disable-sudo mode. This mode effectively disables the use of 'sudo' on the hosted runner, providing an additional layer of protection
Harden-Runner has already been adopted by over 600 open-source repositories: https://github.com/step-security/harden-runner/network/depen.... To fully understand the capabilities of Harden-Runner and how it can protect against past supply chain attacks, please try out our attack simulator GitHub repository at https://github.com/step-security/attack-simulator. I would love to hear your feedback.
-
Least painful path to multiplatform builds?
https://github.com/microsoft/msquic (QUIC / HTTP3)
-
msquic VS MsQuic.Net - a user suggested alternative
2 projects | 15 Jul 2022
- The Illustrated QUIC Connection
- Msquic - Cross-platform, C implementation of the IETF QUIC protocol.
What are some alternatives?
security.txt
quiche - 🥧 Savoury implementation of the QUIC transport protocol and HTTP/3
foundationdb - FoundationDB - the open source, distributed, transactional key-value store
lsquic - LiteSpeed QUIC and HTTP/3 Library
winget-pkgs - The Microsoft community Windows Package Manager manifest repository
quinn - Async-friendly QUIC implementation in Rust
hummingbird - Hummingbird compiles trained ML models into tensor computation for faster inference.
openmptcprouter - OpenMPTCProuter is an open source solution to aggregate multiple internet connections using Multipath TCP (MPTCP) on OpenWrt
coremltools - Core ML tools contain supporting tools for Core ML model conversion, editing, and validation.
shadowsocks-rust - A Rust port of shadowsocks
securitytxt.org - Static website for security.txt.
mvfst - An implementation of the QUIC transport protocol.