Version file points to ccMSC github

[frickler24]

If new versions may be downloaded and installed, src/ckb/kbfirmware.cpp references a file in github which belongs to ccMSC (line 35):
(tableDownload = networkManager->get(QNetworkRequest(QUrl("https://raw.githubusercontent.com/ccMSC/ckb/master/FIRMWARE")));
That file is signed by him via GnuPG and needs an update for the M65RGB at least.

The incidents looks as follows:
My current FW is 1.19 for the M65RGB, but corsair has a new one (2.04).

So I get a hint in ckb to upgrade, but that hint is wrong: Because in the file mentioned the latest version is 2.02, it tries to update to this version, but gets 2.04 from corsair.

The manual activation was a bit difficult, because ckb did not recognize the "alt" key. I hacked the code and could burn the new FW manually. M65RGB runs fine.

[mattanger]

I'm aware of this issue, and I just haven't had a chance to do anything about it yet. I'm going to do work on addressing this shortly.

[frickler24]

Can I help you?
If we create a new pub/priv Key pair just for this purpose, more than one person is able to update the info.

@frickler24 this is definitely an important issue, if you come up with an extensible solution (like the proposed one), I guess @mattanger won't be against.

P. S. thanks for the hardware profile fixes, much appreciated.

[mattanger]

I'm not opposed to it.

[frickler24]

Does anyone have the following HW + firmware running with ckb 0.2.7?
Firmware for Scimitar is a 2.4 available, for Strafe 2.05 (non-RGB)?

The last entries for these two are less than the current downloads.
Problem is, if I put the current links into the FW-Checker and that combination is not running with ckb, we could stop working some equipment.

[mattanger]

@frickler24 What are you working on in regards to resolving this issue? I was planning on signing a new firmware file for now, but if you've got a nice solution in the works I don't want cause you an issue.

[frickler24]

@mattanger I'm just preparing the pullreq. First I have seen some more infos for the K70.

[mattanger]

Awesome. Haven't had a chance to check it yet, but I will tomorrow.

…

On Feb 4, 2017 11:57 AM, "Lutz" ***@***.***> wrote: @mattanger <https://github.com/mattanger> I'm just preparing the pullreq. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFM7GmTgE1Gj1j_jnKKsBMwpmZ-Z9A7uks5rZK3mgaJpZM4Lj9OB> .

[mattanger]

Merged #60