I read an academic paper in the past 5 years (can't cite it off the top of my
head, though) that performed cryptographic authentication of streaming data in
the following manner.
Streaming Data :
[
[Payload 0][SigByte 0]
[Payload 1][SigByte 1]
[Payload 2][SigByte 2]
...
[Payload N][SigByte N]
]
Where
256 < Sizeof(Payload) < 1024
and
SigByte N := LeastSignificantByte( CryptographicSignature( Payload N ))
Each transmission frame (or maybe a superframe) has one byte of signature. By
itself, one byte of authentication is not very trustworthy. But as N becomes
large, the trust of the streaming signature becomes strong. In other words, if
you do this over 64 payloads or more, it's good enough for amateur purposes.
!!Dean
KC4KSU
On Aug 27, 2016, at 11:18 AM, Steve wrote:
>
> That provides a second problem. What to do with an extra 63 bits? Not quite
> enough for 6 bit amateur callsign routing, but I'm sure there is a lot of
> ideas out there.
>
> 73/steve
> ------------------------------------------------------------------------------
> _______________________________________________
> Freetel-codec2 mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
------------------------------------------------------------------------------
_______________________________________________
Freetel-codec2 mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
