Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #352804 > unrolled thread
| Started by | owl <owl@rooftop.invalid> |
|---|---|
| First post | 2016-04-30 03:42 +0000 |
| Last post | 2016-04-30 07:41 -0700 |
| Articles | 5 — 3 participants |
Back to article view | Back to comp.os.linux.advocacy
test failed owl <owl@rooftop.invalid> - 2016-04-30 03:42 +0000
Re: test failed Melzzzzz <mel@zzzzz.com> - 2016-04-30 05:43 +0200
Re: test failed owl <owl@rooftop.invalid> - 2016-04-30 03:51 +0000
Re: test failed owl <owl@rooftop.invalid> - 2016-04-30 03:53 +0000
Re: test failed Steve Carroll <fretwizzer@gmail.com> - 2016-04-30 07:41 -0700
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 03:42 +0000 |
| Subject | test failed |
| Message-ID | <ghjdje902.ar@rooftop.invalid> |
No match on hash. Will try one more test with appended newline, in the event that the ip was just echo'ed through md5sum with a newline: anon@lowtide:~$ echo 10.0.0.1 | md5sum 81a69697c964052ffd235c28166ba917 - anon@lowtide:~$ vs. anon@lowtide:~$ echo -n 10.0.0.1 | md5sum 190dafab69706a67221c1226360de7dc - anon@lowtide:~$ If this doesn't get a match, it may not be an ipv4 ip, despite this eternal-september Injection-Info header looking almost identical to a google-groups header where the "posting-host" substring *is* an ipv4 address. The only format difference is that the hash is surrounded by double quotes in the eternal-september string, whereas there are no quotes around the ip in the google-groups string. Anyway, I made modifications to the code to account for a possible newline being encoded. I'll run a couple more tests with the original, then start over with the new code.
[toc] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2016-04-30 05:43 +0200 |
| Message-ID | <20160430054333.1161dc8a@maxa-pc> |
| In reply to | #352804 |
On Sat, 30 Apr 2016 03:42:01 +0000 (UTC) owl <owl@rooftop.invalid> wrote: > No match on hash. > Will try one more test with appended newline, in the event that > the ip was just echo'ed through md5sum with a newline: > > anon@lowtide:~$ echo 10.0.0.1 | md5sum > 81a69697c964052ffd235c28166ba917 - > anon@lowtide:~$ > > vs. > > anon@lowtide:~$ echo -n 10.0.0.1 | md5sum > 190dafab69706a67221c1226360de7dc - > anon@lowtide:~$ > > If this doesn't get a match, it may not be an ipv4 ip, despite > this eternal-september Injection-Info header looking almost > identical to a google-groups header where the "posting-host" > substring *is* an ipv4 address. The only format difference > is that the hash is surrounded by double quotes in the > eternal-september string, whereas there are no quotes around > the ip in the google-groups string. > > Anyway, I made modifications to the code to account for a > possible newline being encoded. I'll run a couple more tests > with the original, then start over with the new code. > > Do you think they are that stupid to just hash ip address?
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 03:51 +0000 |
| Message-ID | <fhgji03.a3@rooftop.invalid> |
| In reply to | #352805 |
Melzzzzz <mel@zzzzz.com> wrote: > On Sat, 30 Apr 2016 03:42:01 +0000 (UTC) > owl <owl@rooftop.invalid> wrote: > >> No match on hash. >> Will try one more test with appended newline, in the event that >> the ip was just echo'ed through md5sum with a newline: >> >> anon@lowtide:~$ echo 10.0.0.1 | md5sum >> 81a69697c964052ffd235c28166ba917 - >> anon@lowtide:~$ >> >> vs. >> >> anon@lowtide:~$ echo -n 10.0.0.1 | md5sum >> 190dafab69706a67221c1226360de7dc - >> anon@lowtide:~$ >> >> If this doesn't get a match, it may not be an ipv4 ip, despite >> this eternal-september Injection-Info header looking almost >> identical to a google-groups header where the "posting-host" >> substring *is* an ipv4 address. The only format difference >> is that the hash is surrounded by double quotes in the >> eternal-september string, whereas there are no quotes around >> the ip in the google-groups string. >> >> Anyway, I made modifications to the code to account for a >> possible newline being encoded. I'll run a couple more tests >> with the original, then start over with the new code. >> >> > > Do you think they are that stupid to just hash ip address? Maybe. Only one way to find out.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 03:53 +0000 |
| Message-ID | <fhdjv03.75ar@rooftop.invalid> |
| In reply to | #352804 |
Snit <usenet@gallopinginsanity.com> wrote: > On 4/29/16, 8:42 PM, in article ghjdje902.ar@rooftop.invalid, "owl" > <owl@rooftop.invalid> wrote: > >> No match on hash. >> Will try one more test with appended newline, in the event that >> the ip was just echo'ed through md5sum with a newline: >> >> anon@lowtide:~$ echo 10.0.0.1 | md5sum >> 81a69697c964052ffd235c28166ba917 - >> anon@lowtide:~$ >> >> vs. >> >> anon@lowtide:~$ echo -n 10.0.0.1 | md5sum >> 190dafab69706a67221c1226360de7dc - >> anon@lowtide:~$ >> >> If this doesn't get a match, it may not be an ipv4 ip, despite >> this eternal-september Injection-Info header looking almost >> identical to a google-groups header where the "posting-host" >> substring *is* an ipv4 address. The only format difference >> is that the hash is surrounded by double quotes in the >> eternal-september string, whereas there are no quotes around >> the ip in the google-groups string. >> >> Anyway, I made modifications to the code to account for a >> possible newline being encoded. I'll run a couple more tests >> with the original, then start over with the new code. >> >> > Would be interesting to see if you can figure out my current IP address. If > you think you get it let me know... I will let you know if you are right or > wrong. > Would be interesting to see what you think your individual.net headers have to do with this project.
[toc] | [prev] | [next] | [standalone]
| From | Steve Carroll <fretwizzer@gmail.com> |
|---|---|
| Date | 2016-04-30 07:41 -0700 |
| Message-ID | <44f8d5d2-31d0-497d-a6da-7eadd8b389a7@googlegroups.com> |
| In reply to | #352809 |
On Friday, April 29, 2016 at 9:53:25 PM UTC-6, owl wrote: > Snit <usenet@gallopinginsanity.com> wrote: > > On 4/29/16, 8:42 PM, in article ghjdje902.ar@rooftop.invalid, "owl" > > <owl@rooftop.invalid> wrote: > > > >> No match on hash. > >> Will try one more test with appended newline, in the event that > >> the ip was just echo'ed through md5sum with a newline: > >> > >> anon@lowtide:~$ echo 10.0.0.1 | md5sum > >> 81a69697c964052ffd235c28166ba917 - > >> anon@lowtide:~$ > >> > >> vs. > >> > >> anon@lowtide:~$ echo -n 10.0.0.1 | md5sum > >> 190dafab69706a67221c1226360de7dc - > >> anon@lowtide:~$ > >> > >> If this doesn't get a match, it may not be an ipv4 ip, despite > >> this eternal-september Injection-Info header looking almost > >> identical to a google-groups header where the "posting-host" > >> substring *is* an ipv4 address. The only format difference > >> is that the hash is surrounded by double quotes in the > >> eternal-september string, whereas there are no quotes around > >> the ip in the google-groups string. > >> > >> Anyway, I made modifications to the code to account for a > >> possible newline being encoded. I'll run a couple more tests > >> with the original, then start over with the new code. > >> > >> > > Would be interesting to see if you can figure out my current IP address. If > > you think you get it let me know... I will let you know if you are right or > > wrong. > > > Would be interesting to see what you think your individual.net headers > have to do with this project. He wouldn't tell you the truth anyway. When he was busted using his sigmond puppet he denied his IP was what it was, despite it being used on other posts he'd written in another newsgroup under his Snit handle.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.advocacy
csiph-web