-
Notifications
You must be signed in to change notification settings - Fork 12
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.
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
NetSec: Improve multi-party authentication option #25
Comments
clintwilson
pushed a commit
that referenced
this issue
Jan 30, 2024
Add minor changes to Definitions and 1.1.1.1 to address these long-open issues.
clintwilson
added a commit
that referenced
this issue
May 6, 2024
* Reorganize NSRs and add Section 5 * Rewrite 1st commit Changes cover up to "Password-based Authentication", adding definitions, reordering sections and bullets, and rewriting a fair number of requirements. * 2.2.2 through 3.2.3.2 Finished first pass of reorganization for sections 2.2.2 (previously 2.2 Password-based Authentication) through 3.2.3.2 (previously 3.2.3). Lots of markdown comments added as I went, but I'm sure I missed some too. * Remove in-line markdown comments Removing all the in-line markdown comments after moving them to a document better suited to their discussion and use. Minor textual/grammar fixes in a handful of places. * Updates from Feedback Feedback from Ben, J.C., and Wendy incorporated. * Address issues #24 and #25 Add minor changes to Definitions and 1.1.1.1 to address these long-open issues. * Incorporated Section 4 Added Section 4 as-is back in and updated document header with placeholder for ballot. * Fix lists in Section 4 Fix copy/paste issue with lists' appearance in section 4. * MFA and MPC from NSWG feedback Based on feedback in the Jan 30, 2024 NSWG meeting, changed definitions for Multi-Factor Authentication, Multi-Party Control, and Secure Key Storage Device and corresponding document sections. * Markdown fixes Updates to ensure Markdown formatting is correct * Update for Multi-Party Control Fix scoping of 2.2.4 * Address feedback * Address Tim H's feedback on the list related to 1.1.1.1 and 1.1.1.2 * Minor consistency improvements in 1.2 and 1.3 * Address Feedback * Add Effective date of 2024-10-15, with explicit reference to versions that can be followed prior to that date. * Address #31 * Nit from Wendy * Incorporate Feedback * Update TBR name * Update Effective Date to November 12, 2024 (2024-11-12) based on NSWG discussion on April 9, 2024 * Add Document Date in header
Updated in Section 2.2.3 and 2.2.4 with #33 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@sleevi and @rmhrisk (I believe) both raised the point that when multi-party authentication is used, it should be able to be bypassed by an attacker compromising one authentication infrastructure (for example, the LDAP server) or directly harvesting two user passwords.
Can we state that when single-factor multi-party is in use, it is limited to hardware based authentication mechanisms?
The text was updated successfully, but these errors were encountered: