tomb complains about zramswap

[chri2]

tomb complains about zramswap

[chri2]

Applied these changes to not stumble over the missing --force again and again.

[jaromil]

Whoeps, my bad I have never made a stable release including this improvement. On it

[roddhjav]

Have a look at #414. You can force it without issue.

[chri2]

Yes, thanks, I already had read that and it worked this way.

But...

didn't bring up anything about attack vectors through swap-usage and explanations why using swap and which type of swap poses a risk to tomb.

I'm having a bad feeling using -f force without understanding what risk I might take and what other warnings/errors might get forced on the way.

Since the whole purpose of the software is about security understanding the risks is crucial to anybody using it.

I'd love to see some reference somewhere about these questions (or being pointed to the once I missed).

[chri2]

Just stumbled over this after an os upgrade, again: pass is trying to open the tomb, but can't, because tomb doesn't like the cryptswap.

Release ;-) ?