MarkT:
A requirement is not the same thing as a technique. The requirement is to prevent tampering,
not the technique chosen to satisfy the requirement. Sounds like you've been ordered to
do something a particular way, not given a set of functional requirements!
Sorry i think i didnt use the correct word, i should have used technique instead of requirement.
Though what you're saying is absolutely correct, the thing is that my supervisor has told me to use PBC here, i cant use an alternative.
MarkT:
Asymmetric crypto with public key management infrastructure is much more heavyweight than
shared-secret crypto, and is not normally doable on a tiny microcontroller. Yes, that means
a microcontroller is more limited in its options, and that you'd better have distinct shared
secrets for each client.
Yes i understand that asymmetric crypto is more heavy weight, is there no way to implement this at all? What if i were to change from UNO to MEGA? Even that wouldnt suffice?