SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[PR #6316] [MERGED] fix: SSH authorized keys not added in Alpine install script #6557

New Issue
Open
opened 2025-11-20 07:11:07 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:11:07 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/6316
Author: @enihsyou
Created: 7/28/2025
Status: ✅ Merged
Merged: 7/28/2025
Merged by: @tremor021

Base: main ← Head: fix/alpine-add-ssh-authorized-key

📝 Commits (1)

  • 6308ee4 fix: SSH authorized keys not added in Alpine install script

📊 Changes

1 file changed (+7 additions, -0 deletions)

View changed files

📝 misc/alpine-install.func (+7 -0)

📄 Description

✍️ Description

During the Alpine LXC container installation (and ct/alpine-something.sh category), I was asked to provide an SSH public key, but it was not written to the .ssh/authorized_keys file after completion. The install.func file in a previous PR included functionality to automatically create the authorized public key, but this was omitted in the refactored alpine-install.func. This PR restores that functionality.

🔗 Related PR / Issue

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • ✨ New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/6316 **Author:** [@enihsyou](https://github.com/enihsyou) **Created:** 7/28/2025 **Status:** ✅ Merged **Merged:** 7/28/2025 **Merged by:** [@tremor021](https://github.com/tremor021) **Base:** `main` ← **Head:** `fix/alpine-add-ssh-authorized-key` --- ### 📝 Commits (1) - [`6308ee4`](https://github.com/community-scripts/ProxmoxVE/commit/6308ee4d98e74fa79a7295e51fb8e4a33c55d48f) fix: SSH authorized keys not added in Alpine install script ### 📊 Changes **1 file changed** (+7 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `misc/alpine-install.func` (+7 -0) </details> ### 📄 Description <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description During the Alpine LXC container installation (and `ct/alpine-something.sh` category), I was asked to provide an SSH public key, but it was not written to the `.ssh/authorized_keys` file after completion. The `install.func` file in a previous PR included functionality to automatically create the authorized public key, but this was omitted in the refactored `alpine-install.func`. This PR restores that functionality. ## 🔗 Related PR / Issue - #1502 ## ✅ Prerequisites (**X** in brackets) - [X] **Self-review completed** – Code follows project standards. - [X] **Tested thoroughly** – Changes work as expected. - [X] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [X] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 07:11:07 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#6557
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?