Re: Proposal: new CPAN module Crypt::TSD (.TSD read/write per RFC 5544) -> Crypt::TimestampedData

[email protected] (David Mertens) Fri, 3 Oct 2025 05:03:54 -0400
Newsgroups perl.module-authors
Message-ID <CA+4ieYWOva_4PCL0X1o-jPnz8RHGw_qDe50fOG-1miq7beD=gg@mail.gmail.com>
--000000000000442d2006403d625b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

No, I think you just have to be patient and let the testing machines work
through their queue. I notice that you have test reports for your most
recent version that came in 12 hours ago but some reports from earlier
versions came in only a couple hours ago.

I had always figured that a new upload would cancel the testing of an older
version, but you can see here that is not happening. Every version is
getting placed in the queue for every automated smoke tester. Your latest
is just waiting to make its way to the front of the line.

David

 "Debugging is twice as hard as writing the code in the first place.
  Therefore, if you write the code as cleverly as possible, you are,
  by definition, not smart enough to debug it." -- Brian Kernighan

On Fri, Oct 3, 2025, 4:29=E2=80=AFAM Guido Brugnara via module-authors <
[email protected]> wrote:

> I have finally uploaded a version of the package that I consider
> acceptable.
>
>     http://matrix.cpantesters.org/?dist=3DCrypt-TimestampedData
>
> But I don't know why the tests in the last two releases (0.01_04 &
> 0.01_05) are limited to the =E2=80=98Linux=E2=80=99 platform (all passed)=
.
>
> Perhaps it's because there were too many errors in in the previous tests
> on all tested platforms?
>
> I'm sure I've removed the issues that caused those errors, but now I don'=
t
> have any feedback to be sure.
>
> I apologise for the mistakes ... of youth ... I hope to improve.
>
> Should I request that the tests be reactivated? If so, how?
>
> regards
> Guido Brugnara
>
>
>
> Il 29/09/25 14:04, Guido Brugnara ha scritto:
>
> I would like to thank those who suggested I use an alias for the module
> name.
>
> I have therefore published
> https://metacpan.org/release/BRUGNARA/Crypt-TimestampedData-0.01-TRIAL
>
> Any comments you may have will be taken into consideration before final
> publication.
>
> Thank you!
> Guido Brugnara
>
>
> Il 14/09/25 13:15, Guido Brugnara ha scritto:
>
> Hello module-authors,
>     I=E2=80=99d like feedback on a new CPAN distribution I=E2=80=99m prep=
aring:
> Crypt::TSD. It implements reading and writing of RFC 5544 =E2=80=9CSyntax=
 for
> Binding Documents with Time-Stamps=E2=80=9D containers (file extension .t=
sd; media
> type =E2=80=9Capplication/timestamped-data=E2=80=9D per RFC 5955).
>
> In practice, .tsd is used notably in Italy; globally, adoption appears
> limited compared to RFC 3161 Time-Stamp Tokens and ETSI/eIDAS containers
> (CAdES/XAdES/PAdES/ASiC).
>
> Still, .tsd exists in the wild and there is no dedicated CPAN module
> covering it. Based on my survey of open-source options, the only Open
> Source library exposing APIs for RFC 5544/.tsd that I found is Bouncy
> Castle (Java); Crypt::TSD would provide a Perl alternative.
>
> Planned scope:
>  - Read .tsd files and extract the original content and associated
> time-stamp tokens.
>  - Create .tsd files from content and existing RFC 3161 tokens.
>  - Provide helpers for basic structural checks; further verification
> utilities may follow.
>  - Provide command line scripts to read/write .tsd files.
>
> Before first upload, I=E2=80=99d appreciate feedback on:
>  - The namespace: does Crypt::TSD look appropriate (alternatives:
> Crypt::TimestampedData, Crypt::RFC5544)?
>  - Any API/naming concerns or prior art I should align with.
>
> Thanks in advance for your guidance. I=E2=80=99m happy to adjust naming a=
nd API
> based on suggestions.
>
> Best regards,
> Guido Brugnara
>
>

