Say generator

@@nuthinnew3881 He's right. I always called it "Tin Jen" until I saw an old CES video where a Tengen employee called his own company "Tin Gen[ji]" "Gen-ji G is hard G, like again, guy, great and so on"

They're working for me. Are you looking on their Github?

Globalist agenda?

Building secure crypto systems is so hard that expert cryptographers with years of experience still make mistakes. Although flawed, BLE crypto is secure enough for most scenarios. A crypto system created by a non-expert is likely to be significantly more flawed.

Bluetooth 4.2's LE Secure Connections fix the pairing problem, but 4.2 is not widely supported yet. LE Legacy Pairing has crypto issues at pairing-time as well as UI/UX issues in Android/iOS. If you're building a BLE device and you can work around the UI/UX issues, you should probably use Legacy Pairing. While it has pairing-time weaknesses, in the long run it's secure and it's probably better than what most people will invent themselves.

Good evening Mike. I sometimes revise your video, sometimes even began to understand what you are talking about)) my friend do until a prototype security system for a small house. Here we have tried to build different networks on chips TI, STM32, NRF, Silicon Labs. We tried different network 6lowpan, Thread (2.4 GHz, Sub1GHz), BLE, MESH, Bluetooth, 5 (all this is of course a test, not commercial). Whatever you're network is implemented. Now here Bluetooth 5, Bluetooth mesh. Do You think such as sensors are networked Ble Mesh a good choice for the floor of an office building? Or better to take 6lowpan on 868 MHz for example. I understand that this is a difficult question right now I'm just sitting here thinking that with all this iron and stacks to do.

App crashed because of memory violation. if a crafted data is sent, remote code execution could be possible.( bit tricky with ASLR in android)

Yes, if you use the same pairing method you used with 4.0. But there is a better option available now: the "LE Secure Connection". This option even uses the Elliptic Curve version of Diffie-Helman Key Exchange, finally addressing the absurd flaw Ryan exposed so well in this video.

It was intended as a joke but didn't land quite right I guess. Thanks for the feedback.

My N64 plays all regions

You can hardwire existing CIC into your system to bypass copy and region protection. But it won't work with all games. Unfortunately you can't just cut out the CIC reset line in the console like in the prior systems. The console-side CIC on N64 is integrated into PIF chip which does a lot of other things, so if you were to bypass its capability to jam the processor and RAM, you still won't have working inputs and such. It's desirable to have reproduction CIC regardless. There has been active homebrew scene with physical releases on multiple consoles now, on Neo-Geo, Dreamcast, Megadrive - with CIC reproduction, it becomes possible to make new cartridge runs for Nintendo systems too without destroying more existing cartridges.

Jacques Townsend it can still be broken you know