AWAMARKET

Home//Client//C5 Tails on a stick

C5Awazon Market // record C5

C5 // Installed system to Tails

One property, held very firmly: the session leaves no trace on the machine. Everything good and everything awkward about Tails follows from that single sentence.

Awazon Market // onion addresses

The three strings below open the same market. The same account, the same balance, the same open orders sit behind each one. Copy a string, paste it into Tor Browser, and read the last six characters in the address bar before you type a password.

  • awazonozc4jwyrveu4473igv5ldt2hnccl2s7lerm2z27cvrc22e4uyd.onion
  • awazonth6ocz5cyos63czmhtsglqr7ydkdcc4lopux7nxbauoo2qmvyd.onion
  • awazonvaqbgkhirejon6qnlxcjibrhkqhzh2xb2lclc6t67vxhlvjkyd.onion

NOTHING HERE IS RANKED. THE ORDER IS THE ORDER THEY WERE WRITTEN IN.

Baseline
Your normal installed operating system, which remembers everything by design.
Substitution
Tails booted from a USB stick, running in memory, with the installed drives untouched.
What moves
Nothing about the session is written to the machine. All traffic is forced through Tor at the system level, so no application can leak around it. The state you start with is the state the image shipped with.
Does not move
The addresses, the market, the genuineness of what you open, and anything you deliberately save to a persistent volume.
Cost
A reboot to start and a reboot to stop, no saved bookmarks or wallet unless you set up persistence, hardware that sometimes does not cooperate, and a stick that must be written from a verified image.
Verdict
Only if the machine you use is the thing you need to keep clean, or is not yours.

IWhat amnesia actually buys

On an ordinary system a session leaves a long tail: browser caches, thumbnails, swap, journal entries, recently opened lists, and files in temporary directories that survive far longer than people assume. Deleting the obvious ones does not remove the rest. Tails avoids the problem by never creating it: the whole system lives in memory and the memory is wiped at shutdown.

The second property is just as important. Networking is enforced at the system level, so an application that tries to connect directly cannot. On a normal machine, a misconfigured tool routing around Tor is a real and quiet failure mode. Under Tails it is not possible.

IIGetting it right

  1. 01Download the image from the project itself and verify it. An unverified image is a system you have no reason to trust more than the one you are replacing.
  2. 02Write it to a stick used for nothing else.
  3. 03Decide about persistence deliberately. Encrypted persistence gives you a place for a wallet and bookmarks and reduces the amnesia to whatever you put in it.
  4. 04Set an administration password only when a session needs one. It defaults to none for a reason.

IIIWhere it is the wrong tool

If the machine is yours, encrypted, and used by nobody else, the amnesia is solving a problem you may not have, and the friction is real: every session begins with a reboot and ends with losing whatever you did not save. People respond to that friction by using Tails for the careful sessions and their normal system for the quick ones, which puts the important part of the activity on the machine they were trying to keep clean.

IVWhat it does not do

It does not check addresses. A clone opened under Tails is a clone, and the password goes to the same place. It also does not separate identities: two accounts used in one Tails session are two accounts used in one session, which is record I4 and not this one.

CONDITION

Right when the machine must stay clean or is not yours. Wrong as a general upgrade on a private, encrypted laptop.