You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 2, 2026. It is now read-only.
Disclaimer: This idea is completely not thought trough at all, there are alternative ways to achieve what I want to have in onyo, and I also don't know how to implement it.
A scenario and my idea about it:
Imagine an organisation would hypotatically buy a bunch of combination lockers, and wants to track these as asset dirs (so they can contain assets like laptops, but also asset information themself, e.g. size, combination of lock).
Imagine the lock combinations would not be extremly sensitive, but just sensitive enough that you don't want to have them saved in plain text in a repository that 100+ people could see.
It would be lovely in these cases for onyo to have an easy and basic encryption mode that allows to have these combinations in an asset, change these combinations and keep them encrypted, and easily decrypt it. There are probably many ways to do this, one that comes to my mind (replace it with a better solution if you can) first would be:
To set an encrypted key: onyo set --asset ./path/to/locker --keys combination=1234 --password <password>
To get an encrypted key as decrypted: onyo get --asset ./path/to/locker --keys path combination --password <password>
Disclaimer: This idea is completely not thought trough at all, there are alternative ways to achieve what I want to have in onyo, and I also don't know how to implement it.
A scenario and my idea about it:
To set an encrypted key:
onyo set --asset ./path/to/locker --keys combination=1234 --password <password>To get an encrypted key as decrypted:
onyo get --asset ./path/to/locker --keys path combination --password <password>