Topic: [ANN] [LTC] [PPS] [OTP 2FA] [Stratum only] LTCMine PPS mining pool (3.3%) - page 60. (Read 227562 times)
April 22, 2013, 05:26:08 AM
You could only allow wallet address changes when the balance is below a specific threshold (like 0.1 for example, or even zero, since the payouts are only done at the end of rounds).
April 22, 2013, 12:34:47 AM
can litecoin be mined with a mac computer by anychance i thought i read that it could is this true.
April 21, 2013, 08:33:44 PM
True, Keyloggers would get around this 
. I am paranoid when it comes to security and keyloggers are less common on linux but still exist..
If we wanted to be extra paranoid we could all use RSA Secure ID tokens for login :-)
. I am paranoid when it comes to security and keyloggers are less common on linux but still exist..If we wanted to be extra paranoid we could all use RSA Secure ID tokens for login :-)
But those can be stolen, so better to use a password, an RSA Secure ID token, and biometric ID.
April 21, 2013, 08:41:12 PM
True, Keyloggers would get around this . I am paranoid when it comes to security and keyloggers are less common on linux but still exist..
If we wanted to be extra paranoid we could all use RSA Secure ID tokens for login :-)
. I am paranoid when it comes to security and keyloggers are less common on linux but still exist..If we wanted to be extra paranoid we could all use RSA Secure ID tokens for login :-)
But those can be stolen, so better to use a password, an RSA Secure ID token, and biometric ID.
April 21, 2013, 08:08:20 PM
True, Keyloggers would get around this . I am paranoid when it comes to security and keyloggers are less common on linux but still exist..
If we wanted to be extra paranoid we could all use RSA Secure ID tokens for login :-)
. I am paranoid when it comes to security and keyloggers are less common on linux but still exist..If we wanted to be extra paranoid we could all use RSA Secure ID tokens for login :-)
April 21, 2013, 08:00:40 PM
An easy fix would be to set a 2nd password for any withdrawal transactions. If a hacker does compromise an account then its unlikely they will crack the 2nd layer password for the withdrawal. The withdrawal password must not allow the same password as the ltcmine.ru login password. I think this would stop the majority of hack attempts.
seocrow
I agree that this will prevent majority of attacks, but second password could be compromised by keyloggers without any problem. Temporary codes for withdrawal address edit operations are much more secure than "static" password for the withdrawal. seocrow
April 21, 2013, 07:56:39 PM
Sent you a PM Balthazar about my account on the pool.
BTW awesome pool. First pool I have mined at in awhile where I actually earn my projected daily LTC.
BTW awesome pool. First pool I have mined at in awhile where I actually earn my projected daily LTC.
April 21, 2013, 07:50:57 PM
An easy fix would be to set a 2nd password for any withdrawal transactions. If a hacker does compromise an account then its unlikely they will crack the 2nd layer password for the withdrawal. The withdrawal password must not allow the same password as the ltcmine.ru login password. I think this would stop the majority of hack attempts.
seocrow
seocrow
April 21, 2013, 07:39:14 PM
When are you planning on unlocking the possibility to change the payout address?
It's planned for the next week. But it will be available only for google authentication sessions. Users will be able to generate codes and use it with mobile application or desktop client like this:
http://evadeflow.com/2011/09/desktop-authenticator-for-google-2fa/
April 21, 2013, 06:32:26 PM
When are you planning on unlocking the possibility to change the payout address?
April 21, 2013, 06:16:53 PM
I have had to switch to a different pool because of this connectivity issue. I am assuming your server is in russia and have you thought of getting one in EU or USA?
No, this server located in Ukraine.Code:
c:\Program Files (x86)\NovaCoin>tracert ltcmine.ru
Tpaccиpoвкa мapшpyтa к ltcmine.ru [91.235.143.14]
c мaкcимaльным чиcлoм пpыжкoв 30:
1 <1 мc * <1 мc ALEX-DESKTOP [10.0.0.1]
2 * * * Пpeвышeн интepвaл oжидaния для зaпpoca.
3 27 ms 35 ms 40 ms ALEX-DESKTOP [10.77.131.42]
4 42 ms 27 ms 27 ms ALEX-DESKTOP [10.77.176.26]
5 34 ms 27 ms 30 ms ALEX-DESKTOP [10.77.130.130]
6 40 ms 20 ms 29 ms mow-b4-link.telia.net [80.239.128.85]
7 51 ms 66 ms 42 ms s-bb2-link.telia.net [80.239.147.157]
8 52 ms 45 ms 48 ms s-b3-link.telia.net [80.91.253.226]
9 54 ms 47 ms 86 ms retn-ic-135938-s-b3.c.telia.net [213.248.74.194]
10 77 ms 68 ms 70 ms ae17-3.RT.NTL.KIV.UA.retn.net [87.245.233.197]
11 79 ms 77 ms 71 ms v362.TenGig4-2.diamond.volia.net [87.245.247.102]
12 76 ms 70 ms 77 ms be2.206.cr-1.f17.kiev.volia.net [77.120.1.129]
13 74 ms 77 ms 72 ms v253.mars.dc.volia.com [82.144.193.11]
14 84 ms * 76 ms 54.132.123.77.colo.static.dc.volia.com [77.123.132.54]
15 94 ms 92 ms 71 ms 91.235.143.14
Tpaccиpoвкa зaвepшeнa.
c:\Program Files (x86)\NovaCoin>
Tpaccиpoвкa мapшpyтa к ltcmine.ru [91.235.143.14]
c мaкcимaльным чиcлoм пpыжкoв 30:
1 <1 мc * <1 мc ALEX-DESKTOP [10.0.0.1]
2 * * * Пpeвышeн интepвaл oжидaния для зaпpoca.
3 27 ms 35 ms 40 ms ALEX-DESKTOP [10.77.131.42]
4 42 ms 27 ms 27 ms ALEX-DESKTOP [10.77.176.26]
5 34 ms 27 ms 30 ms ALEX-DESKTOP [10.77.130.130]
6 40 ms 20 ms 29 ms mow-b4-link.telia.net [80.239.128.85]
7 51 ms 66 ms 42 ms s-bb2-link.telia.net [80.239.147.157]
8 52 ms 45 ms 48 ms s-b3-link.telia.net [80.91.253.226]
9 54 ms 47 ms 86 ms retn-ic-135938-s-b3.c.telia.net [213.248.74.194]
10 77 ms 68 ms 70 ms ae17-3.RT.NTL.KIV.UA.retn.net [87.245.233.197]
11 79 ms 77 ms 71 ms v362.TenGig4-2.diamond.volia.net [87.245.247.102]
12 76 ms 70 ms 77 ms be2.206.cr-1.f17.kiev.volia.net [77.120.1.129]
13 74 ms 77 ms 72 ms v253.mars.dc.volia.com [82.144.193.11]
14 84 ms * 76 ms 54.132.123.77.colo.static.dc.volia.com [77.123.132.54]
15 94 ms 92 ms 71 ms 91.235.143.14
Tpaccиpoвкa зaвepшeнa.
c:\Program Files (x86)\NovaCoin>
Latency affects only the steps of the connection and disconnection. Server location shouldn't matter when you are using stratum based pool, because it's a protocol, which based on persistent connections.
But if you are using json-rpc based pool, it would affect you very much.
I was using stratum+tcp in my miner settings and was receiving a lot of disconnected from stratum pool messages. I tried 3 other pools and did not have this issue.
April 21, 2013, 01:57:09 PM
30/59
April 21, 2013, 01:14:10 PM
Additional info is added to withdrawal confirmation dialog.
April 21, 2013, 11:10:17 AM
29/59
April 21, 2013, 10:48:12 AM
28/59
April 21, 2013, 09:53:36 AM
1) Confirmation added on the address edit form;
2) Now current withdrawal address displayed on the payments page.
2) Now current withdrawal address displayed on the payments page.
April 21, 2013, 08:35:26 AM
27/59
April 21, 2013, 08:16:26 AM
26/59
April 21, 2013, 07:49:39 AM
25/59
April 21, 2013, 07:13:59 AM
I have had to switch to a different pool because of this connectivity issue. I am assuming your server is in russia and have you thought of getting one in EU or USA?
No, this server located in Ukraine.Code:
c:\Program Files (x86)\NovaCoin>tracert ltcmine.ru
Tpaccиpoвкa мapшpyтa к ltcmine.ru [91.235.143.14]
c мaкcимaльным чиcлoм пpыжкoв 30:
1 <1 мc * <1 мc ALEX-DESKTOP [10.0.0.1]
2 * * * Пpeвышeн интepвaл oжидaния для зaпpoca.
3 27 ms 35 ms 40 ms ALEX-DESKTOP [10.77.131.42]
4 42 ms 27 ms 27 ms ALEX-DESKTOP [10.77.176.26]
5 34 ms 27 ms 30 ms ALEX-DESKTOP [10.77.130.130]
6 40 ms 20 ms 29 ms mow-b4-link.telia.net [80.239.128.85]
7 51 ms 66 ms 42 ms s-bb2-link.telia.net [80.239.147.157]
8 52 ms 45 ms 48 ms s-b3-link.telia.net [80.91.253.226]
9 54 ms 47 ms 86 ms retn-ic-135938-s-b3.c.telia.net [213.248.74.194]
10 77 ms 68 ms 70 ms ae17-3.RT.NTL.KIV.UA.retn.net [87.245.233.197]
11 79 ms 77 ms 71 ms v362.TenGig4-2.diamond.volia.net [87.245.247.102]
12 76 ms 70 ms 77 ms be2.206.cr-1.f17.kiev.volia.net [77.120.1.129]
13 74 ms 77 ms 72 ms v253.mars.dc.volia.com [82.144.193.11]
14 84 ms * 76 ms 54.132.123.77.colo.static.dc.volia.com [77.123.132.54]
15 94 ms 92 ms 71 ms 91.235.143.14
Tpaccиpoвкa зaвepшeнa.
c:\Program Files (x86)\NovaCoin>
Tpaccиpoвкa мapшpyтa к ltcmine.ru [91.235.143.14]
c мaкcимaльным чиcлoм пpыжкoв 30:
1 <1 мc * <1 мc ALEX-DESKTOP [10.0.0.1]
2 * * * Пpeвышeн интepвaл oжидaния для зaпpoca.
3 27 ms 35 ms 40 ms ALEX-DESKTOP [10.77.131.42]
4 42 ms 27 ms 27 ms ALEX-DESKTOP [10.77.176.26]
5 34 ms 27 ms 30 ms ALEX-DESKTOP [10.77.130.130]
6 40 ms 20 ms 29 ms mow-b4-link.telia.net [80.239.128.85]
7 51 ms 66 ms 42 ms s-bb2-link.telia.net [80.239.147.157]
8 52 ms 45 ms 48 ms s-b3-link.telia.net [80.91.253.226]
9 54 ms 47 ms 86 ms retn-ic-135938-s-b3.c.telia.net [213.248.74.194]
10 77 ms 68 ms 70 ms ae17-3.RT.NTL.KIV.UA.retn.net [87.245.233.197]
11 79 ms 77 ms 71 ms v362.TenGig4-2.diamond.volia.net [87.245.247.102]
12 76 ms 70 ms 77 ms be2.206.cr-1.f17.kiev.volia.net [77.120.1.129]
13 74 ms 77 ms 72 ms v253.mars.dc.volia.com [82.144.193.11]
14 84 ms * 76 ms 54.132.123.77.colo.static.dc.volia.com [77.123.132.54]
15 94 ms 92 ms 71 ms 91.235.143.14
Tpaccиpoвкa зaвepшeнa.
c:\Program Files (x86)\NovaCoin>
Latency affects only the steps of the connection and disconnection. Server location shouldn't matter when you are using stratum based pool, because it's a protocol, which based on persistent connections.
But if you are using json-rpc based pool, it would affect you very much.
Jump to: