New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

License key in separate settings file? #79

Closed
bcomnes opened this Issue Nov 19, 2014 · 24 comments

Comments

Projects
None yet
3 participants
@bcomnes

bcomnes commented Nov 19, 2014

Hi! I like to publish my sublime text settings to a public repo, but I can't do that now because there is a license key in my LaTeXing settings file.

Is it possible to store that license in a separate settings file so that I can keep my latexing settings checked into version control and publish those settings publicly (while adding the license file to my ignore list)?

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Nov 20, 2014

Contributor

Great idea.. 👍

Contributor

csch0 commented Nov 20, 2014

Great idea.. 👍

@csch0 csch0 added this to the 1.3.0 milestone Nov 20, 2014

@bcomnes

This comment has been minimized.

Show comment
Hide comment
@bcomnes

bcomnes Feb 21, 2015

Any update on this? Really would love to stop wasting a private github repo on my sublime settings just because of the LaTeXing license. If you don't have time, do you have any pointers on how you would like this done for a PR?

bcomnes commented Feb 21, 2015

Any update on this? Really would love to stop wasting a private github repo on my sublime settings just because of the LaTeXing license. If you don't have time, do you have any pointers on how you would like this done for a PR?

@N4M3Z

This comment has been minimized.

Show comment
Hide comment
@N4M3Z

N4M3Z Mar 8, 2015

Simply moving the license information into a file like LaTeXing.sublime-license (the way Sublimerge package does it) seems a reasonable solution to me.

N4M3Z commented Mar 8, 2015

Simply moving the license information into a file like LaTeXing.sublime-license (the way Sublimerge package does it) seems a reasonable solution to me.

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 9, 2015

Contributor

Yes already done that. Will push the new version later tonight.

On 8 Mar 2015, at 22:32, Martin Zeman notifications@github.com wrote:

Simply moving the license information into a file like LaTeXing.sublime-license (the way Sublimerge package does it) seems a reasonable solution to me.


Reply to this email directly or view it on GitHub.

Contributor

csch0 commented Mar 9, 2015

Yes already done that. Will push the new version later tonight.

On 8 Mar 2015, at 22:32, Martin Zeman notifications@github.com wrote:

Simply moving the license information into a file like LaTeXing.sublime-license (the way Sublimerge package does it) seems a reasonable solution to me.


Reply to this email directly or view it on GitHub.

@bcomnes

This comment has been minimized.

Show comment
Hide comment
@bcomnes

bcomnes Mar 9, 2015

Sweet! Glad to hear it 👍 Thankyou

bcomnes commented Mar 9, 2015

Sweet! Glad to hear it 👍 Thankyou

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 9, 2015

Contributor

Added in 1.2.9

Contributor

csch0 commented Mar 9, 2015

Added in 1.2.9

@csch0 csch0 closed this Mar 9, 2015

@bcomnes

This comment has been minimized.

Show comment
Hide comment
@bcomnes

bcomnes Mar 9, 2015

Can you confirm the location of where this LaTeXing.sublime-license lives? (ST3 Settings Folder/Local ?)
and the format of the contents of the file (JSON?)?

bcomnes commented Mar 9, 2015

Can you confirm the location of where this LaTeXing.sublime-license lives? (ST3 Settings Folder/Local ?)
and the format of the contents of the file (JSON?)?

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 10, 2015

Contributor

at the moment its inside the user folder?! Do you think it would make more sense outside this folder and place it in Local like you mentioned?

Contributor

csch0 commented Mar 10, 2015

at the moment its inside the user folder?! Do you think it would make more sense outside this folder and place it in Local like you mentioned?

@bcomnes

This comment has been minimized.

Show comment
Hide comment
@bcomnes

bcomnes Mar 10, 2015

Doesn't matter to me, as long as its described somewhere. Can you describe how to create and use the external license file? I can't figure it out.

bcomnes commented Mar 10, 2015

Doesn't matter to me, as long as its described somewhere. Can you describe how to create and use the external license file? I can't figure it out.

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 10, 2015

Contributor

Normally it should be just a LaTeXing.sublime-license in your user folder. You could please check the latest testing version, it should extract the information automatically now. :) Once the Mendeley issues are resolved this will be included in the normal release.

Contributor

csch0 commented Mar 10, 2015

Normally it should be just a LaTeXing.sublime-license in your user folder. You could please check the latest testing version, it should extract the information automatically now. :) Once the Mendeley issues are resolved this will be included in the normal release.

@bcomnes

This comment has been minimized.

Show comment
Hide comment
@bcomnes

bcomnes Mar 10, 2015

Should it just be JSON formatted like settings file? The only reason I ask is that the sublime licence file is formatted differently despite having the same file extension.

bcomnes commented Mar 10, 2015

Should it just be JSON formatted like settings file? The only reason I ask is that the sublime licence file is formatted differently despite having the same file extension.

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 10, 2015

Contributor

Yes!

Contributor

csch0 commented Mar 10, 2015

Yes!

@bcomnes

This comment has been minimized.

Show comment
Hide comment
@bcomnes

bcomnes Mar 10, 2015

Cool! Thanks for doing this.

bcomnes commented Mar 10, 2015

Cool! Thanks for doing this.

@N4M3Z

This comment has been minimized.

Show comment
Hide comment
@N4M3Z

N4M3Z Mar 11, 2015

This does not seem to work for me. I simply added LaTeXing.sublime-license file into my user folder (.../Sublime Text 3/Packages/User/) which includes the following:

{
    "username": "<myusername>",
    "license": "<mylicense>",
}

However, I am still getting the "unregistered version" warnings.

N4M3Z commented Mar 11, 2015

This does not seem to work for me. I simply added LaTeXing.sublime-license file into my user folder (.../Sublime Text 3/Packages/User/) which includes the following:

{
    "username": "<myusername>",
    "license": "<mylicense>",
}

However, I am still getting the "unregistered version" warnings.

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 11, 2015

Contributor

With the latest testing version??

Contributor

csch0 commented Mar 11, 2015

With the latest testing version??

@N4M3Z

This comment has been minimized.

Show comment
Hide comment
@N4M3Z

N4M3Z Mar 11, 2015

1.2.9. upgraded through Package Control

N4M3Z commented Mar 11, 2015

1.2.9. upgraded through Package Control

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 11, 2015

Contributor

So could you please check the latest testing version. It's almost identical.

On 11 Mar 2015, at 12:00, Martin Zeman notifications@github.com wrote:

1.2.9. upgraded through Package Control


Reply to this email directly or view it on GitHub.

Contributor

csch0 commented Mar 11, 2015

So could you please check the latest testing version. It's almost identical.

On 11 Mar 2015, at 12:00, Martin Zeman notifications@github.com wrote:

1.2.9. upgraded through Package Control


Reply to this email directly or view it on GitHub.

@N4M3Z

This comment has been minimized.

Show comment
Hide comment
@N4M3Z

N4M3Z Mar 11, 2015

Sorry, confused. How can I get it?

N4M3Z commented Mar 11, 2015

Sorry, confused. How can I get it?

@csch0

This comment has been minimized.

Show comment
Hide comment
Contributor

csch0 commented Mar 11, 2015

@N4M3Z

This comment has been minimized.

Show comment
Hide comment
@N4M3Z

N4M3Z Mar 11, 2015

Thank you, all is well now. Sorry for the false alarm.

However, now that I was about to upload my LaTeXing settings to a public repo, I realized that LaTeXing.sublime-settings file still does contain other sensitive information like citeulike_username ,mendeley_oauth_token etc. Perhaps these entries could be moved as well to achieve the original goal?

N4M3Z commented Mar 11, 2015

Thank you, all is well now. Sorry for the false alarm.

However, now that I was about to upload my LaTeXing settings to a public repo, I realized that LaTeXing.sublime-settings file still does contain other sensitive information like citeulike_username ,mendeley_oauth_token etc. Perhaps these entries could be moved as well to achieve the original goal?

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 11, 2015

Contributor

If we start this then pretty much everything has to move. So I guess the best option would be to encrypt the settings itself or? But normally don't like this idea?! Any other suggestions?

On 11 Mar 2015, at 13:38, Martin Zeman notifications@github.com wrote:

Thank you, all is well now. Sorry for the false alarm.

However, now that I was about to upload my LaTeXing settings to GitHub, I realized that LaTeXing.sublime-settings file still does contain other sensitive information like citeulike_username ,mendeley_oauth_token etc. So at least on my side, this means I still have to use encryption. Perhaps these entries should be moved as well?


Reply to this email directly or view it on GitHub.

Contributor

csch0 commented Mar 11, 2015

If we start this then pretty much everything has to move. So I guess the best option would be to encrypt the settings itself or? But normally don't like this idea?! Any other suggestions?

On 11 Mar 2015, at 13:38, Martin Zeman notifications@github.com wrote:

Thank you, all is well now. Sorry for the false alarm.

However, now that I was about to upload my LaTeXing settings to GitHub, I realized that LaTeXing.sublime-settings file still does contain other sensitive information like citeulike_username ,mendeley_oauth_token etc. So at least on my side, this means I still have to use encryption. Perhaps these entries should be moved as well?


Reply to this email directly or view it on GitHub.

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 11, 2015

Contributor

And you have the same for every package where you save something confidential.

Perhaps try this https://github.com/csch0/SublimeText-Package-Syncing

On 11 Mar 2015, at 13:38, Martin Zeman notifications@github.com wrote:

Thank you, all is well now. Sorry for the false alarm.

However, now that I was about to upload my LaTeXing settings to GitHub, I realized that LaTeXing.sublime-settings file still does contain other sensitive information like citeulike_username ,mendeley_oauth_token etc. So at least on my side, this means I still have to use encryption. Perhaps these entries should be moved as well?


Reply to this email directly or view it on GitHub.

Contributor

csch0 commented Mar 11, 2015

And you have the same for every package where you save something confidential.

Perhaps try this https://github.com/csch0/SublimeText-Package-Syncing

On 11 Mar 2015, at 13:38, Martin Zeman notifications@github.com wrote:

Thank you, all is well now. Sorry for the false alarm.

However, now that I was about to upload my LaTeXing settings to GitHub, I realized that LaTeXing.sublime-settings file still does contain other sensitive information like citeulike_username ,mendeley_oauth_token etc. So at least on my side, this means I still have to use encryption. Perhaps these entries should be moved as well?


Reply to this email directly or view it on GitHub.

@N4M3Z

This comment has been minimized.

Show comment
Hide comment
@N4M3Z

N4M3Z Mar 11, 2015

Yes, you are of course right, that this is a problem with any package that contains sensitive data. I am encrypting those files using blackbox (https://github.com/StackExchange/blackbox) as well as using PackageSyncing to backup my settings through Dropbox. Apart from this, I don't have any good ideas on how to approach this.

N4M3Z commented Mar 11, 2015

Yes, you are of course right, that this is a problem with any package that contains sensitive data. I am encrypting those files using blackbox (https://github.com/StackExchange/blackbox) as well as using PackageSyncing to backup my settings through Dropbox. Apart from this, I don't have any good ideas on how to approach this.

@csch0

This comment has been minimized.

Show comment
Hide comment
@csch0

csch0 Mar 11, 2015

Contributor

For me Package Syncing was always enough, that's why I programmed it. :)

Contributor

csch0 commented Mar 11, 2015

For me Package Syncing was always enough, that's why I programmed it. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment