bigtreetech / bigtreetech/CB1

CB1 Credential Hardening

Open
#193 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
496
Forks
86
PR merge metrics
No merged PRs in 30d

Description

CB1s, similar to other 3dprinting devices, make use of a static default password. Users should be forced into changing this password during the initial setup proces to ensure these devices can't be easily compromised. While changing default account passwords is common best practice in tech, most users do not know how, or don't even think about it as a risk.

To help illustrate the point here is a pic of a simple model stealer I threw together.
[This can easily be swapped out for malware]
![image](https://github.com/user-attachments/assets/b6065318-5970-4678-afba-63c8f62a4e0c)

One possible way to streamline the change into the setup process would be to wrap klipper in a password validation check. If the Biqu account hash is still default, klipper doesn't start.

```bash
#!/bin/bash

DEFAULT_HASH="$6$c1yGPv.3$ZZ..."
CURRENT_HASH=$(getent shadow biqu | awk -F: '{print $2}')

if [[ "$CURRENT_HASH" == "$DEFAULT_HASH" ]]; then
echo "Klipper cannot start. Please change the default password for user 'biqu'." >&2
exit 1
fi
exit 0
```

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the initial setup flow and the point where Klipper is started, then inspect how the biqu account password is checked through the system shadow database. The issue’s proposed behavior is complete when setup requires changing the default password and Klipper cannot start while it remains unchanged.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash
Domain
authentication, operating-systems, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.