openwrt / openwrt/packages

atlas-sw-probe: wrong flags used in ssh-keygen, no exception handling for failed ssh-keygen invocations.

Open
#27,763 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Makefile
Stars
4.6k
Forks
4k
Avg merge
3d 12h
Merged PRs (30d)
134

Description

Package Name

atlas-sw-probe

Maintainer

@ansuel

OpenWrt Version

OpenWrt 24.10.4, r28959-29397011cc

OpenWrt Target/Subtarget

all

Steps to Reproduce

The script /etc/init.d/atlas create_key fails on OpenWRT since it uses dropbear ssh-keygen instead of OpenSSL.

ssh-keygen -t rsa -b 2048 should be instead ssh-keygen -t rsa -s 2048

Also, there is no exception handling for calling ssh-keygen, so when the error is thrown and the script claims it completes successfully.

root@OpenWrt:/usr/libexec/atlas-probe-scripts/data/out# ssh-keygen
Must specify a key filename
Usage: ssh-keygen -t <type> -f <filename> [-s bits]
-t type Type of key to generate. One of:
                rsa
                ed25519
-f filename    Use filename for the secret key.
               ~/.ssh/id_dropbear is recommended for client keys.
-s bits Key size in bits, should be a multiple of 8 (optional)
           Ed25519 has a fixed size of 256 bits
-y              Just print the publickey and fingerprint for the
                private key in <filename>.
-C              Specify the key comment (email).
Actual Behaviour

Kye was not created by script.

Confirmation Checklist

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the /etc/init.d/atlas create_key script and its ssh-keygen invocation. Verify the key-generation flags against the shown ssh-keygen usage, then check how a failed invocation is reported. Done means the key is created successfully and failures no longer claim completion.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
operating-systems
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.