Fermi wrote:Only solution for that is sending token or hash to email@example.com, so I can reset the sessions.
parityboy wrote:@Like blackberries
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.
Captain Blackberry wrote:A better approach would be to have a website basically like the purchasing system.
Dump your token into it, provide an email address, and a new token the correct length is sent to you.
The old one is blocked.
You're essentially buying a new token with an old blocked one, but a record can be kept for tracking abuse of the system.
Users browsing this forum: Baidu [Spider], Bing [Bot], Boorbun21 and 30 guests