Tag Info

New answers tagged

1

In a nutshell, you are writing a program that reads information from a protected secure storage facility (so it can call external APIs). The secure storage facility itself has it's own authentication (username/password and possibly multi-factor authentication). And the key is that this authentication to the secure storage facility you want to persist ...


2

Conditional compilation effectively creates multiple versions of the code base. That's exactly the purpose of version control branches. The other alternative is put whatever code needs to vary in its own assembly/dll. Different dlls can contain different implementations of the same class (assuming the public fields are the same). Both alternatives have the ...


1

I think Oauth providers (twitter, google, fb) will give you what you want: they (arguably store credentials securely ability to authorise applications (not only users) available from API there's probably more features that interest you All you need is to register your application and make some redirections for authentication. It might be not ideal to use ...


3

What you are looking for is Symmetric encryption when the original data is required again. ie Store the important data using Symmetric encryption. Your application then provides access to external applications that can provide a User and password. The calling tools is authenticated against an Asymmetric stored hash. Such as bcrypt for the Hash. You can ...


2

I am not familiar with plugin development at all. However, where your code is in the source control and how you present it to either browser can be separated by adding a build step. With that model: you have a single branch of development (you could have multiple, but you don't need to) your source is wherever you like it to be two distinct build steps ...


1

You might be trying to use git to handle a situation it was not intended to[citation needed], maybe a build script might be the answer. If Chrome is flexible with the folder structure, you could just follow the folder structure required by Firefox. Have one branch for Chrome and another for Firefox to handle the distinct files, then later do a merged by a ...



Top 50 recent answers are included