From 1fe97ca4823b79e3a88e239db7145796a63c9945 Mon Sep 17 00:00:00 2001 From: Sarah Jamie Lewis Date: Fri, 25 Jun 2021 08:42:24 -0700 Subject: [PATCH] Update link --- src/profile_encryption_and_storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/profile_encryption_and_storage.md b/src/profile_encryption_and_storage.md index c06e49b..5914b28 100644 --- a/src/profile_encryption_and_storage.md +++ b/src/profile_encryption_and_storage.md @@ -8,7 +8,7 @@ it isn't possible to provide a full list of profiles a user might have access to ## Unencrypted Profiles and the Default Password To handle profiles that are "unencrypted" (i.e don't require a password to open) we currently create a profile -with a [default, hardcoded password](https://git.openprivacy.ca/cwtch.im/ui/src/branch/master/go/the/globals.go#L12). +with a [defacto, hardcoded password](https://git.openprivacy.ca/cwtch.im/libcwtch-go/src/branch/trunk/constants/globals.go#L5). This isn't ideal, we would much rather wish to rely on OS-provided key material such that the profile is bound to a specific device, but such features are currently patchwork - we also note by creating an unencrypted profile, people