--000000000000442d2006403d625b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div>No, I think you just have to be patient and let the =
testing machines work through their queue. I notice that you have test repo=
rts for your most recent version that came in 12 hours ago but some reports=
 from earlier versions came in only a couple hours ago.</div><div dir=3D"au=
to"><br></div><div dir=3D"auto">I had always figured that a new upload woul=
d cancel the testing of an older version, but you can see here that is not =
happening. Every version is getting placed in the queue for every automated=
 smoke tester. Your latest is just waiting to make its way to the front of =
the line.</div><div dir=3D"auto"><br></div><div dir=3D"auto">David</div><di=
v><br></div><div data-smartmail=3D"gmail_signature">=C2=A0&quot;Debugging i=
s twice as hard as writing the code in the first place.<br>
 =C2=A0 Therefore, if you write the code as cleverly as possible, you are,<=
br>
 =C2=A0 by definition, not smart enough to debug it.&quot; -- Brian Kernigh=
an<br></div></div><br><div class=3D"gmail_quote gmail_quote_container"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 3, 2025, 4:29=E2=80=AFAM Guid=
o Brugnara via module-authors &lt;<a href=3D"mailto:[email protected]=
">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex"><u></u>

 =20
   =20
 =20
  <div>
    <p><span><span><span>I</span>
          <span>have</span>
          <span>finally</span>
          <span>uploaded</span>
          <span>a
            version of the</span> <span>package</span>
          <span>that</span>
          <span>I</span>
          <span>consider</span>
          <span>acceptable</span><span>.</span></span></span></p>
    <p><span><span><span>=C2=A0=C2=A0=C2=A0
            <a href=3D"http://matrix.cpantesters.org/?dist=3DCrypt-Timestam=
pedData" target=3D"_blank" rel=3D"noreferrer">http://matrix.cpantesters.org=
/?dist=3DCrypt-TimestampedData</a><br>
          </span></span></span>
      <span></span>
    </p>
    <p><span><span><span>But
            I</span> <span>don&#39;t</span>
          <span>know</span>
          <span>why</span>
          <span>the</span>
          <span>tests</span>
          <span>in</span>
          <span>the</span>
          <span>last</span>
          <span>two</span>
          <span>releases</span>
          (0.01_04 &amp; 0.01_05) <span>are</span>
          <span>limited</span>
          <span>to</span>
          <span>the</span>
          <span>=E2=80=98</span><span>Linux</span><span>=E2=80=99</span>
          <span>platform</span><span>
            (all passed).</span></span></span></p>
    <p><span><span><span>Perhaps</span>
          <span>it&#39;s</span>
          <span>because</span>
          <span>there</span>
          <span>were</span>
          <span>too</span>
          <span>many</span>
          <span>errors</span>
          in <span>in</span>
          <span>the</span>
          <span>previous</span>
          <span>tests</span><span></span></span></span><span><span><span> o=
n</span>
          <span>all</span>
          <span>tested</span>
          <span>platforms</span></span></span><span><span><span>?</span></s=
pan></span></p>
    <p><span><span><span>I&#39;m</span>
          <span>sure</span>
          <span>I&#39;ve</span>
          <span>removed</span>
          <span>the</span>
          <span>issues</span>
          <span>that</span>
          <span>caused</span>
          <span>those</span>
          <span>errors</span><span>,</span>
          <span>but</span>
          <span>now</span>
          <span>I</span>
          <span>don&#39;t</span>
          <span>have</span>
          <span>any</span>
          <span>feedback</span>
          <span>to</span>
          <span>be</span>
          <span>sure</span><span>.</span></span></span></p>
    <p><span><span><span></span>
          <span>I
            apologise</span> <span>for</span>
          <span>the</span>
          <span>mistakes</span>
          ... <span>of</span>
          <span>youth</span><span>
            ... </span></span></span><span><span>I</span>
        <span>hope</span>
        <span>to</span>
        <span>improve</span></span><span><span><span>.</span></span></span>=
