Menu
▾
▴
Re: [netrexx-pipelines] Literal and digest
|
From: Jeff H. <Je...@Je...> - 2021-08-18 19:25:29
|
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre class="moz-quote-pre" wrap=""><font size="+1">René</font></pre>
<p>Good to hear from you, and I hope you and yours are doing well.
I am doing so, keeping busy with summer activities and friends.</p>
<p>CMS' LITERAL syntax documentation says "Leading and
trailing blanks are significant." I missed that when doing the
NetRexx Pipelines stage testing and documentation. The NR
Pipelines stage just passes the string via a NetRexx method
argument, which strips off both leading and trailing blanks. I
don't know how to get around that. So for now, the NR
documentation for LITERAL should note this difference and offer
the workaround of STRLITERAL. If LITERAL could be fixed so the
string extends with blanks to the stage-separator, I expect many
current pipes that are formatted vertically (and some
horizontally) would suddenly work differently. I have no good
idea on which presents the lesser damage. I do suspect that there
are very few (CMS) pipes with LITERAL stages that have significant
trailing blanks. Probably more with leading blanks so the output
text aligns.<br>
</p>
<p>In my opinion, DIGEST (as any existing stage) should work as in
CMS. But many of our users in the PC/Java world will want the hex
output. The two stage solution works, but could we add a HEX
option with BYTES the default? Or would it be better to have a
new stage: DIGESTHEX?</p>
<font face="monospace"> <font
color="red">+--BYTES--+</font></font><br>
<font face="monospace"> >>--DIGEST--+--SHA1----+--<font
color="red">+---------+</font>--+----------------+-->></font><br>
<font face="monospace"> +--SHA256--+ <font
color="red">+--HEX----+</font> +--APPEND--------+</font><br>
<font face="monospace"> + etc. +
+ +<br>
</font>
<p>As for the symposium, I have no ideas on what to say, but would
be honored to be able to present.</p>
<p>Jeff<br>
</p>
<div class="moz-cite-prefix">On 8/18/2021 9:41 AM, René Jansen
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:5B1...@xs...">
<pre class="moz-quote-pre" wrap="">Hi Jeff,
How are you?
Just found out about a corner case in Pipelines for NetRexx - I was implementing DIGEST and in an effort to be CMS compatible I noticed that the hash is not returned in hex on CMS, but as bytes, which you can later translate. Not being able to get the same hashes, I noticed that I needed an XLATE E2A before the DIGEST stage, and then still it would not work.
So dumping every stage with SPECS 1-* C2X 1 I noticed that CMS Pipelines has an extra space in the pipeline, unless I put the pipe separator litterally at the end of the string.
And lo and behold, in the source for the LITERAL stage it actually tells us (Ed does) that CMS does preserve trailing spaces, and njpipes does not.
What do you think, do we need to fix this? And also, Do we want to have DIGEST output bytes instead of hex? I am leaning to ‘yes’ on both counts, but I would like to hear what you think, and whether fixing LITERAL will break anything.
Other thing, do you think you can present at the symposium, when that is online and somewhere in October?
Best regards.
René.
_______________________________________________
netrexx-pipelines mailing list
<a class="moz-txt-link-abbreviated" href="mailto:net...@li...">net...@li...</a>
<a class="moz-txt-link-freetext" href="https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines">https://lists.sourceforge.net/lists/listinfo/netrexx-pipelines</a>
</pre>
</blockquote>
</body>
</html>
|
