YouTube ideas for Imporvement are Great !!!

[bionicbone]

YouTube Video and Comments for reference. https://youtu.be/TpmY-2w8CTI

Credits to: [@deterdamel7380] [@AllanSavolainen] [@jamesharding7536] [@bsmerchants] [@ajinkyakamat7053] Sorry if I missed anyone :)

The next bullet point has been implimented

• Once the loop of codes has been used change the numbers by a predetermined init-value to all numbers in rollingCode[], thus the codes would never cycle, and when the init-value is added there will be no way to reverse engineer the init-value from the previous last value in the loop to the next first number in the loop, unless you had recorded the first number and somehow worked out the loop was about to renew.

After research, this next bullet point is not required for this project. The reason for encryption & hash in verious methodologies are to hide the original data due to the risk of reverse engineering the algorithm that created the next value. However, given my list of codes were not created by an algorithm there is no such reverse angineering possible, therefore presenting the raw data adds no risk. End users are encouraged to create their own unique list of numbers, either using the inbuilt method or some other method like hex editor value of a file, each user has a unique system, the length of the loop, the size of the code, the init-value to be added after the full loop of numbers has been consumed etc.

• Research Required: HOTP algorithm, although the reason for hashing is so the init-value cannot be reverse engineered, so do I need? HMAC HOTP is better used as TOTP implimention, probably not possible using these basic RF devices due to latency.

After research this next bullet point probably is a threat, I intend to build a RollJam device so I can play and learn how to detect it so I can close the system down - Watch this space, created issue #15 to track progress on this!!

• RollJam, build such a device for testing. Once understood it should be possible to detect it on transmission and make the fob vibrate so the user is aware of potential attack, on the receiver send a text message to mobile phone warning of such activity being close by.

After research RollBack is not a threat to my methodoligy

• RollBack, is a method whereby playing several old messsages back to back causes the system to roll back to a previous code. This would not effect my device, but ensure we dont use this method as a reset function.

As per HOTP

• Potentially add a hash of the date and time of the transmission (TOTP), then check this so older “recordings” are invalid. I like this, not possible with these 433MHz devices due to the nibble binary issue and slow latency but one for the future with faster 433MHz serial devices. TOTP as already been hacked October 2023, hash and key available

[bionicbone]

More great ideas derived from YouTube comments [@thebagmasters] [@bennymegidish]

The next bullet point has been implimented

• after ten unsuccessful attempts we could assume a brute force attack and stop validating transmissions for x seconds, getting long on each attampt. Eventully (once added) a text message could be sent to the owner let them know lock down had been activated and for how long.

The next bullet point has been implimented

• if the user press the Tx for > 5 seconds the Tx should transmit a "forced rolling" unique code. This code will be less numbers (user configrable) than standard code, forcing the read routine to timeout. This time out will check the received code to see if it matches the "Forced Roll" code and then the Tx & Rx should ApplyInitValueToRollingCodeLoop() in a way to reset the number sequence with a fresh set of numbers. The hacker would not know to send 1, 2, 3 less numbers for this "forced roll" to happen. Its not perfect but could provide a way to resync.

[bionicbone]

All these YouTube emhancements have been completed