</p>
    <p><span><span><span>Should</span>
          <span>I</span>
          <span>request</span>
          <span>that</span>
          <span>the</span>
          <span>tests</span>
          <span>be</span>
          <span>reactivated</span><span>?</span>
          <span>If</span>
          <span>so</span><span>,</span>
          <span>how</span><span>?</span></span></span>
      <span><span><span></span></span></span></p>
    <p><span><span><span>regards<br>
            Guido Brugnara<br>
          </span></span></span></p>
    <p><br>
      <br>
    </p>
    <div>Il 29/09/25 14:04, Guido Brugnara ha
      scritto:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <p>I would like to thank those who suggested I use an alias for
        the module name.<br>
        <br>
        I have therefore published <a href=3D"https://metacpan.org/release/=
BRUGNARA/Crypt-TimestampedData-0.01-TRIAL" target=3D"_blank" rel=3D"norefer=
rer">https://metacpan.org/release/BRUGNARA/Crypt-TimestampedData-0.01-TRIAL=
</a><br>
      </p>
      <p>Any comments you may have will be taken into consideration
        before final publication.<br>
        <br>
        Thank you!<br>
        Guido Brugnara<br>
        <br>
        <br>
      </p>
      <div>Il 14/09/25 13:15, Guido Brugnara ha
        scritto:<br>
      </div>
      <blockquote type=3D"cite">
       =20
        <p><span>Hello module-authors,<br>
            =C2=A0=C2=A0=C2=A0 I=E2=80=99d like feedback on a new CPAN dist=
ribution I=E2=80=99m
            preparing: Crypt::TSD. It implements reading and writing of
            RFC 5544 =E2=80=9CSyntax for Binding Documents with Time-Stamps=
=E2=80=9D
            containers (file extension .tsd; media type
            =E2=80=9Capplication/timestamped-data=E2=80=9D per RFC 5955).</=
span></p>
        <p><span>In practice, .tsd is used
            notably in Italy; globally, adoption appears limited
            compared to RFC 3161 Time-Stamp Tokens and ETSI/eIDAS
            containers (CAdES/XAdES/PAdES/ASiC).</span></p>
        <p><span>Still, .tsd exists in the
            wild and there is no dedicated CPAN module covering it.
            Based on my survey of open-source options, the only Open
            Source library exposing APIs for RFC 5544/.tsd that I found
            is Bouncy Castle (Java); Crypt::TSD would provide a Perl
            alternative.</span></p>
        <p><span>Planned scope:<br>
            =C2=A0- Read .tsd files and extract the original content and
            associated time-stamp tokens.<br>
            =C2=A0- Create .tsd files from content and existing RFC 3161
            tokens.<br>
            =C2=A0- Provide helpers for basic structural checks; further
            verification utilities may follow.<br>
            =C2=A0- </span><span><span>Provide</span>
            <span>command</span>
            <span>line</span>
            <span>scripts</span>
            <span>to</span>
            <span>read</span><span>/</span><span>write</span>
            <span>.</span><span>tsd</span>
            <span>files</span><span>.</span></span></p>
        <p><span>Before first upload, I=E2=80=99d
            appreciate feedback on:<br>
            =C2=A0- The namespace: does Crypt::TSD look appropriate
            (alternatives: Crypt::TimestampedData, Crypt::RFC5544)?<br>
            =C2=A0- Any API/naming concerns or prior art I should align wit=
h.</span></p>
        <p><span>Thanks in advance for
            your guidance. I=E2=80=99m happy to adjust naming and API based=
 on
            suggestions.</span></p>
        <p><span>Best regards,<br>
            Guido Brugnara<br>
            <br>
          </span></p>
      </blockquote>
    </blockquote>
  </div>

</blockquote></div>

--000000000000442d2006403d625b--