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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230119160812.6ea60396@kernel.org>
Date:   Thu, 19 Jan 2023 16:08:12 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Rob Herring <robh@...nel.org>
Cc:     netdev@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next v3 2/8] netlink: add schemas for YAML specs

On Thu, 19 Jan 2023 08:07:31 -0600 Rob Herring wrote:
> > +$id: "http://kernel.org/schemas/netlink/genetlink-c.yaml#"
> > +$schema: "http://kernel.org/meta-schemas/netlink/core.yaml#"  
> 
> There's no core.yaml. If you don't have a custom meta-schema, then
> just set this to the schema for the json-schema version you are using.
> Then the tools can validate the schemas without your own validator
> class.

$schema: https://json-schema.org/draft/2020-12/schema

or

$schema: https://json-schema.org/draft-09/schema

? 

It seems like the documentation suggests the former but the latter 
appears widespread.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