Maybe start out saying Legendaries must register PGP keys within a timeout that starts after their most recent login? Then move that requirement down the ranks slowly.

It seems like PGP usage is sort of encouraged, but then again there is also a field in Profile Settings for MSN and Skype handles If PGP is needed to recover accounts, why not actually make it a part of the forum? Given that Bitcoin is really a part of a wider push towards personal cryptography as a whole, I'm slightly surprised we're still at the "post your public key in this thread" stage

Creating a Bitcoin client that fully implements the network protocol is extremely difficult. Bitcoin Core and some of its derivatives are the only known safe implementations of full nodes. Some other projects attempt to compete, but it is not recommended to use such software for anything serious. (Lightweight clients like Electrum and Bither are OK.)

Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.

Requirement for a signed message with the previous key in order to register a new one

I'm not too sure that I like this idea. I ended up staking a new address because the original was controlled by coinbase. Unfortunately, coinbase disabled the ability to sign a message. I don't think the simple fact of losing a key should put a beloved account at risk of being locked out forever. I know us Bitcoiners are used to it. However, it is actually a security flaw to make access totally unrecoverable if keys are lost.

Bitcoin address are one of the main part in the working of the forum. If a person could not verify his BTC address by signing a message means he could not recover his account in case its locked or hacked. It is one of the important criteria to recover a account along with the original email so adding it as an filled on the Bitcointalk profile is a pretty good suggestion.

But this was already suggested by OgNasty to theymos, and theymos thinks PGP keys are insecure and it needs a revision.

Requirement for a signed message with the previous key in order to register a new one

I'm not too sure that I like this idea. I ended up staking a new address because the original was controlled by coinbase. Unfortunately, coinbase disabled the ability to sign a message. I don't think the simple fact of losing a key should put a beloved account at risk of being locked out forever. I know us Bitcoiners are used to it. However, it is actually a security flaw to make access totally unrecoverable if keys are lost.

What happened to you regarding coinbase can't happen with PGP keys. These keys are yours only and can't ever be managed by anybody else, even less so exclusively by someone else. PGP keys should be backed-up and safely kept. If someone loses their PGP keys it would at least be a sign they're not very well at security.

There could be a way to set a new PGP certificate if the last one's keys were lost, but it shouldn't be easy at least. It should require some deep verification.

But this is really secondary compared to first actually having PGP keys registered into the forum, that or another standard that proves to be more secure.

Requirement for a signed message with the previous key in order to register a new one

I'm not too sure that I like this idea. I ended up staking a new address because the original was controlled by coinbase. Unfortunately, coinbase disabled the ability to sign a message. I don't think the simple fact of losing a key should put a beloved account at risk of being locked out forever. I know us Bitcoiners are used to it. However, it is actually a security flaw to make access totally unrecoverable if keys are lost.

What happened to you regarding coinbase can't happen with PGP keys. These keys are yours only and can't ever be managed by anybody else, even less so exclusively by someone else. PGP keys should be backed-up and safely kept. If someone loses their PGP keys it would at least be a sign they're not very well at security.

There could be a way to set a new PGP certificate if the last one's keys were lost, but it shouldn't be easy at least. It should require some deep verification.

But this is really secondary compared to first actually having PGP keys registered into the forum, that or another standard that proves to be more secure.

Eventually losing your keys or having them compromised is the way of the universe. However, I guess for the purpose of this forum, there is no need for anyone else to gain access in the event of my death.

Using Bitcoin keys is more difficult, you need to get people to use legacy addresses, as there's no message signing standard using segwit addresses. Awkward situation.

And what's the trouble keeping a legacy address?

Also it IS possible to sign a message with a segwit address.

Difficult, not impossible

1. There's no standard to sign messages using segwit. Bitcointalk software would need to implement different ways of verifying messages for different wallet software2. People would have to figure out how to switch their wallet to generate legacy addresses, which is different in different wallet software

PGP is better for those config/standardisation reasons, but Bitcoin's cryptography is arguably more secure. Awkward situation.

