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.

Sign up for GitHub

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

Jump to bottom

UX: RECIPIENT #61

Closed
proyb6 opened this issue Dec 31, 2019 · 2 comments
Closed

UX: RECIPIENT #61

proyb6 opened this issue Dec 31, 2019 · 2 comments

Comments

@proyb6
Copy link

proyb6 commented Dec 31, 2019

What were you trying to do

Tried to understand the purpose of RECIPIENT

What will it happen if someone tried to brute force with RECIPIENT key, are the mechanism to avoid encrypted files in form of binary or plaintext from being decrypt?
@southwindcg
Copy link

southwindcg commented Dec 31, 2019 •
edited
Loading

Recipients' public keys [as generated by age-keygen] are 62 alphanumeric characters long (although they all begin with 'age1' as far as I can tell) and I think that length rules out brute forcing. I'm not a domain expert, so hopefully someone else can add more insight.

@proyb6
Copy link
Author

proyb6 commented Dec 31, 2019 •
edited
Loading

I seen it also use Scrypt on passphrase which made brute force inefficient.

Other approach I thought is file splitting could work as some commercial service does it.

@proyb6 proyb6 closed this as completed Jan 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@proyb6 @southwindcg