mirror of
https://github.com/ovh/the-bastion.git
synced 2026-05-09 08:25:27 +02:00
[PR #590] [MERGED] fix: debian 13 uses lastlog2 #595
Labels
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/the-bastion#595
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
📋 Pull Request Information
Original PR: https://github.com/ovh/the-bastion/pull/590
Author: @jon4hz
Created: 9/23/2025
Status: ✅ Merged
Merged: 11/5/2025
Merged by: @speed47
Base:
master← Head:fix-lastlog2📝 Commits (3)
fae4c92fix: debian 13 uses lastlog2a1d6121fix: also make sure libpam-lastlog2 is installed9161911fix: handle lastlog for ubuntu correctly📊 Changes
2 files changed (+20 additions, -0 deletions)
View changed files
📝
bin/admin/install(+13 -0)📝
bin/admin/packages-check.sh(+7 -0)📄 Description
This PR fixes a small issue on debian 13, as it doesn't use
lastlogbutlastlog2.However, I'm not quite sure why this is even needed in the first place. The Bastion seems to track last logins in a file that is stored in the user homes.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.