|
There's some randomness in the amount of fee that will be required.
|
|
|
|
Where is this being displayed? I have had the client open in Ubuntu 10.04 for days (Satoshi version 0.5.0), and I see no alert anywhere. I always wondered how the alerts work...
The GUIs of some early versions of bitcoin-qt don't display alerts. You'll still see it in JSON-RPC getinfo, though. |
|
|
|
I assume downloading the latest version as of today will solve it?
No action is required right now. The alert is in case something bad happens on Feb 20. |
|
|
|
An alert has been sent. Nearly every Bitcoin client is now printing "See bitcoin.org/feb20 if you have trouble connecting after 20 February" somewhere. Safe mode means no blocks can be received and no transactions made? Lazy to look again at wiki.
Just JSON-RPC is disabled. |
|
|
|
|
OK, I think I was finally able to improve BBE's efficiency enough to make it work well despite the increased traffic. Most interestingly, I now have Bitcoin's block database stored entirely in memory.
|
|
|
|
As far as I know the site still hasn't paid anyone, so it looks like I was right and it was a scam. The nature of the vulnerability made me especially suspicious. All login attempts were being logged to a text file at http://bitscalper.com/p/app/log . It's possible that Bitscalper was intentionally logging passwords, and this was the only way he knew how to do it with his CMS. |
|
|
|
My bitcoind is downloading the chain. You can see the progress at /q/getblockcount. |
|
|
|
Advertisers are also very generous, they donate millions of dollars to the cable companies. Oh, I forgot to mention they got an ad in exchange. Still "free", right?
I doubt the ad even comes close to allowing them to recoup the cost of running the server. |
|
|
|
Ha! That one might be me; I still run a 0.3.15 node. This node is old enough that it might go into safe mode when it receives the alert. (Versions older than 0.3.19 can have safe mode activated by alerts.) |
|
|
|
|
It's a reasonable approximation of board rules, which is why I left it. You can mostly get by on common sense here.
The comment of yours that I posted above isn't related to the OP in the slightest. This is what counts when determining whether something is on-topic. Normally I'd just delete posts like this, but I'm 99.9% sure you're Atlas, so you should be very familiar with board rules by now.
|
|
|
|
Slightly longer answer: It does the same thing as when you throw away a hundred dollar bill. You lose money, and everyone else's money gains a little value.
Hardly, when money is created out of thin air every time a bank makes a loan. |
|
|
|
The server won't start up now, due either to a bad disk or to my tweaks meant to make the system faster. Rasengan (who, on behalf of Private Internet Access, generously provides this BBE server for free) is working on fixing it and maybe upgrading it so that it can handle more traffic. Hopefully at least /q/getblockcount will be working tomorrow. Maybe the Internet is broken.
You're the Internet?  |
|
|
|
...and does anybody know if the system will be restored ?
It will be back up eventually. It'll probably be mostly working tomorrow. |
|
|
|
|
It's really fast whenever I restart the database and web servers, but then I guess it gets overwhelmed with traffic. I'll look into it later today.
(Usually I have two "master" servers constantly available and capable of either handling the full load or sharing the load, but the one that I have at home was unfortunately damaged when I moved recently, so I have to rely entirely on the Private Internet Access server.)
|
|
|
|
|
I think everything is fixed now. Sorry about that.
IPs will now automatically be banned (temporarily) if they connect much faster than once per second.
|
|
|
|
|
Looks like it's caused by a lot of traffic. Maybe a DoS attack. I'm fixing it now.
|
|
|
|
I stopped reading right there because I was also labeled a scammer once for arguably no good reason and I am one of the most productive members of the forum now. I don't know TerryTibbs but when I see a scammer tag, I just say "What now?".
You were labeled a scammer because you scammed someone. It was removed because you paid them back. Terrytibbs scammed someone and has not paid them back. He has a scammer tag so that other traders are warned about this incident. Initially I was opposed to reacting to scammers at all, but I decided that if scammer accounts were not somehow marked, almost everyone would feel that the forum had neglected its responsibility to traders. (Most forums would ban scammers outright.) The amount of time elapsed since terrytibbs' conflict and the quality of his posts are not relevant: he still scammed someone in the past and has not paid them back. |
|
|
|
|
The paper is mostly about potentially worrying trends in RSA, which Bitcoin doesn't use.
Summary of the paper: We gathered several million TLS/PGP certificates in the wild. A surprisingly large percentage of RSA keys and maybe a few DSA keys were generated in such a way that they share certain properties with other keys which are never supposed to be shared, making encryption using the affected keys weak or totally useless. We're not sure why this happened.
|
|
|
|
Because of personal freedom concerns, management of bitscalper was forced to leave the site alone for the last ten days. We did just notice the security breach and we do apologize about any issue that this might cause. We want to clarify that we did not store any password in plain text, rather the server was compromised to add a textual password column to the database, supposedly for the hacker to get all the user's passwords.
We did store all the passwords in MD5, while we acknowledge that it is not the state of the art, it still works for decently choosen passwords. We will be posting any update/finding on here. Thanks and apologizes for delaying intervention.
The security vulnerability I used still exists. Read the email I sent to info@bitscalper.com. |
|
|
|
Worst case, some users fail to connect to peers for a couple hours, but even that's a stretch (any peers in the same time will be sync'd with you)
It's UTC, so nodes with the correct time will all make the change at the same instant. |
|
|
|
|
Show Posts
