Sylvain Beucler <[EMAIL PROTECTED]> tapota : >> > If the switch is off by default, btw, users won't be warned when they >> > insert an invalid key, so maybe we could even get rid of the switch. >> >> But we do not know what kind of key X Savane installation intend to >> use. We cannot make valid assumption in this matter. That's site >> specific, so it must be configurable. Even if we think being able to >> list most kind of keys. > > Well, the fact we restrict the key to a single line is already making > assumption on the key format. As I wrote a user pointed that the > 'ssh2' proprietary package use a multiple lines format -- I didn't > really check, though. Likewise, I am not sure that > '~/.ssh/authorized_keys' is specified by the SSH protocol. > > So Savane is making an assumption regarding the SSH keys format.
Ok, right. Let's say we'll limit the assumptions as much as possible. >> The default settings should not make assumptions on how the >> installation is to be used. And checks that restrict usage of the >> installation must always be site-configurable (like the tests made >> on user and group name, for instance). > > The tests on user and group names made in account.php are hardcoded :/ Take a look at etc/site-specific-content/forbidden_group_names.txt -- Mathieu Roy +---------------------------------------------------------------------+ | General Homepage: http://yeupou.coleumes.org/ | | Computing Homepage: http://alberich.coleumes.org/ | | Not a native english speaker: | | http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english | +---------------------------------------------------------------------+
