[saag] Re: Fwd: Submission – RFC 4269 (SEED) – Observational Errata + Firmware Behavior

[ trimmed working group lists to a minimum ]

I went through the attached files, and none of this is related to IETF
specifications. You seem to suggest you
have an errata for RFC 4269 (SEED), but there is no text explaining what
the error in the specification is. As
this RFC defines a cryptographic algorithm, there would also be no real
possibility of changing it, as the
results would be a different cryptographic algorithm and no longer be
considered SEED.

Furthermore, errata's should be submitted via
https://www.rfc-editor.org/errata.php that will assist you with
the proper format of CURRENT and NEW text to address a found errata.

Note further that SEED is an old algorithm that is not in common use. For
example, while IKEv1/IPsec had
a code point for using SEED, IKEv2 no longer supports it. For TLS, these
algorithms are defined but the
document deprecating these (draft-ietf-tls-deprecate-obsolete-kex-05) is
about to become an RFC.

Based on the content of your zip file, there seem no possible actions that
can or need to taken by the IETF.

If you have further questions, feel free to contact me but please do not
mail a dozen different IETF mailing lists
at once.

Thanks,

Paul Wouters
Security Area Director


On Fri, May 16, 2025 at 5:20 AM <[email protected]> wrote:

>
> > ---------- Original Message ----------
> > From: [email protected]
> > To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>
> > Date: 05/08/2025 11:18 PM CEST
> > Subject: Submission – RFC 4269 (SEED) – Observational Errata + Firmware
> Behavior
> >
> >
> > # IETF Submission – RFC 4269 Related Errata + Supplementary Observation
> (May 2025)
> >
> > To: [email protected]
> > From: Alexander C. (Fragle Systems)
> > Subject: Submission – RFC 4269 (SEED Algorithm) – Suspected Anomalies +
> Related Observations
> >
> > ---
> >
> > ## Submission Overview
> >
> > This ZIP archive includes evidence and observations related to potential
> irregularities and broader telemetry implications involving the SEED
> encryption algorithm as described in RFC 4269.
> >
> > Two documents are included that may constitute **errata triggers**:
> > - Observed firmware behavior that mirrors elements from RFC 4269 cipher
> routines
> > - System interactions that suggest algorithmic presence in non-declared
> cryptographic implementations
> >
> > Supporting files show:
> > - Firmware persistence
> > - Network trace anomalies
> > - Credential traces and packet-related activity
> > - Device behavior consistent with undocumented cryptographic presence
> >
> > ---
> >
> > ## Structure
> >
> > - `draft-list.csv`, `rfc4269.txt.pdf` – reference tracking and RFC
> material
> > - `Firmware_Exploitation_Incident_Report_UPDATED*.pdf` – main incident
> narratives
> > - `supplementary_evidence/` – categorized traces, screenshots, log
> fragments
> >
> > ---
> >
> > ## Purpose
> >
> > This submission is intended to:
> > - Notify IETF of suspected behavior that may intersect with or trigger
> errata to RFC 4269
> > - Provide organized evidence for analysis
> >
> > I appreciate confirmation of receipt and would be grateful if you could
> let me know:
> >
> > - Whether the submission was received intact (attachments opened
> successfully)
> > - If any procedural steps are required for tracking or logging this as a
> potential RFC 4269 errata-related observation
> > - Whether follow-up contact or clarification is needed regarding any
> portion of the material
> >
> > All data is collected via isolated, offline analysis with full consent
> of device owner(s).
> >
> > Please advise on procedural next steps.
> >
> > Thank you for your time and attention.
> >
> > Kind regards,
> > Alexander Kristoffersen
> > aka “almao” /
> “invisiblepancake”_______________________________________________
> saag mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

_______________________________________________
saag mailing list -- [email protected]
To unsubscribe send an email to [email protected]