linux-kernel - Re: [v2 0/1] Documentation: bootconfig: Documentation updates

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <0d7d201c-e313-6129-7cfa-4e61eb31342d@web.de>
Date:   Fri, 28 Feb 2020 15:05:42 +0100
From:   Markus Elfring <Markus.Elfring@....de>
To:     Masami Hiramatsu <mhiramat@...nel.org>, linux-doc@...r.kernel.org
Cc:     Jonathan Corbet <corbet@....net>,
        Steven Rostedt <rostedt@...dmis.org>,
        Randy Dunlap <rdunlap@...radead.org>,
        linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [v2 0/1] Documentation: bootconfig: Documentation updates

> Didn't you read the article I shared?

I read also the article “Don’t Use ISO/IEC 14977 Extended Backus-Naur Form (EBNF)”
by David A. Wheeler.
Some possibilities were pointed out as desirable improvements.

> I actually wrote up the EBNF (ISO/IEC 14977) that was a good pazzle,
> but just a toy.

I hope that this contribution can help to become more productive
in the discussed application domain.
https://lkml.org/lkml/2020/2/27/72
https://lore.kernel.org/patchwork/patch/1200987/
https://lore.kernel.org/linux-doc/158278836196.14966.3881489301852781521.stgit@devnote2/

> I found no one use it to define their data format, according to the article,
> including ISO itself (lol!) and there are many local extension,
> including W3C EBNF, and those say "I'm EBNF".

I suggest to reconsider the current situation.

> Well, to say the least, I feel it is quite confused.

Such a view is reasonable.

> So, if you are interested in it, I don't stop you to write it up.

Will the collaboration continue anyhow?

> I just keep away from it.

This is a pity.

Will the clarification become more constructive for remaining challenges?

Regards,
Markus