bjornbouetsmith / root.zfs.api Goto Github PK

To not expose the underlying ZFS Library's classes we should instead create a 1:1 mapping or something else that makes sense, so we instead expose the properties of the underlying classes that we want.

So this task is about going through the REST methods, and make sure that none of them return a class that is not defined ny the API itself.

Improve authentication & authorization, so PAM is not only used to authenticate the user, but also make sure that whatever process is spawned - uses the crendentials provided in the API.

I.e.

right now some user is running the actual API on the server.
Another user logs on the API and calls a method.
Its the user that runs the API that is invoking the zfs/zpool method - which requires that the user have elevated credentials and is a potential attack vector.

So instead make sure that the user calling the API is also the user executing the zfs/zpool binaries.

Write proper documentation

• Classes/Methods needs to be documented
• Examples written