KOPANO-ARCHIVER-ACLSET(8)

📦 version 8.7.0, in ubuntu jammy

✨ kopano-archiver-aclset ✨

okay bestie, so this is a page from the Kopano Core user reference — it's kopano-archiver-aclset(8), section 8, which means it's a sysadmin-flavoured command. it resets the archive ACL settings for the owner. that's the whole vibe. let's get into it 💅

🌸 NAME 🌸

kopano-archiver-aclset — reset the archive ACL settings for the owner.

like literally, that's it. it goes in, it fixes the permissions on an archive store so the owner can actually see their own stuff. no cap.

🦋 SYNOPSIS 🦋

kopano-archiver-aclset [OPTION...]

that's the whole thing. no positional args, just vibes and options. iconic honestly.

💖 DESCRIPTION 💖

so kopano-archiver-aclset sets or updates the permissions on an archive store for the owner of that store. main character energy, fixing what should've been right the first time 🫶

here's the lore: when an archive is attached to a store, the owner of the store gets either read-only or read/write permissions on the archive. which one depends on the configuration or the command line options that were passed at the time of attaching. so if past-you picked wrong, present-you is the one dealing with it 😭

also, when an archive is attached to a store of a non-active user, no permissions for that non-active user get set — because that's literally not possible. the system just can't do it, bestie. it's giving "sorry, not today."

so when would you actually run this?

  • case one: the permissions were fine at the time but now company policy changed, or the original setting was just wrong. we've all been there. it happens. so you'd want to change the permissions at a later time. 🎀
  • case two: the user was non-active, so no permissions were set, and now they've been converted to an active user. in that situation it's required to reset the permissions, because the owner won't have any permissions on their archive. zero. nothing. the archive is right there and they can't touch it. tragic.

so yeah, this tool is the fix. periodt. 🔥

⭐ OPTIONS ⭐

  • -w — by default, kopano-archiver-aclset makes an archive read-only for the user. if you pass this option, the user gets read/write permissions in the attached archive instead. so -w is the "okay fine, you can actually edit things" switch 💅
  • --user, -u NAME — run the script for just the specified user(s). by default, it runs for all users. so if you're feeling targeted rather than generous, this is your girl ✨
  • --log-level, -l NAME — specify log-level. for example, 'error', 'warning', 'info' or 'debug'. turn the volume up or down on the logging, your call 🎚️
  • --server-socket, -s SOCKET — connect to storage server through specified socket. like, tell it where to talk to the storage server, through this socket 🦋
  • --ssl-key, -k FILE — specify SSL key file. 🔐
  • --ssl-pass, -p PASSWORD — specify SSL key password. keep it secret, keep it safe 🙈

👑 AUTHOR 👑

written by Kopano. legends, honestly.

heads up bestie: if you mess with the wrong archive's permissions you're gonna have a bad time, so double-check your --user before you go setting ACLs on everything. this tool does exactly what it says and it does not ask twice 💀

and that's the whole page, babes 💖 it's from Kopano 8, dated November 2016, and it's filed under the Kopano Core user reference as KOPANO-ARCHIVER-ACLSET(8). go forth and reset those ACLs, you absolute icon 🌈⭐

📦 where this page comes from