Why is a bad idea going against CVS philosophy? CVS was engineered as a control version tool for open source. There is no point on dealing a source or configuration files that shouldn't be shared with anybody else only with this tool. In that case there are interesting commercial and/or free tools to protect your sensitive data that could contain critical information like passwords, etc. Those usually provides also the traceability wich is supplied by CVS. If all you need is traceability but you need develop some security mechanisms by making a solution constrainted to a concrete filesystem and authentication system... It would be an interesting exercise, but since other tools still abstract them over any filesystem and any authenticaction system with a huge manpower behind, I don't think an specific solution would be the better solution.

-- FranYuste - 22 Feb 2006

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2020-08-19 - TWikiAdminUser
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox/SandboxArchive All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback