IRC Log Viewer » #firebreath » 2015-04-08

IRC Nick Time (GMT-7) Message
Ashish_ 01:04 hello
jhgj 06:04 hi
taxilian 13:04 kylehuff: I have another task for you, if you're around sometime and have some time. I might find a solution sooner
kylehuff 13:04 taxilian: I'm around now (mostly)
taxilian 14:04 kylehuff: and now I am again as well. we need to figure out what the best way to install the extension and such
kylehuff 14:04 the extension or the native messaging host?
taxilian 14:04 yep =]
so the extension needs to be generated and the ID of the extension needs to be fetched
possibly during the initial cmake process?
and then on build completion and when we install we need to place the manifest with the path to the nativemessagehost executable and the correct extension id
and then the extension needs to not interfere with other extensions
kylehuff 14:04 okay, well, the extension ID is derived from "key" field of the manifest, which could probably be generated easily.
taxilian 14:04 I don't understand how key is generated
or where it comes from
but that sounds like a good place to start
but that sounds like a good place to start
kylehuff 14:04 it comes from chrome; chrome generates a PEM when "packaging" an extension. probably by some hashing/crypto library such as openssl.
it comes from chrome; chrome generates a PEM when "packaging" an extension. probably by some hashing/crypto library such as openssl.
taxilian 14:04 can we generate it from the command line?
kylehuff 14:04 yes, with the chrome binary. probably other ways. I wrote a C util a few years back that packs+signs a directory into a CRX file without needing to call chrome, I'm sure it, or something else could do the generation as well.
taxilian 14:04 probably not much reason that would need to change, is there?
maybe we should have fbgen generate a valid key
maybe we should have fbgen generate a valid key
kylehuff 14:04 if the ID never needs to change, we can use the same pubkey file checked into the project, and it appears easy enough to extract the ID from that; https://https://github.com/dsoprea/ChromeIdGenerator
as an example
taxilian 14:04 I'm assuming most people will want to install their own extension
I know my company wants to :-/
kylehuff 14:04 too easy. all we have to do is generate a public key
taxilian 14:04 it's just a standard public key?
no private key needed?
kylehuff 14:04 as far as I understand, yes.
taxilian 14:04 interesting. so we just need to figure out how to generate that in python, store it in PluginConfig.cmake, and use it to generate the extension
kylehuff 14:04 shouldn't be too difficult
taxilian 14:04 a coworker of mine is working on the problem; he'll probably have a solution soon
a coworker of mine is working on the problem; he'll probably have a solution soon
kylehuff 14:04 as for programmatic installation, that might be problematic. chrome hates anything not installed via the webstore (or group policy on win)
as for programmatic installation, that might be problematic. chrome hates anything not installed via the webstore (or group policy on win)
taxilian 14:04 what do you recommend as the best way to pack it? Using Chrome, or using a util?
kylehuff 14:04 well, for packing without chrome, you either need a util that is statically linked w/ openssl, or a the user will need whatever python modules for that portion. using chrome removes that need, but is terrible if you are using a build/deployment server on the cloud
taxilian 14:04 or at least inconvenient
hmm. python we're not seeing a good way to do it that doesn't require installing an extra component such as pycrypto
kylehuff 14:04 right, and it might be easier now than it was a few years ago. on a machine without X it was a bear.
yeah, that is why I wrote.
*wrote buildcrx
taxilian 14:04 yeah, linux will be more of a pain even
is buildcrx still completely valid?
kylehuff 14:04 if buildcrx is of any use to you, I can give it an appropriate license. having ID generation or even key generation would be great. https://github.com/kylehuff/buildcrx
should be, although, it might be terrible... lol
I haven't even looked at in a while. I have a few people who send me thank you notes here and there, so somebody is using it without complaints
taxilian 14:04 interesting. we'd have to get it building on windows
kylehuff 14:04 yeah.
again, if it is of any use, you are more than welcome
taxilian 14:04 I may; I think to start with we're just going to use python
but eventually it would be nice to have the option of having it all automated in an easier way
right now I need to get this working so I can deploy it
does the size of the key matter?
kylehuff 14:04 I'd have to research, I don't know. it looks like a pretty small key
taxilian 14:04 we'll just try to match an existing one
any idea how to get the id from the key?
without chrome?
http://blog.roomanna.com/12-12-2010/packaging-chrome-extensions
kylehuff 15:04 sorry, got pulled away.
I don't have any experience with that. only packing into a CRX file
taxilian 15:04 no problem, we got it figured out
https://gist.github.com/taxilian/d42b8768b2e3ef5c6998
tested it and it works
kylehuff 15:04 boom