I think we probably wouldn't want to encourage use of a web-based Butane converter hosted outside the Fedora project. Butane configs often contain credentials or other sensitive information, so there's a risk that the service could be compromised and used to steal sensitive data. This isn't a comment about you — no doubt your intentions are good — but we also need to consider security vulnerabilities, including in hosting providers beyond your control.
(One example of such an issue: the converter currently writes the user's Butane config to a temporary file, and then fails to remove that file if Butane produces any errors or warnings.)
In addition, Butane supports inclusion of local files via the local directive and storage.trees section, coupled with the --files-dir argument. Online converters can't use these, of course, which reduces their usefulness for complex configs.
I'll go ahead and close this, but thanks for your interest in making Butane easier to use.
I think we probably wouldn't want to encourage use of a web-based Butane converter hosted outside the Fedora project. Butane configs often contain credentials or other sensitive information, so there's a risk that the service could be compromised and used to steal sensitive data. This isn't a comment about you — no doubt your intentions are good — but we also need to consider security vulnerabilities, including in hosting providers beyond your control.
(One example of such an issue: the converter currently writes the user's Butane config to a temporary file, and then fails to remove that file if Butane produces any errors or warnings.)
In addition, Butane supports inclusion of local files via the
local
directive andstorage.trees
section, coupled with the--files-dir
argument. Online converters can't use these, of course, which reduces their usefulness for complex configs.I'll go ahead and close this, but thanks for your interest in making Butane easier to use.