| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
Signed-off-by: Paul Chaignon <paul.chaignon@gmail.com>
|
| |
|
|
|
|
|
| |
SO_BINDTODEVICE for wg devices allows to reach very important
part of functionality (wg_xmit).
Update #806
|
| |
|
|
| |
By keeping this small, it means much greater probability that a randomly
generated packet that hits xmit will match an existing peer.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The stringnozescapes does not make sense with filename,
also we may need similar escaping for string flags.
Handle escaped strings on ast level instead.
This avoids introducing new type and works seamleassly with flags.
As alternative I've also tried using strconv.Quote/Unquote
but it leads to ugly half-escaped strings:
"\xb0\x80s\xe8\xd4N\x91\xe3ڒ,\"C\x82D\xbb\x88\\i\xe2i\xc8\xe9\xd85\xb1\x14):M\xdcn"
Make hex-encoded strings a separate string format instead.
|
| |
|
|
|
| |
Commit "wireguard: use wg0, wg1, wg2" added wg2,
bump netdev_addr_id accordingly.
|
| |
|
|
|
| |
This adds stringnozescapes to allow parsing of escape sequences in
strings.
|
| |
|
|
|
| |
This matches more closely what people are used to dealing with. We also
add one additional device for interesting multi-interface effects.
|
| |
|
|
|
| |
This tests more edge cases, as well as allowing for potentially a
correponding public and private key to be installed.
|
| |
|
|
| |
Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
|
| | |
|
| |
|
|
|
| |
Adding support for IPPROTO_MPTCP. Like SMC, it is on top of TCP and can
thus be treated like a regular TCP socket.
|
| | |
|
| |
|
|
| |
Update #806
|
| |
|
|
|
|
| |
Thanks to syz-check for catching this.
Update #590
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
If we are going to write all values, don't write field names.
This only increases size of generated files.
The change reduces size of generated files by 5.8%
(62870496-59410354=3460142 bytes saved).
|
| |
|
|
|
|
| |
+ disable binderfs (see comments)
+ add few more missing tty ioctls
+ improve few minor things in hci descriptions
|
| |
|
|
|
| |
They are being fixed in kernel:
https://lists.openwall.net/netdev/2020/01/23/122
|
| | |
|
| |
|
|
|
|
|
|
| |
Stop at the fist varlen field, but check the preceeding ones.
Frequently the varlen array is the last field,
so we should get good checking for these cases.
Update #590
|
| |
|
|
| |
Update #590
|
| |
|
|
|
|
|
|
|
|
| |
Handle NLA_BITFIELD32.
Match string attribtues better.
Calculate and check min size for varlen structs.
Fix NLA_UNSPEC size check.
Fix some things in descriptions.
Update #590
|
| |
|
|
| |
Update #590
|
| |
|
|
| |
Update #590
|
| |
|
|
|
|
|
|
|
|
|
| |
As far as I understand most subsystems don't care about
the nest flag, but some do. But marking them as nest
won't harm (?). Let's mark all of them.
Caught several cases where should have been used array[policy]
but used just policy.
Update #590
|
| |
|
|
|
|
|
|
|
|
| |
1. Match policies that has a _suffix in our descriptions
(we frequently do this to improve precision or avoid dup names).
2. Rename policies in descriptions to match kernel names.
3. Match policy if there are several such names in kernel.
4. Recognize policies with helper sub-policies.
Update #590
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
They can't be a bitmask. This fixes important cases
of "0, 1" and "0, 1, 2" flags. Fix some descriptions
that added 0 to bitmasks explicitly (we should do it
automatically instead).
|
| |
|
|
|
|
| |
Will simplify runtime analysis of flags.
Also just no reason to make it more deterministic
and avoid unnecessary diffs in future if values are reordered.
|
| |
|
|
|
|
|
| |
Generate const[0] for flags without values and for flags
with a single value which is 0.
This is the intention in all existing cases (e.g. an enum with types
of something, but there is really only 1 type exists).
|
| |
|
|
| |
Update #590
|
| |
|
|
| |
The same reason as with seccomp.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The common code now expects it to be called ipv6_packet_t.
The freebsd fork wasn't updated when the linux version changed.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
1. Add "bitmap:port" type.
2. ipv4/6 addresses must be in network byte order.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
1. Turns out that NLA_F_NESTED is actually used and checked
(nla_parse_nested checks it, while nla_parse_nested_deprecated does not).
Similarly, ipset extensively checks NLA_F_NET_BYTEORDER.
So we need these bits.
2. nla_len must not account for the trailing alighnment padding.
This means we set wrong len for payloads that are not multiple of 4
(int8/int16/strings/arrays/some structs/etc).
|
| |
|
|
| |
See the added test for details.
|