[services] Backup - Database - add Item
ClosedPublic
Actions

				// @flow

				import olm from '@matrix-org/olm';
				import fs from 'fs';
				import path from 'path';
				import uuid from 'uuid';

				import { main } from './utils';

				const olmConfigRelativePath = './secrets/olm_config.json';

				async function generateOlmConfig() {
				await olm.init();
				const account = new olm.Account();
				account.create();
				const picklingKey = uuid.v4();
				tomekUnsubmitted Not Done Inline Actions It was discussed during a meeting that we do not expect pickling key to provide additional security layer so I'd feel safer if this pickling key was less deterministic, but on the other hand I'm not sure if it is possible for someone to acquire only the pickled account without the key. If an attacker has both, then key security doesn't matter. So we can probably keep the current approach. tomek: > It was discussed during a meeting that we do not expect pickling key to provide additional…
				const pickledAccount = account.pickle(picklingKey);

				const olmConfig = {
				picklingKey: picklingKey,
				pickledAccount: pickledAccount,
				};
				const scriptWorkingDirectory = path.resolve();

				if (!scriptWorkingDirectory.endsWith('comm/server')) {
				throw new Error('Script must be run in server directory in comm project.');
				}

				const olmConfigFilePath = path.join(
				scriptWorkingDirectory,
				olmConfigRelativePath,
				);

				fs.writeFileSync(olmConfigFilePath, JSON.stringify(olmConfig));
				}

				main([generateOlmConfig]);

services/backup/docker-server/contents/server/src/DatabaseEntities/Item.h

				// @flow

				import olm from '@matrix-org/olm';
				import fs from 'fs';
				import path from 'path';
				import uuid from 'uuid';

				import { main } from './utils';

				const olmConfigRelativePath = './secrets/olm_config.json';

				async function generateOlmConfig() {
				await olm.init();
				const account = new olm.Account();
				account.create();
				const picklingKey = uuid.v4();
				tomekUnsubmitted Not Done Inline Actions It was discussed during a meeting that we do not expect pickling key to provide additional security layer so I'd feel safer if this pickling key was less deterministic, but on the other hand I'm not sure if it is possible for someone to acquire only the pickled account without the key. If an attacker has both, then key security doesn't matter. So we can probably keep the current approach. tomek: > It was discussed during a meeting that we do not expect pickling key to provide additional…
				const pickledAccount = account.pickle(picklingKey);

				const olmConfig = {
				picklingKey: picklingKey,
				pickledAccount: pickledAccount,
				};
				const scriptWorkingDirectory = path.resolve();

				if (!scriptWorkingDirectory.endsWith('comm/server')) {
				throw new Error('Script must be run in server directory in comm project.');
				}

				const olmConfigFilePath = path.join(
				scriptWorkingDirectory,
				olmConfigRelativePath,
				);

				fs.writeFileSync(olmConfigFilePath, JSON.stringify(olmConfig));
				}

				main([generateOlmConfig]);