I am trying to change my minimum payout, but when I try I get "signature fails!"
I am setting it above the minimum as well.
What is the deal?
My Eligius - 2014-06-24 21:17:11 UTC - Minimum_Payout_BTC=0.01049
Signature fails!
Topic: Eligius: 0% Fee BTC, 105% PPS NMC, No registration, CPPSRB - page 148. (Read 1061417 times)
So no, SSL ciphers all the stream, not even the hostname is known for an eavesdropper, only the IP and port is known.
1/ See http://tools.ietf.org/html/rfc6066#page-6 ( Server Name Indication Extention )
2/ The DNS request is still made in the clear unless you are using DNSCrypt
What puzzles me a bit is the following: I have two clusters of miners pointing at different adresses. Both of these clusters have all 17 to 19 hours difficulties to connect. But often not at the same time, there is sometimes a difference between the two clusters, sometimes at the same time. They are on different networks, in different buildings. So something IS going on, although I don't know yet what it is.
Don't think so. AFAIK the transfer of the complete URL is already encrypted.
The other way someone could take a guess at which address was yours was if they knew what hashrate you were hashing at. If that were the case then they could merely visit http://eligius.st/~wizkid057/newstats/topcontributors.php and work out which one was yours.That's easy to defeat. Use more than one address!
M
Back pay rises as sqrt(n) / n, so for 2 addresses it rises twice as fast.
Don't think so. AFAIK the transfer of the complete URL is already encrypted.
Now that I think about it, only the host name part of the URL would be visible to an eavesdropper on a network.
https://eligius.st/~wizkid057/newstats/userstats.php/1zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
So my bad on that one :-/.
Standard SSL ciphers all the communication in a way that the url is only known after the handshake is done and the server certificate is provided, this indeed is a problem for sites as it forces to have only site per IP.
Currently most browsers support an protocol extension to provide with the url in clear text but it is on the user side so you can disable it if you wish.
So no, SSL ciphers all the stream, not even the hostname is known for an eavesdropper, only the IP and port is known.
Don't think so. AFAIK the transfer of the complete URL is already encrypted.
The other way someone could take a guess at which address was yours was if they knew what hashrate you were hashing at. If that were the case then they could merely visit http://eligius.st/~wizkid057/newstats/topcontributors.php and work out which one was yours.That's easy to defeat. Use more than one address!
M
Don't think so. AFAIK the transfer of the complete URL is already encrypted.
Now that I think about it, only the host name part of the URL would be visible to an eavesdropper on a network.
https://eligius.st/~wizkid057/newstats/userstats.php/1zzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
So my bad on that one :-/.
The other way someone could take a guess at which address was yours was if they knew what hashrate you were hashing at. If that were the case then they could merely visit http://eligius.st/~wizkid057/newstats/topcontributors.php and work out which one was yours.
SSL will not protect your mining address from casual observers. The mining address is in the URL you request which is visible to the network even when SSL/TLS is implemented.
Don't think so. AFAIK the transfer of the complete URL is already encrypted.
Pool's working fine for me. I haven't noticed anything different.
it only seems to be happening to 1th of my 3.5 th. drops to 2.5th for about 20 mins or so and then back up. but then maybe thats a miner issue? (geddit? lol)
Whatever it is, it seems to have been on going for ~4 days now.
Of course it sucks as I'm receiving a significantly reduced pay out.
If it gets any worse, it will be quicker picking up micro payments from the "Free Bitcoin sites"
Ha Ha Ha
On a more serious note, could we see a reduction in diff for the first time if all pools seem to be down on luck ?
SSL will not protect your mining address from casual observers. The mining address is in the URL you request which is visible to the network even when SSL/TLS is implemented.
I am not sure what the benefits would be for viewing your balance/profile page over SSL when the page is publicly accessible.
For protecting my mining address from passive observers.
Luke/wk I would be happy to pay for a semi-private TLS endpoint for those more conscious of their privacy needs.
Will
I am using S1 and S2 ant miners and they have fallen off line every once and a while but come back pretty quick.
Eligius is working just fine for me FWIW.
Even to the extent that I can cleanly use the stats for testing.
Even to the extent that I can cleanly use the stats for testing.
Maybe it's hardware specific?
I'm using Ants... two S2s and one S1s, going through a stratum proxy.
M
Eligius is working just fine for me FWIW.
Even to the extent that I can cleanly use the stats for testing.
Even to the extent that I can cleanly use the stats for testing.
I'm not having an issue yet but the clock is still ticking down
Eligius is working just fine for me FWIW.
Even to the extent that I can cleanly use the stats for testing.
Even to the extent that I can cleanly use the stats for testing.
About 4 days ago my reported hashrate at eligius.st dropped from the usual ~600gh to ~200gh.
I was about to check the miners then noticed my hashrate graph mirrors the pool hashrate graph.
This isn't the first time I've seen this which is why I didn't even bother to check my miners.
They're fine. Something is happening to the pool.
Whatever it is, it seems to have been on going for ~4 days now.
Of course it sucks as I'm receiving a significantly reduced pay out.
What causes this??
I was about to check the miners then noticed my hashrate graph mirrors the pool hashrate graph.
This isn't the first time I've seen this which is why I didn't even bother to check my miners.
They're fine. Something is happening to the pool.
Whatever it is, it seems to have been on going for ~4 days now.
Of course it sucks as I'm receiving a significantly reduced pay out.
What causes this??
Probably a DDOS attack since some of us are all experiencing it at the same time.
About 4 days ago my reported hashrate at eligius.st dropped from the usual ~600gh to ~200gh.
What causes this??
What causes this??
My worker just went idle again. 
M
EDIT: Just saw my proxy was showing every hash submission as rejected again.
M
EDIT: Just saw my proxy was showing every hash submission as rejected again.
Jump to: