| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Replaced all those magic numbers.
|
| |
|
| |
|
|
|
|
| |
messages.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Since INFORMATIONAL "exchanges" are actually unidirectionally sent
message we don't have any responder rules.
|
|
|
|
|
| |
These are basically the same as for ID_PROT but no payloads are expected
to be encrypted (at least if using PSK or signatures for authentication).
|
|
|
|
|
| |
These rules are quite broad and cover main mode with at least PSK and
signature based authentication.
|
| |
|