| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
makes my vagrant VM angry otherwise.
|
|
|
|
| |
duh.
|
| |
|
| |
|
|
|
|
|
| |
figured something changed and it's now wrong since
wireguard-go also fails this counter tests.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
just like main WireGuard source
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit a5bad2984b404b91670bbb634c79102b476a0b5a.
This seems to be the cause of a segfault.
|
| |
|
| |
|