Use Session Session Private Messenger Chat with Kicksecure

From Kicksecure
Revision as of 04:30, 22 December 2024 by TheUnderpricedDonkey (talk | contribs) (Line 17 - published gpg fingerprint of apt signing key / Line 19 - reference to Published fingerprint of Jason's GPG signing key on Github - gpg fingerprint finally published by KeeJef)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Session Private Messenger Logo

How-To: Use Session Private Messenger with Kicksecure.

Introduction[edit]

Documentation for this is incomplete. Contributions are happily considered! See this for potential alternatives.

Session Private Messenger Security[edit]

Install the Session Desktop Client[edit]

warning Security warning: Adding a third party repository and/or installing third-party software allows the vendor to replace any software on your system. Including but not limited to the installation of malware, deleting files and data harvesting. Proceed at your own risk! See also Foreign Sources for further information. For greater safety, users adding third party repositories should always use Multiple Kicksecure to compartmentalize VMs with additional software.

Kicksecure default admin password is: changeme Documentation in the Kicksecure wiki provides guidance on adding third-party software from different upstream repositories. This is especially useful as upstream often includes generic instructions for various Linux distributions, which may be complex for users to follow. Additionally, documentation Kicksecure usually has a higher focus on security, digital software signatures verification.

The instructions provided here serve as a "translation layer" from upstream documentation to Kicksecure, offering assistance in most scenarios. Nevertheless, it's important to acknowledge that upstream repositories, software may undergo changes over time. Consequently, the documentation on this wiki might need occasional updates, such as revised signing key fingerprints, to stay current and accurate.

Please note, this is a general wiki template and may not apply to all upstream documentation scenarios.

Users encountering issues, such as signing key problems, are advised to adhere to the Self Support First Policy and engage in Generic Bug Reproduction. This involves attempting to replicate the issue on Debian bookworm, contacting upstream directly if the issue can be reproduced as such problems are likely unspecific to Kicksecure. In most cases, Kicksecure is not responsible for, nor capable of resolving, issues stemming from third-party software.

For further information, refer to Introduction, User Expectations - What Documentation Is and What It Is Not.

Should the user encounter bugs related to third-party software, it is advisable to report these issues to the respective upstream projects. Additionally, users are encouraged to share links to upstream bug reports in the Kicksecure forums and/or make edits to this wiki page. For instance, if there are outdated links or key fingerprints in need of updating, please feel free to make the necessary changes. Contributions aimed at maintaining the currentness and accuracy of information are highly valued. These updates not only improve the quality of the wiki but also serve as a useful resource for other users.

The Kicksecure wiki is an open platform where everyone is welcome to contribute improvements and edits, with or without an account. Edits to this wiki are subject to moderation, so contributors should not worry about making mistakes. Your edits will be reviewed before being made public, ensuring the integrity and accuracy of the information provided.

1. Add the Session GPG key to the APT keyrings. [1]

To add the signing key, follow steps A to C.

A. Securely download the key.

Kicksecure

If you are using Kicksecure (kicksecure), run.

Click = Copy Copied to clipboard! scurl https://deb.loki.network/pub.gpg --output loki.gpg

Qubes

If you are using a Qubes Template (kicksecure-17), run. [2] [3]

Click = Copy Copied to clipboard! http_proxy=http://127.0.0.1:8082 https_proxy=http://127.0.0.1:8082 scurl https://deb.loki.network/pub.gpg --output loki.gpg

B. Display the key's fingerprint.

Optional for better security. If you are interested, click on Expand on the right.

C. Copy the signing key to the APT keyring folder. [7]

Click = Copy Copied to clipboard! sudo cp loki.gpg /usr/share/keyrings/loki.gpg

2. Add the Session third-party APT repository. [8]

Click = Copy Copied to clipboard! echo 'deb [signed-by=/usr/share/keyrings/loki.gpg] tor+https://deb.loki.network bookworm main' | sudo tee /etc/apt/sources.list.d/loki.list

3. Install Session.

Install package(s) session-desktop following these instructions

1 Platform specific notice.

2 Update the package lists and upgrade the systemOnion Logo.

Click = Copy Copied to clipboard! sudo apt update && sudo apt full-upgrade

3 Install the session-desktop package(s).

Using apt command line --no-install-recommends optionOnion Logo is in most cases optional.

Click = Copy Copied to clipboard! sudo apt install --no-install-recommends session-desktop

4 Platform specific notice.

  • Kicksecure: No special notice.
  • Kicksecure-Qubes: Shut down Template and restart App Qubes based on it as per Qubes Template ModificationOnion Logo.

5 Done.

The procedure of installing package(s) session-desktop is complete.

4. Done.

The process of installing Session is complete.

5. Note.

  • Kicksecure: No extra steps required.
  • Kicksecure-Qubes: Shutdown kicksecure-17 Template. Restart Kicksecure (kicksecure App Qube).

Usage[edit]

Click = Copy Copied to clipboard! session-desktop

Footnotes[edit]

  1. ↑ https://github.com/oxen-io/session-desktop/issues/1397#issuecomment-754945698archive.org iconarchive.today icon
  2. ↑ Using Qubes UpdatesProxy (http://127.0.0.1:8082/archive.org iconarchive.today icon) because Qubes Templates are non-networked by Qubes default and therefore require UpdatesProxy for connectivity. (APT in Qubes Templates is configured to use UpdatesProxy by Qubes default.)
  3. ↑ Even more secure would be to download the key Disposable and then qvm-copyarchive.org iconarchive.today icon it to the Qubes Template because this would avoid curl's attack surface but this would also result in even more complicated instructions.
  4. ↑ Even more secure would be to display the key in another Disposable because this would protect the Template from curl's and gpg's attack surface but this would also result in even more complicated instructions.
  5. ↑ Minor changes in the output such as new uids (email addresses) or newer expiration dates are inconsequential.
  6. ↑ publish OpenPGP / gpg fingerprint of APT signing key #2309archive.org iconarchive.today icon gpg fingerprint of APT signing key has finally been published by KeeJefarchive.org iconarchive.today icon 
    6636 1D8E 3C96 E41C 6DCB  7051 C499 2CE7 A88D 4262
  7. ↑ https://forums.whonix.org/t/apt-repository-signing-keys-per-apt-sources-list-signed-by/12302archive.org iconarchive.today icon
  8. ↑ See this for a comment why tor+ is useful even inside Kicksecure.
Your support makes
all the difference!

We believe security software like Kicksecure needs to remain Open Source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!

Retrieved from "https://www.kicksecure.com/w/index.php?title=Session&oldid=89735"