PGP is better for those config/standardisation reasons, but Bitcoin's cryptography is arguably more secure. Awkward situation.

I'm sorry I still don't see how keeping your PGP over the years is easier/more convenient than storing a legacy btc addy for that purpose.

I get that some people will already have a PGP and this will come at no extra cost/complexity, but then again, I highly doubt most people on this forum are using PGP. However MOST of them do own/still have access to their old legacy addresses.

While your proposal would be a nice to have I don't see any point or reason in forcing people into it.

So the solution is already here. If you are more confident in keeping your PGP, you are already welcome to stake it. If you like BTC legacy more, stick with that.

While your proposal would be a nice to have I don't see any point or reason in forcing people into it.

So the solution is already here. If you are more confident in keeping your PGP, you are already welcome to stake it. If you like BTC legacy more, stick with that.

My thinking is that high rank accounts are actually becoming a little more valuable now that it's more difficult to rank up. You need to put in some real work to do it, people would happily hack an account to cut that out. Imagine if a great poster had their Hero account's password hacked, and they couldn't recover their account because admin wasn't convinced their email wasn't hacked too?

Maybe a better idea is only to make keys part of high rank requirements, not to lock existing high rankers out of their accounts or something like that. To rank up, you need to register a key (PGP or Bitcoin), and you drop ranks until you do for existing high ranks.

I am totally fine with using my old legacy addy as a staked address, have been doing that for years.

What I cannot believe is we don't have some form of 2FA, even if opt-in.

I'm sure if there was an open source, secure format that theymos believed in we would have it. I don't see theymos using google authenticator, which seems to be the most popular 2FA service. I have no issues with google authenticator, it's pretty easy to use and relatively secure.

PGP would be my choice. Again, it may not be very secure, but something is better than nothing.

This is a bitcoin forum, so it is guaranteed that (at least) every legendary member has a bitcoin wallet and is capable of signing a message with his private key. Security of that digital signature (ECDSA) is no less than security of PGP signatures (RSA or DSA). But the problem is most members don't have any use for PGP so you would be forcing them to use something they don't need.

1. There's no standard to sign messages using segwit. Bitcointalk software would need to implement different ways of verifying messages for different wallet software

It really isn't that hard to implement even if different wallets used different standards, the difference would be in the first byte and the rest is the same. Every signature has a "signature" that is r and s which you use to recover the possible public keys (most cases only 1 possible but can be up to 4) hash them and compare it to the given address. The first byte is just telling you which address is supposed to be correct, which you can ignore and loop through all possibilities.

PGP fingerprints are SHA-1, which is insecure. The OpenPGP standard really needs a complete new revision...

Is it really insecure in this context? To my knowledge the only problem with SHA-1 so far is collision. Considering SHA-1 is 160-bit and there is a known structural weakness, it has a time complexity of 263 which is very fast. But in this context the security depends on ability to find a second preimage (since the message aka the pubkey and the hash of it is already known), and there has been no weaknesses found to help perform this any faster so this has a time complexity of 2160 which makes it expensive enough to be secure.

My thinking is that high rank accounts are actually becoming a little more valuable now that it's more difficult to rank up. You need to put in some real work to do it, people would happily hack an account to cut that out. Imagine if a great poster had their Hero account's password hacked, and they couldn't recover their account because admin wasn't convinced their email wasn't hacked too?

Actually high ranks account are worth way less than before in the sense that they can't make you win easy money anymore now that good paying bounties are nearly extinct. I am pretty sure from what I saw account seller post that the price tag on a legendary account is way down compared to 18 months ago

Someone suggested that it should be mandatory for users to change their passwords every few months, I had nothing against the idea but the responses were mostly negative and the community didn't like that. They also didn't think it would make the account any safer since users could just start using similar password combinations or recycle old ones. The PGP keys are also one way to get an extra bit of security but again if the community was against users being forced to change their passwords I don't think forcing users to use PGP keys should be done either.