Skip to content
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

Inconsistent usage of clone.password/clone.salt vs pgclone.password/pgclone.salt #19

Merged
merged 2 commits into from Apr 27, 2019

Conversation

4 participants
@needo37
Copy link
Contributor

commented Apr 26, 2019

Running through the install it creates the proper passwords in clone.password and clone.salt and leaves pgclone.password and pgclone.salt blank. Whereas keys.sh looks for pgclone.* to generate the rclone.conf. Thus having rclone obscuring an empty file causing encryption not to work.

needo37 added some commits Apr 26, 2019

@Admin9705

This comment has been minimized.

Copy link
Member

commented Apr 26, 2019

ah nice reveiw!

@Admin9705

This comment has been minimized.

Copy link
Member

commented Apr 26, 2019

thanks @robertbaker

@Admin9705 Admin9705 merged commit 65d3bd0 into PGBlitz:v8.6 Apr 27, 2019

@antigravity83

This comment has been minimized.

Copy link

commented Apr 27, 2019

Does this fix the issue I was experiencing yesterday, where encyrpted files in Team Drive couldn't be read by the rclone mount?

@needo37

This comment has been minimized.

Copy link
Contributor Author

commented Apr 27, 2019

It does!

@antigravity83

This comment has been minimized.

Copy link

commented Apr 27, 2019

Great news thanks for replying and fixing the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.