You know what dude, fighting with me is ridiculous since I am someone who was trying to *HELP THE COMMUNITY GET THE MOST OUT OF THEIR MINERS*.
You don't fscking understand dynamic vs. static linking. And lcgm and the .so.2 are *NOT* linked to cgminer and cannot be because cgminer is not a fscking library you fscking idiot.
And the original ".so.2" was a SHARED LIBRARY that other things would dynamically link to, you imbecile. If it was static, you wouldn't see it on the filesystem! Using the same _filename_ does not make the new contents exist under GPL as you so ignorantly and stubbornly assume.
These miners came out, purposefully gimped from the factory. I took the time to unlock them and release it to the community.
Then folk had issues with certain boards on specific batches, so I made a modification to let them get the most out of their system.
Then folk wanted voltage controls... well, you've just ensured that all future work stops because I refuse to sit here and defend against fscking idiots like yourself over and over.
My claims are on lcgm and and the the contents of the file named libnss_mdns_minimal.so.2, not the packaging. You are distributing my work in the packing you provided.
BTW, shit from idiots like yourself is why Bliss moved on also.
.. and the reason why I would have said "a billion dollars" or whatever to you is because you have been ignorantly annoying from the beginning speaking out of your ass with your posts and questions.
Good luck.
(Yeah folk, I *CAN* be an asshole, but most of the time I'm not.. and those of you who have dealt with me privately know that.)
-j
Topic: Z9 Series Full and Mini Modded Efudd NO-DEV FEE 100% - Individual Clocking - page 4. (Read 2048 times)
February 12, 2019, 02:44:36 AM
February 12, 2019, 02:14:21 AM
You have no rights, I am telling you, if you don't follow the GPL licensing you cannot claim any violation because then you have no rights to distribute your releases. Your work is considered a derivative work
Those who do not accept the GPL's terms and conditions do not have permission, under copyright law, to copy or distribute GPL licensed software or derivative works. However, if they do not redistribute the GPL'd program, they may still use the software within their organization however they like, and works (including programs) constructed by the use of the program are not required to be covered by this license.
Linked to GPL file
libc.so.6 and ld-linux-armhf.so.3
Your lcgm and s02 files are also linked to cgminer which is GPL and open source
The distribution rights granted by the GPL for modified versions of the work are not unconditional. When someone distributes a GPL'd work plus their own modifications, the requirements for distributing the whole work cannot be any greater than the requirements that are in the GPL. You distributed GPL'd work with your modifications.
Whether you want your files proprietary or not you cannot exceed past the GPL license, the .so.2 file was static linked to cgminer therefore you have no claim your work became derivative work whether the library file was junk or not the moment you replaced it you lost any right as the file was part of the original firmware. So either you except the GPL license terms and move on or you don't accept them and pull your firmware offline claiming its all proprietary. But don't think your gonna legal bully me to remove it. I accept the GPL terms
Those who do not accept the GPL's terms and conditions do not have permission, under copyright law, to copy or distribute GPL licensed software or derivative works. However, if they do not redistribute the GPL'd program, they may still use the software within their organization however they like, and works (including programs) constructed by the use of the program are not required to be covered by this license.
Linked to GPL file
libc.so.6 and ld-linux-armhf.so.3
Your lcgm and s02 files are also linked to cgminer which is GPL and open source
The distribution rights granted by the GPL for modified versions of the work are not unconditional. When someone distributes a GPL'd work plus their own modifications, the requirements for distributing the whole work cannot be any greater than the requirements that are in the GPL. You distributed GPL'd work with your modifications.
Whether you want your files proprietary or not you cannot exceed past the GPL license, the .so.2 file was static linked to cgminer therefore you have no claim your work became derivative work whether the library file was junk or not the moment you replaced it you lost any right as the file was part of the original firmware. So either you except the GPL license terms and move on or you don't accept them and pull your firmware offline claiming its all proprietary. But don't think your gonna legal bully me to remove it. I accept the GPL terms
February 12, 2019, 01:41:48 AM
Yup a couple names had to guess on the older version. No big deal that still don't count as an intrusion.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
Dear Chip- My firmware is an in-memory modification of otherwise GPL'd software. The factory image is provided, along with my non-GPL'd modifications which are performed at run-time. That is completely with all rights of GPL'd software. It's akin to how an Nvidia driver can be loaded into a GPL'd linux kernel, without the driver itself being GPLd.
However, your action was to take my compiled code and resulting binary which in turn generates modifications at run-time on factory firmware. This maintains the proverbial "separation of church and state" with the Bitmain GPL'd code, and my work. My code is NOT GPL and is under copyright. Redistribution of it, even if not modified, is theft by any legal definition.
It is simple as that. I am sorry you do not apparently have the capability to understand that. Talk to a proper lawyer who can explain things to you.
I, on the other hand, work with the legality of GPL (and other licenses) as it relates to other software and components as a function of my actual job and have experience working with corporate IP lawyers on this type of thing, including the protection of ensuring GPL code does not impact non-GPL code.
You are well out of water here and obviously do not have the experience or knowledge to make the claims you make.
Your change is (by your own admittance) a modification of code I wrote completely from scratch followed by distribution of said change which is the exact opposite of a "unique" work in any way, shape, or form. Your own words counter your statements.
Also, this is now the 3rd or 4th "firmware" you have released on these forums for these same miners.
-j
You need to look harder because under GPL once you changed a static linked file your claims can disappear and the file becomes part of the GPL whether you wrote it over from scratch or not and since you mixed your code with GPL you are also suppose to supply the source code if requested. You are using GPL libraries and so on therefore under the laws and GPL license for the main codes are GPL
The distribution rights granted by the GPL for modified versions of the work are not unconditional. When someone distributes a GPL'd work plus their own modifications, the requirements for distributing the whole work cannot be any greater than the requirements that are in the GPL.
This requirement is known as copyleft. It earns its legal power from the use of copyright on software programs. Because a GPL work is copyrighted, a licensee has no right to redistribute it, not even in modified form (barring fair use), except under the terms of the license. One is only required to adhere to the terms of the GPL if one wishes to exercise rights normally restricted by copyright law, such as redistribution. Conversely, if one distributes copies of the work without abiding by the terms of the GPL (for instance, by keeping the source code secret), they can be sued by the original author under copyright law.
So threaten me with an order some more. Your software mods fall under the GPL license whether you like it or not.
Laugh -- there have been no threats and these paragraphs are entirely too cohesive to have been written by you.
There are 0 statically linked libraries associated with the content I named "libnss_mdns_mininal.so.2" or "lcgm".
If you are going to copy/paste something from the internet to sound smart, at least give credits. You've pasted what you have implied (by the act of not providing a source) you wrote above from https://en.wikipedia.org/wiki/GNU_General_Public_License
What you have _still_ failed to comprehend is that I am not distributing modifications that fall under GPL. Further, the fact that things are split across multiple libraries and executables is specifically to avoid GPL encumbrance.
BTW, I'm still "Enjoying".
-j
February 12, 2019, 01:26:29 AM
Yup a couple names had to guess on the older version. No big deal that still don't count as an intrusion.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
Dear Chip- My firmware is an in-memory modification of otherwise GPL'd software. The factory image is provided, along with my non-GPL'd modifications which are performed at run-time. That is completely with all rights of GPL'd software. It's akin to how an Nvidia driver can be loaded into a GPL'd linux kernel, without the driver itself being GPLd.
However, your action was to take my compiled code and resulting binary which in turn generates modifications at run-time on factory firmware. This maintains the proverbial "separation of church and state" with the Bitmain GPL'd code, and my work. My code is NOT GPL and is under copyright. Redistribution of it, even if not modified, is theft by any legal definition.
It is simple as that. I am sorry you do not apparently have the capability to understand that. Talk to a proper lawyer who can explain things to you.
I, on the other hand, work with the legality of GPL (and other licenses) as it relates to other software and components as a function of my actual job and have experience working with corporate IP lawyers on this type of thing, including the protection of ensuring GPL code does not impact non-GPL code.
You are well out of water here and obviously do not have the experience or knowledge to make the claims you make.
Your change is (by your own admittance) a modification of code I wrote completely from scratch followed by distribution of said change which is the exact opposite of a "unique" work in any way, shape, or form. Your own words counter your statements.
Also, this is now the 3rd or 4th "firmware" you have released on these forums for these same miners.
-j
You need to look harder because under GPL once you changed a static linked file your claims can disappear and the file becomes part of the GPL whether you wrote it over from scratch or not and since you mixed your code with GPL you are also suppose to supply the source code if requested. You are using GPL libraries and so on therefore under the laws and GPL license for the main codes are GPL
The distribution rights granted by the GPL for modified versions of the work are not unconditional. When someone distributes a GPL'd work plus their own modifications, the requirements for distributing the whole work cannot be any greater than the requirements that are in the GPL.
This requirement is known as copyleft. It earns its legal power from the use of copyright on software programs. Because a GPL work is copyrighted, a licensee has no right to redistribute it, not even in modified form (barring fair use), except under the terms of the license. One is only required to adhere to the terms of the GPL if one wishes to exercise rights normally restricted by copyright law, such as redistribution.
So threaten me with an order some more. Your software mods fall under the GPL license whether you like it or not.
February 12, 2019, 12:42:07 AM
Yup a couple names had to guess on the older version. No big deal that still don't count as an intrusion.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
Dear Chip- My firmware is an in-memory modification of otherwise GPL'd software. The factory image is provided, along with my non-GPL'd modifications which are performed at run-time. That is completely with all rights of GPL'd software. It's akin to how an Nvidia driver can be loaded into a GPL'd linux kernel, without the driver itself being GPLd.
However, your action was to take my compiled code and resulting binary which in turn generates modifications at run-time on factory firmware. This maintains the proverbial "separation of church and state" with the Bitmain GPL'd code, and my work. My code is NOT GPL and is under copyright. Redistribution of it, even if not modified, is theft by any legal definition.
It is simple as that. I am sorry you do not apparently have the capability to understand that. Talk to a proper lawyer who can explain things to you.
I, on the other hand, work with the legality of GPL (and other licenses) as it relates to other software and components as a function of my actual job and have experience working with corporate IP lawyers on this type of thing, including the protection of ensuring GPL code does not impact non-GPL code.
You are well out of water here and obviously do not have the experience or knowledge to make the claims you make.
Your change is (by your own admittance) a modification of code I wrote completely from scratch followed by distribution of said change which is the exact opposite of a "unique" work in any way, shape, or form. Your own words counter your statements.
Also, this is now the 3rd or 4th "firmware" you have released on these forums for these same miners.
-j
February 11, 2019, 09:52:40 PM
Yup a couple names had to guess on the older version. No big deal that still don't count as an intrusion.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
And my change is unique to me. Lets not preach theft you started with someone else's code too. So if you say I am a thief then so are you.
February 11, 2019, 09:21:48 PM
I hope you have proof of the scanning of your server because I have never scanned anything. Attempting to download older versions is not scanning a server it is attempting to download older versions that you apparently removed from the server and no one tried to intrude your server.
Fine, here's a selection...
Code:
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0d.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:19:00 +0000] "GET /Z9_2.0d.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:19:00 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:20:25 +0000] "GET /Z9_2.0b.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:23:18 +0000] "GET /Z9_2.0b.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:24:45 +0000] "GET /Z9_Unlocked__hashboard_control__2.0c.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:24:57 +0000] "GET /Z9_Unlocked__hashboard_control__2.0.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:25:15 +0000] "GET /Z9__2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [08/Feb/2019:02:50:54 +0000] "GET /Z9_2.1d.tar.gz HTTP/1.1" 200 12507784 "https://bitcointalk.org/index.php?topic=5036968.0" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:18:14 +0000] "GET /Z9Mini_2.1d.tar.gz HTTP/1.1" 200 12549086 "https://bitcointalk.org/index.php?topic=5036968.0" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:44:50 +0000] "GET / HTTP/1.1" 200 4928 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:34 +0000] "GET /Z9_2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:43 +0000] "GET /Z9_v2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:54 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:46:01 +0000] "GET /Z9_2.0a.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:49:34 +0000] "GET /Z9_Unlocked__hashboard_control__2.0.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:49:49 +0000] "GET /Z9_Unlocked__hashboard_control__2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:01 +0000] "GET /Z9_Unlocked__hashboard_control.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:18 +0000] "GET /Z9_Unlocked.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:34 +0000] "GET /Z9_Unlocked__hashboard_control__2.0c.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
How do I know it was you? The PM I sent you a few minutes ago where you clicked the link, specifically designed to validate that I had indeed previously identified you.
Code:
24.179.XXX.XXX - - [11/Feb/2019:23:16:16 +0000] "GET /chipless HTTP/1.1" 301 433 "https://bitcointalk.org/index.php?action=pm" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
-j
Yup and like I said no one was trying to intrude your system it clearly shows I was attempting to download older versions. Anything else. That is not scanning that is downloading previous files you released.
Ok dude. You should get your system checked out for malware or viruses then... and not all of those were released and is guessing.
Regardless, the method of doing changes in memory on ARM *IS unique* to me. Theft is theft man.
Enjoy your thread.
-j
February 11, 2019, 08:57:24 PM
I hope you have proof of the scanning of your server because I have never scanned anything. Attempting to download older versions is not scanning a server it is attempting to download older versions that you apparently removed from the server and no one tried to intrude your server.
Fine, here's a selection...
Code:
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0d.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:19:00 +0000] "GET /Z9_2.0d.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:19:00 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:20:25 +0000] "GET /Z9_2.0b.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:23:18 +0000] "GET /Z9_2.0b.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:24:45 +0000] "GET /Z9_Unlocked__hashboard_control__2.0c.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:24:57 +0000] "GET /Z9_Unlocked__hashboard_control__2.0.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:25:15 +0000] "GET /Z9__2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [08/Feb/2019:02:50:54 +0000] "GET /Z9_2.1d.tar.gz HTTP/1.1" 200 12507784 "https://bitcointalk.org/index.php?topic=5036968.0" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:18:14 +0000] "GET /Z9Mini_2.1d.tar.gz HTTP/1.1" 200 12549086 "https://bitcointalk.org/index.php?topic=5036968.0" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:44:50 +0000] "GET / HTTP/1.1" 200 4928 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:34 +0000] "GET /Z9_2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:43 +0000] "GET /Z9_v2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:54 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:46:01 +0000] "GET /Z9_2.0a.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:49:34 +0000] "GET /Z9_Unlocked__hashboard_control__2.0.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:49:49 +0000] "GET /Z9_Unlocked__hashboard_control__2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:01 +0000] "GET /Z9_Unlocked__hashboard_control.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:18 +0000] "GET /Z9_Unlocked.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:34 +0000] "GET /Z9_Unlocked__hashboard_control__2.0c.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
How do I know it was you? The PM I sent you a few minutes ago where you clicked the link, specifically designed to validate that I had indeed previously identified you.
Code:
24.179.XXX.XXX - - [11/Feb/2019:23:16:16 +0000] "GET /chipless HTTP/1.1" 301 433 "https://bitcointalk.org/index.php?action=pm" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
-j
Yup and like I said no one was trying to intrude your system it clearly shows I was attempting to download older versions. Anything else. That is not scanning that is downloading previous files you released.
February 11, 2019, 08:28:33 PM
I hope you have proof of the scanning of your server because I have never scanned anything. Attempting to download older versions is not scanning a server it is attempting to download older versions that you apparently removed from the server and no one tried to intrude your server.
Fine, here's a selection...
Code:
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0d.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:18:59 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:19:00 +0000] "GET /Z9_2.0d.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:19:00 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:20:25 +0000] "GET /Z9_2.0b.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:23:18 +0000] "GET /Z9_2.0b.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:24:45 +0000] "GET /Z9_Unlocked__hashboard_control__2.0c.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:24:57 +0000] "GET /Z9_Unlocked__hashboard_control__2.0.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [03/Feb/2019:10:25:15 +0000] "GET /Z9__2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [08/Feb/2019:02:50:54 +0000] "GET /Z9_2.1d.tar.gz HTTP/1.1" 200 12507784 "https://bitcointalk.org/index.php?topic=5036968.0" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:18:14 +0000] "GET /Z9Mini_2.1d.tar.gz HTTP/1.1" 200 12549086 "https://bitcointalk.org/index.php?topic=5036968.0" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:44:50 +0000] "GET / HTTP/1.1" 200 4928 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:34 +0000] "GET /Z9_2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:43 +0000] "GET /Z9_v2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:45:54 +0000] "GET /Z9_2.0.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:46:01 +0000] "GET /Z9_2.0a.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:49:34 +0000] "GET /Z9_Unlocked__hashboard_control__2.0.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:49:49 +0000] "GET /Z9_Unlocked__hashboard_control__2.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:01 +0000] "GET /Z9_Unlocked__hashboard_control.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:18 +0000] "GET /Z9_Unlocked.tar.gz HTTP/1.1" 404 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
24.179.XXX.XXX - - [10/Feb/2019:10:50:34 +0000] "GET /Z9_Unlocked__hashboard_control__2.0c.tar.gz HTTP/1.1" 403 348 "-" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
How do I know it was you? The PM I sent you a few minutes ago where you clicked the link, specifically designed to validate that I had indeed previously identified you.
Code:
24.179.XXX.XXX - - [11/Feb/2019:23:16:16 +0000] "GET /chipless HTTP/1.1" 301 433 "https://bitcointalk.org/index.php?action=pm" "Mozilla/5.0 (Windows NT 10.0; Trident/7.0; rv:11.0) like Gecko" "-"
-j
February 11, 2019, 08:26:02 PM
I hope you have proof of the scanning of your server because I have never scanned anything. Attempting to download older versions is not scanning a server it is attempting to download older versions that you apparently removed from the server and no one tried to intrude your server.
Glad you can lookup a ip. As I said I will swap some more and then you cant claim its yours not hard to do and perfectly legal your routines aren't hard to change and get the same results.
Glad you can lookup a ip. As I said I will swap some more and then you cant claim its yours not hard to do and perfectly legal your routines aren't hard to change and get the same results.
February 11, 2019, 08:23:47 PM
*munches on some popcorn*
Cant wait to see whats next.....
Cant wait to see whats next.....
Me too, I'm out now.
-j
February 11, 2019, 08:23:34 PM
You better look again it is in the factory Bitmain firmware. libnss_mdns_minimal.so.2 is located in the /lib
Again, do not trust a filename, chipless.
Absolutely nothing in my shipped libnss_mdns_minimal.so.2 has anything to do with bitmain's factory, unused, library and is 100% original code. If you had a lick of sense with this stuff you would be able to see that for yourself.
... and you won't be able to release a mini version using this tactic, so you might as well remove that lie from the top of the thread, too.
You are wrong.
You are also in the wrong.
Good day.
-j
To make you happy maybe I will remove some more of your junk from the file then it wont be "yours" anymore. I tried doing legit business with you and you right away claimed I was trying to rip you off, I tried setting clients up with your software and you were an ass when I asked you questions, you refused to sell me a license, and so on so tell me why I should have not came up with a version then I could use. The original firmware was tied to that file so I used it, not my fault you also used that same file. As far as the mini I already have that figured out I just need to make some more changes then test it.
The filename does not make the contents and you are ignorant if you cannot see that. As far as your statement of my claims or refusal to sell, unless you have approached under multiple names, you are simply lying there also about the attempt or the circumstance.
Again, if the _contents_ of my libnss_mdns_minimal.so.2 or lcgm are included in what you release, it is theft of my intellectual property, pure and simple. The underlying abilities for ARM processors which I developed to generate these modifications are unique and have applications well beyond these miners.
I *DO* have have copyright and legal precedent here and I am politely asking that you take this down and cease and desist distributing my work. You are welcome to release whatever you want that does not include my content. I've made it clear which my unique content ("libnss_mdns_minmal.so.2 in any firmware I have released", and "lcgm") where it is, and that you have crossed the line with it.
You told me to "enjoy", so I am.
-j
As I said things changed once you used that file plain and simple. I wont take it down and I will modify them some more to get the junk out then you cant say nothing. All by the time your order finds me, making you waste some money trying. I find it funny how you can take someone elses firmware make some changes and then call it yours but when I make a change to the same fw you cry like a baby. There are more sites then google to put it on. About you selling a license you told me a billion dollars or something like that is what it is was going to cost me.
You remind me of the first person who tried to sell my firmware on ebay as their own after buying a copy from me. They too, did not understand the GPL. Further, you don't understand the difference in on-disk and in-memory modification as it relates to the GPL. That is why you "find it funny" -- because you do not understand it.
Point blank to anyone reading, it is *impossible* for him to provide the functionality he claims without theft of my work because of how my work was implemented. The only other option would be for him to produce a ground-up modification from scratch, which I am confident this person cannot do.
chipless, the methods used to "make my firmware go" are copyrighted, unique, and will be protected and defended as there is value beyond these ASICs with my work.
As far as your comment "by the time your order finds me", the internet is not anonymous Mr. Alabama.
-j
February 11, 2019, 08:20:15 PM
*munches on some popcorn*
Cant wait to see whats next.....
Cant wait to see whats next.....
February 11, 2019, 08:15:54 PM
You better look again it is in the factory Bitmain firmware. libnss_mdns_minimal.so.2 is located in the /lib
Again, do not trust a filename, chipless.
Absolutely nothing in my shipped libnss_mdns_minimal.so.2 has anything to do with bitmain's factory, unused, library and is 100% original code. If you had a lick of sense with this stuff you would be able to see that for yourself.
... and you won't be able to release a mini version using this tactic, so you might as well remove that lie from the top of the thread, too.
You are wrong.
You are also in the wrong.
Good day.
-j
To make you happy maybe I will remove some more of your junk from the file then it wont be "yours" anymore. I tried doing legit business with you and you right away claimed I was trying to rip you off, I tried setting clients up with your software and you were an ass when I asked you questions, you refused to sell me a license, and so on so tell me why I should have not came up with a version then I could use. The original firmware was tied to that file so I used it, not my fault you also used that same file. As far as the mini I already have that figured out I just need to make some more changes then test it.
The filename does not make the contents and you are ignorant if you cannot see that. As far as your statement of my claims or refusal to sell, unless you have approached under multiple names, you are simply lying there also about the attempt or the circumstance.
Again, if the _contents_ of my libnss_mdns_minimal.so.2 or lcgm are included in what you release, it is theft of my intellectual property, pure and simple. The underlying abilities for ARM processors which I developed to generate these modifications are unique and have applications well beyond these miners.
I *DO* have have copyright and legal precedent here and I am politely asking that you take this down and cease and desist distributing my work. You are welcome to release whatever you want that does not include my content. I've made it clear which my unique content ("libnss_mdns_minmal.so.2 in any firmware I have released", and "lcgm") where it is, and that you have crossed the line with it.
You told me to "enjoy", so I am.
-j
As I said things changed once you used that file plain and simple. I wont take it down and I will modify them some more to get the junk out then you cant say nothing. All by the time your order finds me, making you waste some money trying. I find it funny how you can take someone elses firmware make some changes and then call it yours but when I make a change to the same fw you cry like a baby. There are more sites then google to put it on. About you selling a license you told me a billion dollars or something like that is what it is was going to cost me.
February 11, 2019, 07:52:42 PM
You better look again it is in the factory Bitmain firmware. libnss_mdns_minimal.so.2 is located in the /lib
Again, do not trust a filename, chipless.
Absolutely nothing in my shipped libnss_mdns_minimal.so.2 has anything to do with bitmain's factory, unused, library and is 100% original code. If you had a lick of sense with this stuff you would be able to see that for yourself.
... and you won't be able to release a mini version using this tactic, so you might as well remove that lie from the top of the thread, too.
You are wrong.
You are also in the wrong.
Good day.
-j
To make you happy maybe I will remove some more of your junk from the file then it wont be "yours" anymore. I tried doing legit business with you and you right away claimed I was trying to rip you off, I tried setting clients up with your software and you were an ass when I asked you questions, you refused to sell me a license, and so on so tell me why I should have not came up with a version then I could use. The original firmware was tied to that file so I used it, not my fault you also used that same file. As far as the mini I already have that figured out I just need to make some more changes then test it.
The filename does not make the contents and you are ignorant if you cannot see that. As far as your statement of my claims or refusal to sell, unless you have approached under multiple names, you are simply lying there also about the attempt or the circumstance.
Again, if the _contents_ of my libnss_mdns_minimal.so.2 or lcgm are included in what you release in any way, shape, or form, it is theft of my intellectual property, pure and simple. The underlying abilities for ARM processors which I developed to generate these modifications are unique and have applications well beyond these miners.
I *DO* have have copyright and legal precedent here and I am politely asking that you take this down and cease and desist distributing my work. You are welcome to release whatever you want that does not include my content. I've made it clear which is my unique content ("libnss_mdns_minmal.so.2 in any firmware I have released", and "lcgm") where it is, and that you have crossed the line with it.
One last warning, I have you scanning my systems and attempting to intrude, searching my webservers for firmware and other files on 02/03, 02/08, and 02/10.
You told me to "enjoy", so I am.
-j
February 11, 2019, 07:36:44 PM
You better look again it is in the factory Bitmain firmware. libnss_mdns_minimal.so.2 is located in the /lib
Again, do not trust a filename, chipless.
Absolutely nothing in my shipped libnss_mdns_minimal.so.2 has anything to do with bitmain's factory, unused, library and is 100% original code. If you had a lick of sense with this stuff you would be able to see that for yourself.
... and you won't be able to release a mini version using this tactic, so you might as well remove that lie from the top of the thread, too.
You are wrong.
You are also in the wrong.
Good day.
-j
To make you happy maybe I will remove some more of your junk from the file then it wont be "yours" anymore. I tried doing legit business with you and you right away claimed I was trying to rip you off, I tried setting clients up with your software and you were an ass when I asked you questions, you refused to sell me a license, and so on so tell me why I should have not came up with a version then I could use. The original firmware was tied to that file so I used it, not my fault you also used that same file. As far as the mini I already have that figured out I just need to make some more changes then test it.
February 11, 2019, 05:51:09 PM
You better look again it is in the factory Bitmain firmware. libnss_mdns_minimal.so.2 is located in the /lib
Again, do not trust a filename, chipless.
Absolutely nothing in my shipped libnss_mdns_minimal.so.2 has anything to do with bitmain's factory, unused, library and is 100% original code. If you had a lick of sense with this stuff you would be able to see that for yourself.
... and you won't be able to release a mini version using this tactic, so you might as well remove that lie from the top of the thread, too.
You are wrong.
You are also in the wrong.
Good day.
-j
February 11, 2019, 05:42:54 PM
You better look again it is in the factory Bitmain firmware. libnss_mdns_minimal.so.2 is located in the /lib
February 11, 2019, 05:26:14 PM
Never called it my own it still says its your firmware just dev free. Don't preach to me, you took Bitmain's and the writers of cgminers firmware made some changes and call it your own. I did no different, I made a few changes and released it, with the exception of not calling it my own.
As far as the host file well when it looks for your server it don't go to it and that's all that matters. I may not explain things very well but I do get positive results.
As far as the host file well when it looks for your server it don't go to it and that's all that matters. I may not explain things very well but I do get positive results.
Actually, it is significantly different. My changes are not in any of bitmain's work that otherwise is not already released (for example .html files are by default released by proxy of them being in the firmware). The things you have modified are not released, are not legally required to be released in source, and are not public domain.
As far as bitmain goes, bitmain is in violation of the GPL by not releasing the source code to their work which is required by law.
My work was done specifically to avoid GPL and that requirement.
Again, enjoy your theft for now. I now need to go look into some specific Colorado laws.
-j
The files I modified are included in the Bitmain firmware I didn't play with your lgcm file sorry. Therefore the file is in public domain and a normally released file to the public, again you used the start of someone else's work. You modified an already existing file and I modified the modified.
Are they chip? Are you sure? You might want to take another look. This is another situation where you are simply wrong. Worse, you know you are wrong and are lying because I can tell what you've accessed and what you've modified in the image you released. (You really should look at the various timestamp types stored on a file/directory, only some of which are exposed to an 'ls -al' command). You leak a lot of OPSEC data.
You are also wrong about the rights given to an end user of GPL software, including the right to modify. And I'm telling you that you have released a modification of software that does not fall into the GPL and is my original code as your own.
This is my last response regarding your theft.
-j
This file is released in the Bitmain firmware
libnss_mdns_minimal.so.2 ---- This file you modified and recompiled
hosts
Those are the only two files besides the web pages. And as I said I don't claim it as my own. It has your name all over it. So tell me what files you say I changed that weren't in the Bitmain firmware.
Again, you are wrong.
libnss_mdns_minimal.so.2 is *NOT* in bitmain firmware and is in fact original code, not under the GPL. Modifying and releasing it is theft, end of story. The legal fact that your action is theft is not a matter of debate, it is a factual thing by your actions and the letter of the law. Also, Don't always trust a filename.
The act of you releasing it in this manner, in any court of law, would be considered you "claim[ing] it as [your] own", despite what your words say. It may have my name on it, but it is not my release, and you know this, and have admitted the same.
Hell, even lcgm is in fact original code, not covered by the GPL, so you releasing it in a bundle that bypasses the intention is also theft dude.
You can release all the firmware firmware without 'lcgm' and 'libnss_mdns.so.2' you want and be legally compliant. If you do anything else which includes those two, including modifying them or releasing them in any other bundle, you are in fact releasing goods as your own that are my copyright. This is not a matter of debate either.
chipless, you aren't the first I've had to cease and desist legally. You'll be the 5th.
-j
February 11, 2019, 05:21:00 PM
Never called it my own it still says its your firmware just dev free. Don't preach to me, you took Bitmain's and the writers of cgminers firmware made some changes and call it your own. I did no different, I made a few changes and released it, with the exception of not calling it my own.
As far as the host file well when it looks for your server it don't go to it and that's all that matters. I may not explain things very well but I do get positive results.
As far as the host file well when it looks for your server it don't go to it and that's all that matters. I may not explain things very well but I do get positive results.
Actually, it is significantly different. My changes are not in any of bitmain's work that otherwise is not already released (for example .html files are by default released by proxy of them being in the firmware). The things you have modified are not released, are not legally required to be released in source, and are not public domain.
As far as bitmain goes, bitmain is in violation of the GPL by not releasing the source code to their work which is required by law.
My work was done specifically to avoid GPL and that requirement.
Again, enjoy your theft for now. I now need to go look into some specific Colorado laws.
-j
The files I modified are included in the Bitmain firmware I didn't play with your lgcm file sorry. Therefore the file is in public domain and a normally released file to the public, again you used the start of someone else's work. You modified an already existing file and I modified the modified.
Are they chip? Are you sure? You might want to take another look. This is another situation where you are simply wrong. Worse, you know you are wrong and are lying because I can tell what you've accessed and what you've modified in the image you released. (You really should look at the various timestamp types stored on a file/directory, only some of which are exposed to an 'ls -al' command). You leak a lot of OPSEC data.
You are also wrong about the rights given to an end user of GPL software, including the right to modify. And I'm telling you that you have released a modification of software that does not fall into the GPL and is my original code as your own.
This is my last response regarding your theft.
-j
This file is released in the Bitmain firmware
libnss_mdns_minimal.so.2 ---- This file you modified and recompiled
hosts
Those are the only two files besides the web pages. And as I said I don't claim it as my own. It has your name all over it. So tell me what files you say I changed that weren't in the Bitmain firmware.
The GNU General Public License (GNU GPL or GPL) is a widely used free software license, which guarantees end users the freedom to run, study, share and modify the software
You started with a GPL file that was linked to a open source program. I did look into it and you have no leg to stand for this version.
Jump to: