Topic: KanoPool kano.is lowest 0.9% fee 🐈 since 2014 - Worldwide - 2432 blocks - page 2034. (Read 5352086 times)

I use the google 2fa for lots of websites I am a big fan although maybe I should not be ?

I don't understand how compatibility with a sha256 algorithm is relevant to 2fa

CKDB restarted - bug in my new code - fixed now.
Of course ckdb restarting doesn't affect your active mining at all.
Web (and ckdb) is all back up and running again.

I added a comment on the 2fa page also regarding one other thing:

How it works is it uses the integer value of (current time / 30)
So a number is valid for 30 seconds (but I've only allowed single use per value as the RFC suggests)

However the 30 second time is from HH:MM:00 to HH:MM:30 or HH:MM:30 to HH:MM+1:00
- not 30 seconds from when you click on the App
Of course it depends on the clock on the pool server, but that is accurate within 1 second thanks to ntpd.

In both the Android app and the Apple app it has a 'dial' that shows the 30 second range running out.
If you are close to the end of the range, the time you have to type it in and click on the submit button is of course less.
You can wait for the 30 seconds to time out and type the new code it will come up with.
CKDB checks your answer against the pool time (when you submit the information), not the time the web page was generated.

And anyone wondering about it - there's an RFC describing TOTP:
 https://tools.ietf.org/html/rfc6238
which is based on the RFC for HOTP:
 https://tools.ietf.org/html/rfc4226

After trying the 2FA out and thought I had it messed up trying to change the payout address and getting invalid code message (was using the password and the 2FA code).

So disabled 2FA, then re-enabled it and tried again to change payout, but this time I just used the code without the password and got the payout address changed message and email about the change (but still showing the old address on the pool).

Set up on android tablet was just downloading FreeOTP Authenticator, then just hit the qrcode symbol on the top off the app and scanning the qrcode (it adds all the info, then just hit the kano icon and get the 6 digit code (as easy as can be).

BEFORE TESTING WRITE YOUR SECRET KEY DOWN FIRST, after you test the key is not displayed any-more (and haven't checked the app out enough to see if there is a way to get out of it or not).

Will check it out some more tomorrow, but so far it works, off to bed for now.

All changes are live for ckdb now also.

Again as I mentioned above:
https://bitcointalksearch.org/topic/m.12090186
If you want to try using the new 2FA, PM me your username and I'll allow it on your account.
The advantage of this is of course testing it for the pool but also if you have problems, I don't mind resetting your 2FA during the test phase - which, for security reasons, I wouldn't normally do once it's live for everyone.

Good rhythm to the pool right now. Keep up the good work all

ckpool restart done now so miners should be unaffected by anything else I do (and shouldn't have failed over)

ckdb next as I work on it over the next hour.

Edit: oh well. Had to do a 2nd ckpool restart. OK this time should be all done there.
Only ckdb after this.

was the pool restarted

2 blocks overnight, one 'just' under 100% Diff and the other well under - 99.071% Diff and 16.748% Diff

I will be doing a bunch of updates over the next hour or two.
The pool itself should just be one restart and should be few if any miner failovers as per a normal restart.
I will also change the payout addresses
The web site will add a 3rd link next to the other 2 on the Payments page showing the new address.

The back end ckdb will include the changes for 2FA, and code for being able to relabel the 368348 "Orphan" to "Unworthy" (since it wasn't an Orphan)
2FA won't be available for everyone yet, I'll run a short test period where people can try it and give any feedback.
After the end of the trial (and after resolving any issues that may arise) I'll clear all 2FA anyone has enabled and then everyone will be able to add 2FA to their normal login account (again) if they wish.
- this will also allow me to implement any changes, if necessary, that might affect the keys.

2FA has details on the 2FA setup page about how it works.

The apps I've tested:
There are issues with "Google Authenticator" since it seems to fail to support SHA256 properly.
So don't use it.

The 2FA setup is 2 steps on the web site:
1) Create a Secret Key and show a qrcode, links and details for setting up your App
2) Test your App and then enable 2FA if it succeeds
For security reasons, there is no "recover your 2FA key" on the web site, so you need to pay attention to the warnings there.

Read the page contents if you setup 2FA

Send me a PM in the next 24 hours with your pool account name (not your payout address) if you want to try it out.
Make sure you keep up to date on this thread and respond to messages here, if you want to be part of the trial.
Again, once the trial has completed, I'll clear eveyone's 2FA and you can then enable it again with a new Key.
I'll post that here in the thread, so you'll need to take note of that when I post it.

Payout 368838 sent
13f51fb66241a0a444cf31201e6c2243dfa022957e1b648ecb98f696a2793738
and confirmed

Yeah only account mining has the full details on the web site.
Address mining is limited to the stats similar to solo ckpool.

Another block not long ago

Thanks. Well, actually, it was 4 in the morning, frikking hot, and when I registered and set up the miner, I put the wallet address in as a name instead of the account name #clappingonmyhead...

So I see now the miner, but not the details (until I'm back in the office and change it...)

However, if you need to know NOW what the worker is doing
On the Workers page:
It will show more information on the worker as soon as it submits a single share.
The Share Rate is the hash rate estimate based on submitted shares since the miner connected - and is current to the second as at when you load the page.
It resets if the worker goes idle.
It's not really a very accurate estimate of your miner hash rate since it will have VERY high variance when you first connect, but it gives you some information that is current to the second.

Shy question: How long does it usually take until a worker shows on the pools stats?

Never mind... my bad :-p

Yeah I guess that maybe hotmail will start working again at some point, but I've no idea.
They give no reason for blocking my mail server and there was no large amount of email going through them
(only a few messages a day)
It's only hotmail, and it's not the first time it's happened, so yeah best to avoid them like the plague they are.

Payout 368563 sent (~7hrs ago)
3767074e66789af819276ce1c3d6f93ace170c748d012324457cf83b3fabdf47
and confirmed (~3hrs ago)

Edit: Nevermind for me, i found out how unsecure PW saved in chrome are and retrieved it there, i will change my email to gmail.
@Kano

So there was an issue with password recovery with Hotmail. Thus you now reject Hotmail as new registering email. But my e-mail is already set to an @hotmail.com. Right now i'm asking for a recovery password and i am not receiving the recovery e-mail. (After a few minutes)

So what would the procedure be for password recovery for people who previously registered with Hotmail?

More than usual, then they make cartman into a ginger so he has to join 'their' side. He rallies the gingers to kill everyone non-ginger, then they switch him back. ROFL. Funny as heck.

"The" episode?  Cartman rags on Kyle all the time for being ginger.

But more importantly, BLOCK + confirms!

LOL.. Did you guys see the Southpark Episode where they totally rip on Gingers ? Cracked me up. 

I decided on Unworthy for now ... change not quite finished will prolly get it live tomorrow with the 2FA changes also.

--

Last two payouts have been sent.
The previous was 3.5hrs ago and the last one about 15mins ago

Neither have confirmed coz there's lots of paying spam on the network at the moment.
They are both in our block work so the next block we find will confirm them both if no one else does before that.

Payout 368390 sent
39b7553a549a22497f3923bf315444840aebb0ab66dfb9701a4bdfab36d84543

Payout 368415 sent
d914c4362af1a183412b4cce04a57973eeb20190b7e49617e80c93bfebc3191e