Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
  • Sign in / Register
lava
lava
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 112
    • Issues 112
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 17
    • Merge Requests 17
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Packages
    • Packages
    • Container Registry
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lava
  • lavalava
  • Issues
  • #63

Closed
Open
Opened Aug 30, 2018 by Neil Williams@codehelp💬
  • Report abuse
  • New issue
Report abuse New issue

Generate low-security ssh keys for secondary connections

Use potentially weak keys generated using low security random sources (to avoid running out of entropy on the dispatcher) and generate the lava public and private key on a per job basis.

This support is intended for a secondary connection which will run a VM inside the test action and will need to copy content into that VM. Copy the public key into the guest deployment, use the existing support to copy the private key into the host deployment. Add the public key to the authorized_keys list on the guest.

Migrated from https://projects.linaro.org/browse/LAVA-517

Related issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
3
Labels
Linaro Migrated Technical Debt
Assign labels
  • View project labels
Reference: lava/lava#63