From e1d7138053033688fce374d819f7850d13f29578 Mon Sep 17 00:00:00 2001 From: Nick Sweeting Date: Tue, 12 Apr 2022 19:04:44 -0400 Subject: [PATCH] Updated Security Overview (markdown) --- Security-Overview.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Security-Overview.md b/Security-Overview.md index cf841fb..b54303f 100644 --- a/Security-Overview.md +++ b/Security-Overview.md @@ -18,6 +18,8 @@ ArchiveBox is able to archive content that requires authentication or cookies, b To get started, set [`CHROME_USER_DATA_DIR`](https://github.com/ArchiveBox/ArchiveBox/wiki/Configuration#chrome_user_data_dir) and [`COOKIES_FILE`](https://github.com/ArchiveBox/ArchiveBox/wiki/Configuration#COOKIES_FILE) to point to a Chrome user folder that has your sessions and a wget `cookies.txt` file respectively. +For full instructions on setting up a Chromium user profile see here: https://github.com/ArchiveBox/ArchiveBox/wiki/Chromium-Install#setting-up-a-chromium-user-profile + If you're importing private links or authenticated content, you probably don't want to share your archive folder publicly on a webserver, so don't follow the [[Publishing Your Archive]] instructions unless you are only serving it on a trusted LAN or have some sort of authentication in front of it. Make sure to point ArchiveBox to an output folder with conservative permissions, as it may contain archived content with secret session tokens or pieces of your user data. You may also wish to encrypt the archive using an encrypted disk image or filesystem like ZFS as it will contain all requests and response data, including session keys, user data, usernames, etc. **Things to watch out for:**