Add support for Code to DBUS

[awlx]

Hi,

as we have the new Pebble daemon Rockpool on SFOS, it would be very nice to send those generated codes to DBUS via setting, each time they are newly generated.

I don't know if this is possible or a security risk. But might be an idea.

Cheers,

[seiichiro0185]

Hi,

I think something like this should be possible to implement (although I didn't use dbus with SFOS till now). I see two possibilities for this;

1. Send the Code and Name of the currently starred token via a dbus event
2. Send all the Names and Codes via dbus (I'll have to check if there is a usable dbus datatype similar to dictionaries / hashes)

Are there any specifics to consider to make this usable for rockpool?

[awlx]

I am sorry to answer this late, totally forgot about it.

I would prefer option 1. I think you maybe need to throw out a notification, but if you have a DBUS implementation it might be also possible to open a issue with rockpool to make it compatible to your app :).

[piggz]

id like something similar for my watch controlling app, and was considering a full totp implementation until i came across this. i was thinking about a dbus interface with a method i could call to retrieve the code for a given name.

[seiichiro0185]

I didn't start any implementation of this yet, since I dont have any experience with dbus programming (especially on SFOS) and didn't get around to take a look at it till now.
Settings storage is there in the latest Code, so I would prefer to have this configurable (and off by default) since, potentially any app could call such a method which imposes a security risk. If no one steps up to implement this and sends me a pull request I might do it in a future version, but can't give any ETA at the moment.