lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 26 Dec 2019 09:04:06 -0800 From: Stephen Hemminger <stephen@...workplumber.org> To: Julien Fortin <julien@...ulusnetworks.com> Cc: netdev@...r.kernel.org, roopa@...ulusnetworks.com, dsahern@...il.com Subject: Re: [PATCH iproute2-next] ip: ipneigh: json: print ndm_flags as boolean attributes On Thu, 26 Dec 2019 15:44:15 +0100 Julien Fortin <julien@...ulusnetworks.com> wrote: > From: Julien Fortin <julien@...ulusnetworks.com> > > Today the following attributes are printed as json "null" attributes > NTF_ROUTER > NTF_PROXY > NTF_EXT_LEARNED > NTF_OFFLOADED > > $ ip -j neigh show > [ > { > "dst": "10.0.2.2", > "dev": "enp0s3", > "lladdr": "52:54:00:12:35:02", > "router": null, > "proxy": null, > "extern_learn": null, > "offload": null, > "state": [ > "REACHABLE" > ] > } > ] No, this was intentional. Null is a standard method in JSON to encode an option being present.
Powered by blists - more mailing lists