View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004255 | unreal | ircd | public | 2014-03-09 09:06 | 2014-05-30 19:33 |
| Reporter | Friendly_hazard | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | no change required | ||
| Summary | 0004255: Key Chain | ||||
| Description | I would love to be able to define multiple keys for a channel. The current key "+k key1" would remain the same but there would be a new key (lets say "+B key2"). If both are defined, user can supply either key1 or key2 to join. This way you can migrate from key1 to key2 with less chance of interruption. (I got the idea while studying for my Cisco exams.) So for example you start using "+k keyA" on January 1st with +B being undefined. Most users can only join if they use keyA. On January 25th you add "+B keyB". Users may use either keys to join (perhaps users can receive a notice if they are using the outdated key). Finally on February 1st, you -k. Hopefully the server will automatically fill it is as "-k keyA", and then immediately "+k keyB". | ||||
| 3rd party modules | |||||
|
|
I appreciate the feature suggestion but I wonder if this will really be used in practice. Does anyone else feel this is useful / will use it? |
|
|
On second thought, I'm going to close this off, as it won't get in core UnrealIRCd anyway. It may be possible to do in a module, though. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2014-03-09 09:06 | Friendly_hazard | New Issue | |
| 2014-03-14 01:14 | peterkingalexander | Issue cloned: 0004258 | |
| 2014-05-30 19:33 | syzop | Note Added: 0018150 | |
| 2014-05-30 19:33 | syzop | Note Added: 0018151 | |
| 2014-05-30 19:33 | syzop | Status | new => closed |
| 2014-05-30 19:33 | syzop | Assigned To | => syzop |
| 2014-05-30 19:33 | syzop | Resolution | open => no change required |
