Ξ welcome to cryptostorm's member forums ~ you don't have to be a cryptostorm member to post here Ξ∞ take a peek at our legendary cryptostorm_is twitter feed if you're into that kind of thing ∞Ξ we're rolling out voodoo network security across cryptostorm - big things happening, indeed! ΞΞ any OpenVPN configs found on the forum are likely outdated. For the latest, visit GitHub Ξ

Looking for assistance with a cryptostorm connection issue? Post here & we'll help out. Also: if you're not sure where to post, do so here & we'll move things around as needed. Also: for quickest support, email our oddly calm & easygoing support reps at support@cryptostorm.is

Been getting a weird error since my power browned out this afternoon and I had to restart some network equipment. Been getting:Error: Authorization failed for that tokenDoesn't matter what node I try.Tried to do some self help and also checked out:https://www.cryptostorm.nuI get the message of:That token has reached the maximum number of sessions. Thoughts/ideas? I waited a couple of hours to see if what ever ghost session timed out but no go.Oh, and I'm using the latest widget.

It's not ideal but there are options, however cumbersome they may be. Obviously this depends on how you paid for the token - if you used your real name and your own credit card then the risk only becomes apparent if you then send the same token to be reset while using a different email address; therein lies the opportunity for correlation.

CS do make an effort to not keep logs in order to avoid such correlation from happening. Having said that though, the person who purchases the token is not guaranteed to be the person who uses it. We as members can help this along by using a consistent channel of communication when dealing with token issues and keeping the emails as clean as possible - simply saying "Please reset this token" is more than enough; there's no need to refer to any thread on the forums, especially one you have started. :p

As for the mail, CS staff do use PGP so you can send them an encrypted mail from an burner address, just remember to include your public key with your email. You could also look at using Bitmessage over Tor as an option.

It's not ideal but there are options, however cumbersome they may be. Obviously this depends on how you paid for the token - if you used your real name and your own credit card then the risk only becomes apparent if you then send the same token to be reset while using a different email address; therein lies the opportunity for correlation.

CS do make an effort to not keep logs in order to avoid such correlation from happening. Having said that though, the person who purchases the token is not guaranteed to be the person who uses it. We as members can help this along by using a consistent channel of communication when dealing with token issues and keeping the emails as clean as possible - simply saying "Please reset this token" is more than enough; there's no need to refer to any thread on the forums, especially one you have started. :p

As for the mail, CS staff do use PGP so you can send them an encrypted mail from an burner address, just remember to include your public key with your email. You could also look at using Bitmessage over Tor as an option.

Ah PGP, I suppose I could use a tutanota or protonmail account with encryption too.

But purely from a consumer POV it's a pain in the bottom to have to jump through these hoops to get my token working when I've done nothing wrong.

This is where CS falls down for me. Being obfuscated offers great protection, but obfuscated support is a pita.

CS team should focus a bit of attention here so it's less painful for users to rectify CS's faults.It's a lovely learning experience and opSec practice thinking things through all the time, but sometimes you're just tired of it all and just want it to work when you're on the mobile away from home!

Protonmail has yet to respond to email complain for locked out account.

Back then all they needed to do was reset the mailbox password, and allow me to log in to initiate new mailbox creation. But no ; no help from their end.

It is hard to trust their implementation of PGP. Or their mailbox security for that matter.

And if you read their fine print they turn over encrypted mailboxes upon binding requests. Yes, although they do not have knowledge of your passwords they are still legally bound to retain or hand over encrypted mailboxes if they cannot ignore the legal request.