As far as I know are the passwords used on Cryptsy hashed, yet I hear numerous stories about people losing coins on Cryptsy. On the other hand I have never heard a single story of people having lost coins on mcxNOW.
|
|
|
No round three hasn't started yet, because the bot is getting more complex and this will take time. But because I am trading my own funds manually anyway, I am also trading the fund manually and am using this thread to keep you updated. So you could say this is round 2'
|
|
|
Current value of a share is: 0.06253083BTC +0.67% since last Monday
Total since end of 2nd round +4.78%
|
|
|
This is the liquidation value in BTC. But at the moment the fund is completely invested in BTC.
|
|
|
New version 1.4.
Solved an issue that not all transactions were logged.
|
|
|
Currently the shares are worth 0.062116213BTC +1.05% since Friday
Total since end of 2nd round +4.08%
|
|
|
[snip..]Salting and hashing is absolutely no added security.
.. I'd just like to point out, that if the server is compromised and the attacker can download the full database of passwords... then they have 11k accounts and passwords, some of which will no doubt be used on other sites aswell. If the passwords are stored encrypted, then the attacked cannot download all 11k passwords at once and must put in some code to get the password - pre encryption - per login. Thus, if time between attack and attack detection is 24 hours, the attacker will only have gathered the passwords of users who have logged in the last 24 hours - not all 11k. Thus, quite obviously, storing passwords encrypted IS infact added security. Not doing this IS a flaw. According to RS the passwords ARE ENCRYPTED, but it is a two encryption not a one way like hashing is.
|
|
|
I just released version 1.3 which solves the issue with the database lock.
|
|
|
It seems that I found the cause of the database lock crash and it will be fixed in the next update tonight.
BTW: Is anyone using or interested that I continue this project? It costs a lot of time and I don't get much feedback, so I might as well stop updating. Let me know what you guys think.
|
|
|
Yes I am trading frequently, not every day but almost. Not during the weekends though.
20% of the shares have left after round 2.
Will try to give you guys some more frequent updates.
|
|
|
I haven't been trading XPM so the rise in XPM has been missed completely, unfortunately.
Current value of a share is 0.061198151BTC +2.55% Last reported price was 0.0596785BTC
BTW: This is in manual trade mode
Almost 15 XPM per share then. Are you planning to start trading XPM again? When I see an opportunity yes, but I still think it is a coin that is mainly dumped.
|
|
|
I haven't been trading XPM so the rise in XPM has been missed completely, unfortunately.
Current value of a share is 0.06119815BTC +2.55% Last reported price was 0.0596785BTC
BTW: This is in manual trade mode
|
|
|
Released version 1.2
Now it should be possible for everyone to login using the FireFox cookies.
|
|
|
Work around added for crash because of database lock.
Delete file %appdata%\CryptoDB\mcxTransactionDB
|
|
|
I see Just checked another FF installation and there it is as you describe. But this means we need a more sophisticated solution that can tackle both. But let's continue talk implementation in git, where it belongs, instead of cluttering the thread here
|
|
|
I've pushed a change so it works getting cookies from Firefox in a Windows 7, I haven't tried with Windows 8, XP or any Server variant. Feel free to discard it if this breaks compativility with any other Windows version, just keep in mind that on Windows 7 default Firefox directory scheme it doesn't work.
It already works with cookies from FireFox
|
|
|
V1.1 ----- An update has become available that makes the use of MySQL optional.
|
|
|
Any chance for you to change the project to VS2010 / .NET 4.0? Are you using classes or XAML stuff from .NET 4.5?
It should not be too hard to get it work with .net 4.0 I guess. I am not aware that I have used new features from 4.5 (although I might have ) It is WPF with XAML, but when you look at the code you see all you answers.
|
|
|
Known bugs: ------------
WebCookies.dll not in executable on sourceforge -> solved
V1.1 doesn't work with all installations of FireFox. -> Solved in version 1.2.
Program crash due to database lock -> Solved in version 1.3
|
|
|
|