[Cryptography] Renewable Identities - Dynamic PII

[Govind Yadav]

Hello Team,

We recently filed a patent on 'Renewable Identities - Dynamic PII'.
The novelty offered by this (patent pending) technique relates to safeguarding PII by offering Dynamic Personally Identifiable Information (DPII) which completely eliminates static PII & cannot be compromised by means of :

a) Card skimming & social engineering fraud
b) Phishing, vishing, smishing
c) Pharming & Man-In-The-Middle (MITM)
d) Photo copy fraud & replay attack
e) Insider fraud and Database breach, etc.

The PPT (converted to PDF) is available here<https://www.dropbox.com/scl/fi/9gxoxdmyk40x4pf56l712/Renewable_Identities_OTPI_OTCI_NB_2024_PPT_v2.3.pdf?rlkey=so2tqngnf85jang2lpzyqmstx&dl=0>
This has links to a more detailed datasheet and even more detailed whitepaper.

The core concept relies on symmetric crypto. Ancillary components will leverage asymmetric crypto and PKI.

Would appreciate feedback on the concept and, most importantly, if someone can punch a hole in the threat mitigation 🙂


Looking forward to hearing from you...


Regards

Govind

________________________________
From: cryptography <cryptography-bounces+yadavgovind=hotmail.com at metzdowd.com> on behalf of cryptography-request at metzdowd.com <cryptography-request at metzdowd.com>
Sent: Wednesday, May 15, 2024 5:00 PM
To: cryptography at metzdowd.com <cryptography at metzdowd.com>
Subject: cryptography Digest, Vol 133, Issue 5

Send cryptography mailing list submissions to
        cryptography at metzdowd.com

To subscribe or unsubscribe via the World Wide Web, visit
        https://www.metzdowd.com/mailman/listinfo/cryptography
or, via email, send a message with subject or body 'help' to
        cryptography-request at metzdowd.com

You can reach the person managing the list at
        cryptography-owner at metzdowd.com

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cryptography digest..."


Today's Topics:

   1. Re: Wring isn't as secure on big messages as I thought
      (Pierre Abbat)


----------------------------------------------------------------------

Message: 1
Date: Tue, 14 May 2024 06:25:38 -0400
From: Pierre Abbat <phma at bezitopo.org>
To: cryptography at metzdowd.com
Subject: Re: [Cryptography] Wring isn't as secure on big messages as I
        thought
Message-ID: <6771489.XQYqjrCR6X at puma>
Content-Type: text/plain; charset="UTF-8"

On Friday, May 10, 2024 4:16:23 PM EDT Pierre Abbat wrote:
> Can you think of a better mix3parts pattern, or should I simply increase the
> number of rounds?

The mix3parts pattern, with the number near len/? (len is 1/3 of the message
size) that's of maximal order (a primitive root of len, if there are any), is
not the problem. I ran a simulation of enciphering a megabyte, assuming that
mix3 results in any byte affecting all three. With all rotations being by
integral numbers of bytes, the number of affected bytes grew as 1, 3, 9, 27,
27, 81, 243, 729, 2187, 6546. At this point there were collisions of the
affected bytes. With rotations being by any number of bits, the growth factor
was between 4.42 and 4.72.

I think the slow growth is due to two factors:

1. When the rotation is by 8n?1, a changed byte affects one byte most of the
time, and a single bit of another byte half the time.

2. When three bytes are mixed, a single bit change in one byte either affects
that byte or affects the other two bytes, but not both.

I'm going to increase the number of rounds.

Pierre
--
li fi'u vu'u fi'u fi'u du li pa





------------------------------

Subject: Digest Footer

_______________________________________________
cryptography mailing list
cryptography at metzdowd.com
https://www.metzdowd.com/mailman/listinfo/cryptography


------------------------------

End of cryptography Digest, Vol 133, Issue 5
********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.metzdowd.com/pipermail/cryptography/attachments/20241016/80d8b478/attachment.htm>