Closed
Bug 1112980
Opened 11 years ago
Closed 9 years ago
Many duplicate keydir reports when committing conf/gitolite.conf
Categories
(Developer Services :: Git, defect)
Developer Services
Git
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: hwine, Assigned: fubar)
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4238] )
Committing the configuration file very nicely does an automatic deploy. However, there are many duplicate key warnings reported, which could mask deployment errors.
As I understand the messages and concept, the duplicate keys provide no end user value.
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/4238]
| Assignee | ||
Comment 1•9 years ago
|
||
I don't think there's any way to fix this bar modifiying gitolite itself.
/usr/share/gitolite3/triggers/post-compile/ssh-authkeys:
for my $f (@pubkeys) {
my $fp = fp($f) || "";
if ($fp eq "") { next } ;
if ( $seen{$fp} ) {
_warn "$f duplicates $seen{$fp}, sshd will ignore it";
} else {
$seen{$fp} = $f;
}
push @gl_keys, grep { /./ } optionise($f);
}
One can, in theory, change what _warn() does, but then we run the risk of missing other important things. Also, sometimes it *is* useful to see these messages, as we've had cases where people have the same key on multiple accounts that have different privs and wonder why their access doesn't work.
Assignee: nobody → klibby
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•