Sync dta4/radius with latest updates from beerappasm/radius #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* fix set vendor Co-authored-by: Jaroslaw Dziuk <jaroslaw@aimbrain.com> Co-authored-by: Dominik Weidenfeld <dominik@weidenfeld.info> Co-authored-by: Holger Metschulat <holger.metschulat@telekom.de> Co-authored-by: Warren Brown <wa.brown@reply.com>
…lpassword-lookup Fix tunnelpassword lookup
…asswords Fix userpasswords
* apply patches * fix comment Co-authored-by: Dirk Moermans <dirk.moermans@telekom.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fork Structure:
layeh/radius.layeh/radius.holgermetschulat/radius.npuri/radius(multiple steps removed from the originallayeh/radius).Purpose:
This PR syncs the
dta4/radiusrepository with the latest updates frombeerappasm/radius, which contains the most recent changes and improvements.beerappasm/radiusis several forks ahead ofdta4/radius, and we need to bring those changes intodta4/radiusto keep it up to date.Potential Conflicts:
dta4/radiusandbeerappasm/radius. These will need to be resolved during the merge process.Testing:
dta4/radiusis thoroughly tested. Verify that all tests pass and no issues are introduced by the merge.Additional Notes:
dta4/radiuscloser to the current state ofbeerappasm/radius, while maintaining its foundation inlayeh/radius.