Certificates

This page goes over how certificates work in Reyveld.

Security and safety are two of Reyveld's top priorities. To achieve this goal, everything must first create and load a unique certificate that describes what it wants to do with Reyveld.

---This requests all permissions in Arceus. 
---This is not recommended, as it is not trustworthy.
function AuthAll()
    return AuthVeld.authorize("Rey Dau",
        { SPolicy.all() })
end

---This requests access to write, create, and delete SKits, but not read them.
---This will give the user a warning, as writing, creating, and deleting SKits could
---lead to missing/corrupted files, however, it can be contained.
function AuthSKit()
    return AuthVeld.authorize("Rey Dau", {
        SPolicy.skit({ write = true, create = true, delete = true })
    })
end

---This requests access to only read pk9, pk8, pk7, and pk6 files.
---This is the most trustworthy certificate, and should be safe.
function AuthFiles()
    return AuthVeld.authorize("Rey Dau", {
        SPolicy.externalFiles({
            read = true
            whitelist = Globs.whitelist().addAll({ "*.pk9", "*.pk8",
                "*.pk7", "*.pk6" })
        })
    })
end