group for checking permissions on reading configuration is hardcoded

[roock]

In

opkssh/commands/verify.go

Line 145 in 60a454a

err = v.filePermChecker.CheckPerm(v.ConfigPathArg, []fs.FileMode{0640}, "root", "opksshuser")

the groups is hardcoded to opksshuser, but should be somehow "configurable/auto-detected".

[EthanHeilman]

@roock Why should this be configurable/auto-detected? What is the your usecase?

[roock]

I'm currently trying to setup installation of opkssh with a configuration management system instead of using the installation script. In my first test, I called the user just opkssh and noticed some error messages in the log which I could pinpoint this issue.

Also even the official installation script supports customized usernames via environment variables.

[EthanHeilman]

Also even the official installation script supports customized usernames via environment variables.

That's a good point. We should probably add that to the server config file. Would you be willing to create a PR that makes it configurable?

[roock]

The issue happens when reading the server config file, so not sure if this is the best option.

(Anyway, not sure my Go language skills are sufficient for a PR).

[EthanHeilman]

Let me look into it. Is this blocking you?

[roock]

No, it's not blocking, I changed my configuration management system to use opkuser.