I think I'll end up making the speed tweaks myself after I wrap up with Kangaroo-256, without waiting for anyone.
This is why all open source projects have some sort of license attached to them such as GPLv3 , they include a no liability clause that look like this:
In other words if your program is used by a bunch of hackers you can tell claimants trying to hold you liable to take a hike (and perhaps practice some better security hygiene like not revealing the first ~30 characters of their private key
). Unless your country's law code has some special terms about liability of cracking tool devs, you (and I, and sp_, and anyone else who codes) quite literally have no liability for whatever people do with our tools.
Jean_Luc uses this kind of license for his programs also.
Making a pool would be one of my wildest dreams lol, but I think that before we all get too exited and start buying equipment we should be porting Bitcrack to different architectures, ARM64 & OpenCL and FPGAs and whatnot, right? Nobody wants to wait for the cracker to finished being written while their ROI is steadily lowered.
There was this one guy a few pages back trying to make an ARM port to raspberry Pi 4 and he reported speeds 3x faster than Intel. I am quite curious to see if ARMv8's NEON instruction set really does run Bitcrack better, so that we can stock up on RPi's and get a better rate of return (because all that chassis and memory crap doesn't have to be bought separately).
Diversifying of compute units is also important so that we don't become NVIDIA's next nerf target after ethereum miners.
Quote
hi, where can i find your vanbitcracken?
I haven't released it or put it out to the public due to same concerns others have about closed source. I never want to get blamed for a virus or any type of "hacking". I have put a few things out, but have stopped.This is why all open source projects have some sort of license attached to them such as GPLv3 , they include a no liability clause that look like this:
Quote from: https://www.gnu.org/licenses/gpl-3.0.en.html
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
17. Interpretation of Sections 15 and 16. [15 is the unrelated "no warranty" clause]
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
17. Interpretation of Sections 15 and 16. [15 is the unrelated "no warranty" clause]
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
In other words if your program is used by a bunch of hackers you can tell claimants trying to hold you liable to take a hike (and perhaps practice some better security hygiene like not revealing the first ~30 characters of their private key
). Unless your country's law code has some special terms about liability of cracking tool devs, you (and I, and sp_, and anyone else who codes) quite literally have no liability for whatever people do with our tools.Jean_Luc uses this kind of license for his programs also.
Pool ...
I do know how to compile and such basic levels, just not a coder. I am referrign to the Pool link that apparently runs the BitCrack Software (and forks thereof) in a pooled environment. PureBasic is apparently what it is written in, and unlike any other compilations that I have created to date, this is not one I am familiar with.
An open source and available Pool is something I am happy to setup for the community, including the vast array of GPU systems IF deemed necessary to work with, that we have at our disposal also.
I am happy to work WITH someone along the lines of setting up under CentOS7/8 and my appreciation would go further than just a 'Thanks'. Purely because I like dabbling with things that interest the hell outta me
#crysx
I do know how to compile and such basic levels, just not a coder. I am referrign to the Pool link that apparently runs the BitCrack Software (and forks thereof) in a pooled environment. PureBasic is apparently what it is written in, and unlike any other compilations that I have created to date, this is not one I am familiar with.
An open source and available Pool is something I am happy to setup for the community, including the vast array of GPU systems IF deemed necessary to work with, that we have at our disposal also.
I am happy to work WITH someone along the lines of setting up under CentOS7/8 and my appreciation would go further than just a 'Thanks'. Purely because I like dabbling with things that interest the hell outta me
#crysx
Making a pool would be one of my wildest dreams lol, but I think that before we all get too exited and start buying equipment we should be porting Bitcrack to different architectures, ARM64 & OpenCL and FPGAs and whatnot, right? Nobody wants to wait for the cracker to finished being written while their ROI is steadily lowered.
There was this one guy a few pages back trying to make an ARM port to raspberry Pi 4 and he reported speeds 3x faster than Intel. I am quite curious to see if ARMv8's NEON instruction set really does run Bitcrack better, so that we can stock up on RPi's and get a better rate of return (because all that chassis and memory crap doesn't have to be bought separately).
Diversifying of compute units is also important so that we don't become NVIDIA's next nerf target after ethereum miners.