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

Add keypair support for ed25519 #13219

Merged
merged 7 commits into from
Jun 27, 2023
Merged

Add keypair support for ed25519 #13219

merged 7 commits into from
Jun 27, 2023

Commits on Jun 26, 2023

  1. Add ed25519 insecure private key 

    Add a new ed25519 insecure private key. Update the README with
information about the two insecure keys. Retain the RSA key in the
`vagrant` file and duplicate it into `vagrant.key.rsa`. Append the
ed25519 public key to the `vagrant.pub` file.
    @chrisroberts
    chrisroberts committed Jun 26, 2023
    Configuration menu
    Copy the full SHA
    b40f6e5 View commit details
    Browse the repository at this point in the history

  2. Add ed25519 keypair support 

    Introduce keypair support for ed25519. Default keypair type when
generating without specifying type is rsa to maintain existing behavior.
    @chrisroberts
    chrisroberts committed Jun 26, 2023
    Configuration menu
    Copy the full SHA
    6756258 View commit details
    Browse the repository at this point in the history

  3. Use key type supported by server if possible 

    Check the key types supported by the server. If the data is not
available, default to the previous behavior which is using the rsa key
type.

Update insecure key check to match against any key files located within
the keys directory. For now, this effectively allows matching either rsa
or ed25519 insecure private keys.
    @chrisroberts
    chrisroberts committed Jun 26, 2023
    Configuration menu
    Copy the full SHA
    cebfb7a View commit details
    Browse the repository at this point in the history

  4. Define directory and paths for insecure private keys 

    Within the environment, add a new directory value which points to the
directory containing the valid insecure private keys. A new default
private key paths value contains an array of all the insecure private
keys which are available for initial authentication.
    @chrisroberts
    chrisroberts committed Jun 26, 2023
    Configuration menu
    Copy the full SHA
    380afe5 View commit details
    Browse the repository at this point in the history

  5. Use all insecure private key paths 

    When constructing the ssh information, use all available insecure key
paths for authentication.
    @chrisroberts
    chrisroberts committed Jun 26, 2023
    Configuration menu
    Copy the full SHA
    e0dbbcc View commit details
    Browse the repository at this point in the history

  6. Add and update tests for insecure private keys 

    Updates existing test coverage to use insecure private key collection
and adds testing for behavior changes within the communicator and the
keypair utility.
    @chrisroberts
    chrisroberts committed Jun 26, 2023
    Configuration menu
    Copy the full SHA
    602d42b View commit details
    Browse the repository at this point in the history

  7. Update box documentation about keys

    @chrisroberts
    chrisroberts committed Jun 26, 2023
    Configuration menu
    Copy the full SHA
    2e95d08 View commit details
    Browse the repository at this point in the history