Enable (even) longer encryption passwords #416

Closed
securitymanager opened this Issue Sep 4, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@securitymanager

securitymanager commented Sep 4, 2016

Hello everyone!

Could someone explain to me why the website says there is a limit of 32 characters for the encryption password? Please correct me if I'm wrong, but many other custom ROMs in combination with an app like "Cryptfs Password" would enable the user to choose encryption passwords that are much longer than 32 characters. Why is there such limit of characters for a password in a ROM that aims to provide the best security for its users?

Thank you very much!

@securitymanager securitymanager changed the title from (Even) longer encryption passwords to Enable (even) longer encryption passwords Sep 4, 2016

@thestinger

This comment has been minimized.

Show comment Hide comment
@thestinger

thestinger Sep 4, 2016

Contributor

The issue tracker isn't going to be used for providing support / answering questions. There are no changes to this area in the current Nougat-based CopperheadOS anyway, and there's support for a new encryption format where things work differently.

Contributor

thestinger commented Sep 4, 2016

The issue tracker isn't going to be used for providing support / answering questions. There are no changes to this area in the current Nougat-based CopperheadOS anyway, and there's support for a new encryption format where things work differently.

@thestinger thestinger closed this Sep 4, 2016

@securitymanager

This comment has been minimized.

Show comment Hide comment
@securitymanager

securitymanager Sep 4, 2016

I guess I accidentally misused the tracker. I also found a subreddit and now I think I should have opened a topic there instead of opening one in here. Still: It would have been nice to read one or two short sentences or receive a link which directly addresses the

new encryption format where things work differently.

I'm sure other users are also searching the internet for this question and thus the creation of new topics with the same question or in the wrong place could be avoided in the future.

Thank you very much!

securitymanager commented Sep 4, 2016

I guess I accidentally misused the tracker. I also found a subreddit and now I think I should have opened a topic there instead of opening one in here. Still: It would have been nice to read one or two short sentences or receive a link which directly addresses the

new encryption format where things work differently.

I'm sure other users are also searching the internet for this question and thus the creation of new topics with the same question or in the wrong place could be avoided in the future.

Thank you very much!

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