| 27 Dec 2023 |
 geo_bot | But the command looks the same right | 17:50:55 |
| geo_bot | I'll look soon | 17:51:12 |
| geo_bot | can you tell me what you were doing with the device while you made this capture | 18:21:46 |
| geo_bot | I would like on where you know what you were doing | 18:27:23 |
| geo_bot | ok, let's look at what you do have | 18:38:56 |
| geo_bot | what were you able to figure out before you went hunting for key generation, I noticed that the command 40 c6 sends the same data | 18:41:40 |
| geo_bot | I also noticed that every time it does a set report, the monitor responds with no data | 18:42:15 |
| geo_bot | that means that if 40 e1 02 is a key transmission, there is no key exchange happening because the monitor is not sending any key information to do it with | 18:45:04 |
| geo_bot | Yeah, no key exchange, just alienfx deciding what the key is | 18:49:56 |
| geo_bot | Okay well if the data's getting sent and then the exact same data is getting sent back that's not a true key exchange that's just one side deciding and what the key is | 18:56:09 |
| geo_bot | Also were you doing an effect with movement, it might just be that | 19:34:07 |
| 28 Dec 2023 |
| geo_bot | What was it | 07:10:56 |
| geo_bot | ...is that an array of 7 keys I just saw on that discord server 🤦♂️ why even bother | 07:17:21 |
| geo_bot | It's not that what you are doing is easy, but if you're doing encryption you can do a lot better than storing a few keys client side | 15:59:52 |
|  418cat changed their profile picture. | 16:54:35 |
|  jopejoe1 changed their display name from jopejoe1 to jopejoe1 [4094]. | 18:09:01 |
| 30 Dec 2023 |
|  mat1592 changed their display name from mat#1592 to mat1592. | 04:46:15 |
| jopejoe1 changed their display name from jopejoe1 [4094] to jopejoe1. | 22:04:22 |
| 31 Dec 2023 |
 chr1sno | What device? | 03:00:43 |
| chr1sno | Check for Coolermaster's VID 0x2516 | 03:01:36 |
| chr1sno | otherwise it's likely i2c / SMBus | 03:01:51 |
| chr1sno | They generally partner with CM for any stock RGB controller. The Wraith Prism is / was the same. | 03:02:50 |
| chr1sno | Not sure TBH. | 03:08:48 |
 theroguezeta | This is going to be PCIe to I2C through the driver and not on the CPU SMBus. | 19:38:31 |
| theroguezeta | Yeah, we need to monitor the AMD driver calls to figure this one out. We do not have a tool at the moment to do that like we do with the NvAPISpy tool for NVIDIA cards. | 20:50:18 |
| 1 Jan 2024 |
|  algfree changed their profile picture. | 21:17:18 |
| theroguezeta | The system driver, sure, but not how the OE app interacts with the said driver is not part of their responsiblity. | 23:04:11 |
| 2 Jan 2024 |
| theroguezeta | Start looking for patterns in the data sent. This could be promising! | 00:05:28 |
| theroguezeta | Relevant: https://www.phoronix.com/news/AMDGPU-SMU-14.0-Patches | 00:07:00 |
| theroguezeta | So we need to figure out the SMU i2c then. | 00:07:33 |
