Pachube Keys
9 January, 2012 - 12:10
I had a xap-livebox.ini corruption and had to reset everything.
It seems that Pachube have updated their keys model and I had to generate a new one.
The thing is - it doesnt seem to be pasting all of the key into the text box on the webgui - is the new key too long?
My key is now approx 128 characters long.
My feed 10591 is now frozen.
Is this a bug?
9 January, 2012 - 12:28
#2
Key Change
I think you are right, the existing key can be up to 65 characters long. The HAH code will need changing to correct this.
9 January, 2012 - 13:27
#3
Manual Edit
You could try editing the ini file directly, just don't update pachube through the web gui after you do this. From the web gui, fill in all the details, enter a dummy apikey, and save them, then edit the xap-livebox.ini file. Find the [pachube] section, then replace the "dummy" apikey with your new apikey, the field name in the ini file is key.
I don't have access to my system at the moment, so I'm not sure if the web gui tries to check the apikey before saving it, it might, so the above might not work.
9 January, 2012 - 13:43
#5
Yep, it's a buffer overflow.
Yep, it's a buffer overflow. The web gui loads the data, but it's too long to fit the variable, so it overwrites stuff and corrupts things. I'm pretty sure it's a quick fix, and Brett is always keen to get stuff like this fixed asap. I can test what I think the fix would be tonight, and see about getting that to you, but it wouldn't surprise me if Brett's fixed it before then.
I take it you've looked everywhere for your old key?
9 January, 2012 - 14:02
#6
Not a buffer overflow just not enough of it.
I take it nobody is using the BACKUP/RESTORE facility I put in place to prevent your data from being lost?
The internal buffers where not large enought to cope with an unforseen and unscheduled change in PACHUBE's API key length, this is pretty shitty of them actually. I've pushed up build 302 but I've not TESTED the increases I've made - I can no longer test anything (no livebox).
Hopefully I got them all.
Brett
9 January, 2012 - 14:50
#9
I do
And very handy it is as well.
9 January, 2012 - 14:56
#10
Wierd
Very strange might have had something to do with your corrupt .ini file when you reflashed although I don't see how. The default IP if setting up for a static network and and you are missing the IP address we use 192.168.1.50. DHCP should not be handing out a duplicate IP either, esp not the routers IP. If its is using the routers IP simple leave your livebox up, and cable direct to your PC and setup a small network so you can break back in and have a look.
In anycase I didn't change any code or logic around this area in this build. Shrug.
- Brett
Though I would post the contents of /var/log/xap-pachube.log :
Pachube Connector for xAP v12
Copyright (C) DBzoo 2009-2010
[crt][main.c:134:getDynINI] INI file missing [pachube] section1=<value>