Navigation menu

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This usually happens, when you did not specify correct URL(s) for your license keys. Make sure to send us the exact URL(s) the system will be visible from (i.e. https://example.com/owncloud) -> basically everything before index.php. If you plan to use different URLs for the same installation make sure to send us all of them.

The installation did not create the correct tables.

The E2EE app uses 4 tables. On some system configurations the update seemed to fail. Please notify us of your configuration so we can fix the issue.

If you want to manually add the tables here is the current schema:

Code Block
languagesql
titleE2EE Share 1.2.6
CREATE TABLE `oc_e2eeshare_filekeys` (
  `parent_id` bigint(20) unsigned NOT NULL,
  `path` text COLLATE utf8mb4_bin,
  `key_id` varchar(32) COLLATE utf8mb4_bin NOT NULL,
  `filekey` text COLLATE utf8mb4_bin NOT NULL,
  `created` int(10) unsigned NOT NULL,
  KEY `e2ee_parent_id_index` (`parent_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=COMPRESSED

CREATE TABLE `oc_e2eeshare_folderkeys` (
  `folder_id` bigint(20) unsigned NOT NULL,
  `user_uid` varchar(254) COLLATE utf8mb4_bin NOT NULL,
  `key_id` varchar(32) COLLATE utf8mb4_bin NOT NULL,
  `created` int(10) unsigned NOT NULL,
  KEY `e2ee_folderkeys_folder` (`folder_id`),
  KEY `e2ee_folderkeys_user` (`user_uid`),
  KEY `e2ee_folderkeys_userkey` (`user_uid`,`key_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=COMPRESSED

CREATE TABLE `oc_e2eeshare_keys` (
  `user_uid` varchar(254) COLLATE utf8mb4_bin NOT NULL,
  `key_id` varchar(32) COLLATE utf8mb4_bin NOT NULL,
  `public_key` text COLLATE utf8mb4_bin NOT NULL,
  `ip` varchar(45) COLLATE utf8mb4_bin NOT NULL,
  `user_agent` text COLLATE utf8mb4_bin,
  `created` int(10) unsigned NOT NULL,
  `description` text COLLATE utf8mb4_bin,
  KEY `e2ee_user_uid_index` (`user_uid`),
  KEY `e2ee_key_id_index` (`key_id`),
  KEY `e2ee_user_key_index` (`user_uid`,`key_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=COMPRESSED

CREATE TABLE `oc_e2eeshare_shares` (
  `fileid` bigint(20) unsigned NOT NULL,
  UNIQUE KEY `e2ee_fileid_index` (`fileid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin ROW_FORMAT=COMPRESSED

Are there any file size limitations?

Short Answer: no

Long Answer: It depends on your browser, operating system and available RAM. Since the en-/decryption takes place in your browser the file needs to fit within the available memory. Depending on you configuration it should not be a problem sharing files > 2GB although the additional en-/decryption process might require you to wait for quire some time.

How long do you have to wait to have a file de-/encrypted?

De-/Encryption times for small files (<20MB) are barely noticeable on modern systems or even mobile devices. The larger the file gets the more noticeable is the wait after downloading (or before upload starts) - always depending on your hardware.