Skip to content
This repository has been archived by the owner on Oct 18, 2024. It is now read-only.

Can't decrypt on different machine after importing credentials #60

Open
5 tasks done
AIMCRYPTION opened this issue Nov 1, 2020 · 1 comment
Open
5 tasks done
Labels
Milestone

Comments

@AIMCRYPTION
Copy link

AIMCRYPTION commented Nov 1, 2020

Prerequisites

  • Can you reproduce the problem?
  • Did you read the entire README.md?
  • Did you read the FAQs?
  • Do you fully understand how Crypter works and how to use it?
  • Did you check the issues to see if your bug or enhancement is already reported?

Description

Encrypt and decrypt only works on source machine, when export credentials and import them on different machine it doesn't work at all. Also after importing credentials, verification page doesn't show up as well. So Encrypt and decrypt only works on source machine, which isn't convenient and not secure.

Steps to Reproduce

  1. My suggestion is to not save the MasterPass in OS keychain
  2. [Second Step]
  3. [and so on...]

Expected behavior: [What you expected to happen]

Actual behavior: [What actually happened]

Versions

Crypter:

Release (full release name): Crypter 5.0.0

Operating System (name and version): Windows 10 2004

You can find the full release name under https://github.com/HR/Crypter/releases. For version 3.0.0 and up, the version is found under Crypter > About or just in the menu Version X.Y.Z.

@HR HR added this to the v5.0 milestone Nov 10, 2020
@HR HR added the bug label Nov 10, 2020
@HR
Copy link
Owner

HR commented Nov 10, 2020

Thanks for reporting this issue @AIMCRYPTION

This due to Crypter not asking and saving/updating the MasterPass on importing the credentials. So this is something that needs to be implemented to make the Keychain stuff work with the migration. However, this does not compromise the security since no secrets are leaked.

Since we don't have this problem with v4.0.0 and I am too busy to fix this right now, I have downgraded the version in the README and marked the current v5.0.0 as an alpha release.

You are welcome to open a PR to fix this! Would be well appreciated!

I'd be more than happy to provide any support needed to do so :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants