| … | |
… | |
| 504 | =item seed-interval = seconds |
504 | =item seed-interval = seconds |
| 505 | |
505 | |
| 506 | The number of seconds between reseeds of the random number generator |
506 | The number of seconds between reseeds of the random number generator |
| 507 | (default: C<3613>). A value of C<0> disables this regular reseeding. |
507 | (default: C<3613>). A value of C<0> disables this regular reseeding. |
| 508 | |
508 | |
|
|
509 | =item serial = string |
|
|
510 | |
|
|
511 | The configuration serial number. This can be any string up to 16 bytes |
|
|
512 | length. Only when the serial matches on both sides of a conenction will |
|
|
513 | the connection succeed. This is I<not> a security mechanism and eay to |
|
|
514 | spoof, this mechanism exists to alert users that their config is outdated. |
|
|
515 | |
|
|
516 | It's recommended to specify this is a date string such as C<2013-05-05> or |
|
|
517 | C<20121205084417). |
|
|
518 | |
|
|
519 | The exact algorithm is as this: if a connection request is received form a |
|
|
520 | node with an identical serial, then it succeeds normally. |
|
|
521 | |
|
|
522 | If the remote serial is lower than the local serial, it is ignored. |
|
|
523 | |
|
|
524 | If the remote serial is higher than the local serial, a warning message is |
|
|
525 | logged. |
|
|
526 | |
| 509 | =back |
527 | =back |
| 510 | |
528 | |
| 511 | =head2 NODE SPECIFIC SETTINGS |
529 | =head2 NODE SPECIFIC SETTINGS |
| 512 | |
530 | |
| 513 | The following settings are node-specific, that is, every node can have |
531 | The following settings are node-specific, that is, every node can have |
