procrypto
Full Member
Offline
Activity: 224
Merit: 100
Shitcoin Maximalist
|
|
April 08, 2014, 06:06:57 PM |
|
This is EXTREMELY bad advice.
Hence the disclaimer at the bottom. Incidentally, can you point out to me where hashco.ws FAQ talks about stales? (hint: it doesn't) When I've asked nearmiss in the past whether we should submit stales to hashco.ws, the answer has been no. You're obviously free to pursue a life of stale submitting happiness. I will continue to heed good pool etiquette, based on the response I got from the pool owner.
|
|
|
|
dogechode
|
|
April 08, 2014, 06:10:45 PM |
|
This seems to be a hot issue with multipools lately. Wafflepool implemented new code a few weeks back to cut back on the number of borderline shares that were being submitted right as a coin switch took place.
|
|
|
|
theclawX
Newbie
Offline
Activity: 1
Merit: 0
|
|
April 08, 2014, 07:34:31 PM |
|
Just wanted to make you guys aware that between yesterday 4/7/2014 and today 4/8/2014 i noticed that my btc payout address had been changed without my authorization. It was changed from 16rBgvegJnDWQtakxc6ChYaUu2fozuDk47 (which has been my legitimate address since i started with hashcows) to 1GxdwuYxuoJEtzoJrxv2mQQ4344YgqUAzv (bad address that i don't recognize).
I changed my address back and did a cashout of my funds. None of my bitcoins seem to have been lost. I have already changed my password with hashcows and will look to further secure things on my end. I never wrote the password down and i used a password that i have never used on any other site. I know online security is a myth and this is not an accusation of any kind, just a heads to the other members of this community to check their payout addresses. I know this might just be an isolated incident of my password being brute forced or something, but in light of the December Hack I would prefer to be safe than sorry.Maybe nearmiss and his team can take a look internally? or maybe add another step to changing btc addreses? wemineltc 4 digit pin to make changes comes to mind. user id is miner4ever.
|
|
|
|
procrypto
Full Member
Offline
Activity: 224
Merit: 100
Shitcoin Maximalist
|
|
April 08, 2014, 08:15:36 PM |
|
Just wanted to make you guys aware that between yesterday 4/7/2014 and today 4/8/2014 i noticed that my btc payout address had been changed without my authorization. It was changed from 16rBgvegJnDWQtakxc6ChYaUu2fozuDk47 (which has been my legitimate address since i started with hashcows) to 1GxdwuYxuoJEtzoJrxv2mQQ4344YgqUAzv (bad address that i don't recognize).
The team appreciate the feedback. There have been one or two other reports like this, the first within hours of the heartbleed openssl exploit becoming public knowledge. Nearmiss patched the server against the vulnerability as early as possible today. If anyone else has similar issues, please email support@hashco.ws with full info to help nearmiss investigate - but the initial hunch is that it was an opportunistic thing using heartbleed.
|
|
|
|
nearmiss (OP)
|
|
April 08, 2014, 08:54:21 PM Last edit: April 09, 2014, 01:10:02 AM by nearmiss |
|
Just wanted to make you guys aware that between yesterday 4/7/2014 and today 4/8/2014 i noticed that my btc payout address had been changed without my authorization. It was changed from 16rBgvegJnDWQtakxc6ChYaUu2fozuDk47 (which has been my legitimate address since i started with hashcows) to 1GxdwuYxuoJEtzoJrxv2mQQ4344YgqUAzv (bad address that i don't recognize).
The team appreciate the feedback. There have been one or two other reports like this, the first within hours of the heartbleed openssl exploit becoming public knowledge. Nearmiss patched the server against the vulnerability as early as possible today. If anyone else has similar issues, please email support@hashco.ws with full info to help nearmiss investigate - but the initial hunch is that it was an opportunistic thing using heartbleed. As has been mentioned, we patched the servers asap earlier this morning. We are in the midst of a full audit for possible changes like this, as mentioned, feel free to report if you notice anything out of the ordinary. We'll likely be forcing site-wide password resets as a precautionary measure once the audit is complete. We'll have a full news update on this later tonight. This was not a hashcows-specific vulnerability, and is related to heartbleed mentioned above.
|
Profit-Switching Pool w/ Vardiff -> http://hashco.ws Optionally keep the alts we mine or auto-trade for BTC. In addition can be paid out in any of: 365, AC, BC, BTC, C2, CINNI, COMM, FAC, HBN, MINT, PMC, QRK, RDD, WC, XBC
|
|
|
adaseb
Legendary
Offline
Activity: 3878
Merit: 1732
Up to 300% + 200 FS deposit bonuses
|
|
April 08, 2014, 10:49:32 PM |
|
Well why is it that after mining for a day and a half. I am averaging about 0.0005MHASH/BTC/DAY about 1/10th of what other multipools are paying out.
Either that or my stats are frozen.
The owner is most likely skimming profits from everybody
|
|
|
|
coyote
Newbie
Offline
Activity: 58
Merit: 0
|
|
April 09, 2014, 09:45:37 AM |
|
Well why is it that after mining for a day and a half. I am averaging about 0.0005MHASH/BTC/DAY about 1/10th of what other multipools are paying out.
Either that or my stats are frozen.
The owner is most likely skimming profits from everybody
Why can't people take time to investigate issues and ask questions before going off the handle and throwing accusations about? Firstly even a little time spent reading would tell you that the nature of this pool means that payments take time to ramp up. Also what evidence do you have to support a statement like "The owner is most likely skimming profits from everybody"? I have been with this pool for most of it's life and have had absolutely NO reason to doubt nearmiss' integrity.
|
|
|
|
Catswold
|
|
April 09, 2014, 02:57:16 PM |
|
Well why is it that after mining for a day and a half. I am averaging about 0.0005MHASH/BTC/DAY about 1/10th of what other multipools are paying out.
Either that or my stats are frozen.
The owner is most likely skimming profits from everybody
Why can't people take time to investigate issues and ask questions before going off the handle and throwing accusations about? Firstly even a little time spent reading would tell you that the nature of this pool means that payments take time to ramp up. Also what evidence do you have to support a statement like "The owner is most likely skimming profits from everybody"? I have been with this pool for most of it's life and have had absolutely NO reason to doubt nearmiss' integrity. LOL!!! Give it up, coyote. You're expecting a bunch of spoiled, immature, socially inept, emotionally driven computer geeks raised with a sense of entitlment to demonstrate manners, self-control, responsibility, and calm reasoning. Maybe in about 20 years.
|
|
|
|
kuroman
|
|
April 09, 2014, 04:26:35 PM |
|
anyone else getting : ssl_error_bad_cert_domain ?
|
|
|
|
coyote
Newbie
Offline
Activity: 58
Merit: 0
|
|
April 09, 2014, 04:43:45 PM |
|
anyone else getting : ssl_error_bad_cert_domain ?
nearmiss has recently done a number of updates, including the SSL certificate, following the heartbleed vulnerability development. Unfortunately he only registered the certificate to hashco.ws and not www.hashco.ws. If you use that address all should be well - also note the password reset shortcut that is emailed to you will also need the www. removing.
|
|
|
|
nearmiss (OP)
|
|
April 09, 2014, 05:13:19 PM |
|
A few updates: 1) SSL Cert has been updated due to heartbleed. I notice now the old one was for both www and blank, new one is not. I can't simply re-issue the old as startssl is being owned atm (not unsurprisingly). https://hashco.ws works as expected, email links are updated to reflect this. If I can't get into startssl soon I'll just order another cert for www as well. 2) Site-wide password resets are required. This is a precautionary measure due to heartbleed. 3) Anyone who made an address change between April 7th 0:00:00 UTC and the time we patched the servers, have had their btc addy's changed to a garbage string. Simply log in and change to a valid address and your good to go 4) The delayed payout from Monday (due to my back issues), and then last night due to heartbleed, will be paid out tonight.
|
Profit-Switching Pool w/ Vardiff -> http://hashco.ws Optionally keep the alts we mine or auto-trade for BTC. In addition can be paid out in any of: 365, AC, BC, BTC, C2, CINNI, COMM, FAC, HBN, MINT, PMC, QRK, RDD, WC, XBC
|
|
|
kuroman
|
|
April 09, 2014, 05:36:38 PM |
|
ok thanks for the informations
|
|
|
|
procrypto
Full Member
Offline
Activity: 224
Merit: 100
Shitcoin Maximalist
|
|
April 09, 2014, 07:17:34 PM |
|
Go back through that dude's post history too. At least 75% of his posts are shrieking about one thing or another. Well why is it that after mining for a day and a half. I am averaging about 0.0005MHASH/BTC/DAY about 1/10th of what other multipools are paying out.
Either that or my stats are frozen.
The owner is most likely skimming profits from everybody
Why can't people take time to investigate issues and ask questions before going off the handle and throwing accusations about? Firstly even a little time spent reading would tell you that the nature of this pool means that payments take time to ramp up. Also what evidence do you have to support a statement like "The owner is most likely skimming profits from everybody"? I have been with this pool for most of it's life and have had absolutely NO reason to doubt nearmiss' integrity. LOL!!! Give it up, coyote. You're expecting a bunch of spoiled, immature, socially inept, emotionally driven computer geeks raised with a sense of entitlment to demonstrate manners, self-control, responsibility, and calm reasoning. Maybe in about 20 years.
|
|
|
|
MoDu
Member
Offline
Activity: 93
Merit: 10
|
|
April 09, 2014, 09:39:17 PM |
|
Are the current fast rounds normal? Longest is about 10 minutes, most are 1 - 2 minutes.
|
|
|
|
amix
Member
Offline
Activity: 84
Merit: 10
|
|
April 10, 2014, 02:53:17 PM |
|
im having a problem accessing hashcows - https://hashco.ws/Secure Connection Failed An error occurred during a connection to hashco.ws. The OCSP server has no status for the certificate. (Error code: sec_error_ocsp_unknown_cert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. tried both www and without the www. same message on both.
|
|
|
|
wheatrich
Member
Offline
Activity: 89
Merit: 10
|
|
April 10, 2014, 06:47:26 PM |
|
im having a problem accessing hashcows - https://hashco.ws/Secure Connection Failed An error occurred during a connection to hashco.ws. The OCSP server has no status for the certificate. (Error code: sec_error_ocsp_unknown_cert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. tried both www and without the www. same message on both. same, came in here to post this
|
|
|
|
ppetrovic68
|
|
April 10, 2014, 07:51:26 PM |
|
im having a problem accessing hashcows - https://hashco.ws/Secure Connection Failed An error occurred during a connection to hashco.ws. The OCSP server has no status for the certificate. (Error code: sec_error_ocsp_unknown_cert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. tried both www and without the www. same message on both. same, came in here to post this Same here. Both with and without www
|
|
|
|
twistedtrick
|
|
April 10, 2014, 07:52:18 PM |
|
Confirming connection issues as the guys above.
|
|
|
|
meelvanchris
|
|
April 10, 2014, 08:04:22 PM |
|
im having a problem accessing hashcows - https://hashco.ws/Secure Connection Failed An error occurred during a connection to hashco.ws. The OCSP server has no status for the certificate. (Error code: sec_error_ocsp_unknown_cert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site. tried both www and without the www. same message on both. same, came in here to post this Same here. Both with and without www Same here... but getting the error on mozilla. Chome loads the page just fine... Havnt tried ie yet but im sure some1 else will
|
|
|
|
ibfr33k
Member
Offline
Activity: 75
Merit: 10
|
|
April 10, 2014, 11:15:23 PM |
|
If your using Firefox you might have to uncheck a box in your "Options". Go to "Options", "Advanced", "Certificates", and then click "Validations" and uncheck both boxes. hashco.ws should load up just fine after that.
|
I'm a noob just starting, all donations are welcome. 13DXKRXQncUnWAFtemSwNH7boRZfEfsg5a
|
|
|
|