Topic: [Pushpool Web Frontend] Simplecoin v5.0 Opensource PHP/MySQL - NEW RELEASE - page 7. (Read 57227 times)

Sorry I haven't had the chance to chat, it's been a busy day.

What version of simplecoin are you using? 1,2,experimental? I'm looking at the experimental code personally.

yes - debian lenny apache2 php5.3,

I tested the cronjob.php from ivasilov's github if there is a btc comunication problem (200 OK ) and that one works with out any error but ofcourse i dnt get a result...

It sounds like a possible server issue. Are you running this on a typical linux/apache/mysql setup?

I deleted the additional parameters but that didnt solve the problem, i usualy had this error with the miningfarm from xenland, but in that case was a wrong rpc value the problem.

I cheched requiredFunctions.php if the values are correct what they indeed are. So there is probably just a small bug what doesnt allows the cronjob.php to communicate with bitcoind.

The right include path is set aswell in the cronjobs.

hmm, it should be getting 200 transactions from the server. you can take the other parameters out and just leave in the listtransactions call. The only downfall to this is if you get too many transactions it knocks it off the list.

This solved it perfectly thank you!

But i discovered an other problem when i run cronjob.php:

guess thats why the mine keeps counting on the same block!

I use pushpool 5 and bitcoin 0.3.23
The rpc values works with the requiredFunctions.php i can see on the stats page difficulty and blockcount etc.. just the cronjob.php gives me the 200 error

Ok, btc account locking is now in the experimental repo. You will need to add an enum field to webUsers: btc_lock (0,1) and the locks table (fields - varchar: name, tinyint locked) if you wish to use it.


To answer the issues:


Without the cronjobs running, there will be no stats. Do you have pushpool/bitcoind up and running?

I'm not familiar with ionCube PHP. I recommend running the cronjobs using wget through your apache interface.


This issue should be fixed in the experimental branch.


I'll look into this.

hey everyone

when i cronjob any of the cronjob php files manualy trough command line i get this error:


There is an other bug in the Admin Page, its not possible to change any value since the pin nbr dnt gets accepted, but it works fine on the account details site
We have allso a bug since the first block was found on the stats.php:

where the blocks per week box was.

on news.php:
on users.php

Since the block was found it isnt possible to see the personal stats page anymore, and the left sidebar keeps counting on the same block even when the block is allready shown as found

Hi,
my server error in /var/log/apache2/error.log
Statistics on the site are empty.
Thank's for help.


and error cron log syslog:

It's not really different for obscurity, but moreso that I used a different algorithm when I setup my initial site before open-sourcing it.

I just haven't gotten around to changing it

Great job, for simplecoin.

One thing that is important to know is that security by obscurity is a very bad thing, most of the times there are problems with the design and even when the design of the algorithm is good, there are security holes that go undetected until the cracker finds out.

Open source security algorithms are the best, for example take a look at the security of the bitcoin network, it is very solid, and in the rare event that a security was found most likely it would be in the implementation and it would be fixed within hours.

There are a lot of commercial security closed source programs that use the vigenere cipher, of course that is a secret, the vigenere cipher is very easy to implement and it provides security against the average person, but by design it is insecure, it is used a lot due to its simplicity,  in closed source it is very hard to tell it uses the vigenere chipher, until someone does some reverse engineering, and after that the security completely colapses, any good cracker will crack the algorithm no very easy but doable. There are other algorithm that are also very simple and easy to implement used in closed source programs like rot13, or substitution cipher both very insecure and worse than vigenere.

Then there the famous one time pad very secure only algorithm proven to be unbreakable but also not very practical.

The there are the good ones, but more complex idea, rsa, blowfish, etc, these can only be broken by brute force attacks, extremely difficult specially is the keys are large.

I used to be a cryptographer in the mid 90, so I am not up to date with the latest algorithms, but one thing I learned is that most close source packages are very insecure, and there are packages that break the security of those closed source programs, there was a programmer I do not remember his name that wrote software to unlock the locks, he was arrested in las vegas by the fbi after he gave a conference in defcon, he would talk a lot about insecure close source software with mathematical proofs, he sold unlock software for most closed source commerical packages.

The lesson to be learned is that for the most security it is best to rely on a good algorithm, and not by security by obscurity, therefore most secure algorithms are usually open source. In theory if a person is a brilliant genius a close source security software could be secure, but for most of us, and most real world cases, open source is the way to go for security.

In many companies managers believe on closed source, the only reason for that is ignorance, they are usually not cryptographers, and know very little about programming, when working for a company like that vigenere cipher is great makes the manager happy and you are done quickly with the job, but for a job well done it is all in the algorithm and its implementation  and it takes more work when you have security in mind.





 

Nice catch. The salting in the OS version is slightly different than my sites implementation (hooray obscurity!). Fixing in repo now.

Will try that out again and see if I can get it to give me something other than internal server error 500 which is what I usually get.....is there a way I can check my tables for something missing maybe? I imported the .sql file included in the download with no errors. Was there any additional steps I needed to take maybe in creating any extra tables possibly?

Thanks again Mike! You can expect a donation for sure! Awseome stuff!

Peace!

I should have caught that.  Thank you, that fixed it.

That typo is in "simplecoin-simplecoin-v2.0-0-g361c13d.tar.gz", that's the rev I pulled.

typo in your code (or mikes).   Change $_$authPin to $authPin

Mike,

Been a lurker on the thread, and now trying to setup Simplecoin.

I have everything working, and in fact, my tests with one of my rigs appears to be working fine.

However, I cannot load the Admin Panel.  I have the link on my login, but when clicked it's a blank page and I get this error in the Apache error.log:


Any thoughts, that line in my version of the code is:


I'm thinking it doesn't think my account has a valid $authPin?  But it does...  Am I missing something?

It seems also some of the cronjobs are failing with a exit code/status of 255?

Only 2 cronjobs I get these errors on is when payout.php is tried to be executed by cron and also cronjob.php gives me this error...the rest run without errors from cron....only those 2 php files cause this cron error with a exiting code/status of 255?

I looked at the directoryinclude and all the cronjob files are setup the same....why only those 2 error out?

Please help!

Thanks!

Nice initiative, if I didn't have to pay so many damn bills Ill probably open-source mine as well.

Tell me if you need help with anything.

Kind regards
Kris

Thanks! Got the clients to connect succesfully! Do you have an example of about how long or in how many minutes I should run each cronjob file? I know in the thread it states from 10 to 30 minutes but how about the workers.php one for example? I like the stats to update frequently but I do not want to create to much or uneeded database traffic either...

Thanks again for all your help!

Anyone else having issues accessing the admin page? I have my account flag set to 1 in the database? Cant seem to figure that one out.

Peace!

Looks like BurningToad is going to share his MaxPPS code, so hopefully we'll have MaxPPS as a payout option soon.