Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #352744 > unrolled thread
| Started by | owl <owl@rooftop.invalid> |
|---|---|
| First post | 2016-04-29 22:13 +0000 |
| Last post | 2016-04-30 07:33 -0700 |
| Articles | 20 on this page of 116 — 15 participants |
Back to article view | Back to comp.os.linux.advocacy
done owl <owl@rooftop.invalid> - 2016-04-29 22:13 +0000
Re: done John Gohde <john.h.gohde@gmail.com> - 2016-04-29 15:43 -0700
Re: done DFS <nospam@dfs.com> - 2016-04-29 19:26 -0400
Re: done owl <owl@rooftop.invalid> - 2016-04-30 03:50 +0000
Re: done Melzzzzz <mel@zzzzz.com> - 2016-04-30 05:51 +0200
Re: done owl <owl@rooftop.invalid> - 2016-04-30 03:55 +0000
Re: done Melzzzzz <mel@zzzzz.com> - 2016-04-30 05:57 +0200
Re: done owl <owl@rooftop.invalid> - 2016-04-30 04:04 +0000
Re: done owl <owl@rooftop.invalid> - 2016-04-30 04:07 +0000
Re: done Melzzzzz <mel@zzzzz.com> - 2016-04-30 06:08 +0200
Re: done owl <owl@rooftop.invalid> - 2016-04-30 14:35 +0000
Re: done Melzzzzz <mel@zzzzz.com> - 2016-04-30 17:20 +0200
Re: done owl <owl@rooftop.invalid> - 2016-04-30 15:40 +0000
Re: done Melzzzzz <mel@zzzzz.com> - 2016-04-30 18:11 +0200
Re: done owl <owl@rooftop.invalid> - 2016-04-30 16:17 +0000
Re: done owl <owl@rooftop.invalid> - 2016-04-30 17:23 +0000
Re: done Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-05-01 00:56 +0200
Re: done Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-05-01 01:30 +0200
Re: done owl <owl@rooftop.invalid> - 2016-04-30 23:11 +0000
Re: done Sandman <mr@sandman.net> - 2016-05-01 08:38 +0000
Re: done owl <owl@rooftop.invalid> - 2016-05-01 15:58 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 11:59 -0700
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 12:00 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 19:48 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 13:02 -0700
Re: done Melzzzzz <mel@zzzzz.com> - 2016-05-01 22:04 +0200
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 13:41 -0700
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 13:47 -0700
Re: done Melzzzzz <mel@zzzzz.com> - 2016-05-02 02:21 +0200
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:34 -0700
Re: done chrisv <chrisv@nospam.invalid> - 2016-05-02 08:27 -0500
Re: done Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-05-02 15:54 +0200
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 13:15 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 20:16 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 13:38 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 20:55 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 14:17 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 21:35 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 14:47 -0700
Re: done Marek Novotny <marek.novotny@marspolar.com> - 2016-05-01 14:56 -0700
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-01 22:37 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 15:59 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 23:10 +0000
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-01 23:09 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 17:11 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-02 00:27 +0000
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 00:31 +0000
Re: done owl <owl@rooftop.invalid> - 2016-05-02 00:52 +0000
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 01:04 +0000
Re: done owl <owl@rooftop.invalid> - 2016-05-02 01:47 +0000
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 01:51 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:44 -0700
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:41 -0700
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 19:43 -0700
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 03:36 +0000
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 21:14 -0700
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 21:43 -0700
Re: done Steve Carroll <fretwizzen@gmail.com> - 2016-05-01 22:25 -0700
Re: done Steve Carroll <fretwizzen@gmail.com> - 2016-05-01 22:27 -0700
Re: done ronb <ronb02NOSPAM@gmail.com> - 2016-05-02 17:45 +0000
Re: done Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-05-02 20:16 +0200
Re: done Peter Köhlmann <peter-koehlmann@t-online.de> - 2016-05-02 20:46 +0200
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-02 12:43 -0700
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 20:55 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:32 -0700
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:38 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-02 01:48 +0000
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 01:49 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 19:18 -0700
Re: done ronb <ronb02NOSPAM@gmail.com> - 2016-05-02 01:02 +0000
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 01:10 +0000
Re: done chrisv <chrisv@nospam.invalid> - 2016-05-02 08:31 -0500
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-02 07:27 -0700
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-02 09:10 -0700
Re: done Steve Carroll <fretwizzen@gmail.com> - 2016-05-02 10:45 -0700
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 14:51 +0000
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-02 11:18 -0700
Re: done ronb <ronb02NOSPAM@gmail.com> - 2016-05-02 19:13 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 17:12 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-02 00:27 +0000
Re: done owl <owl@rooftop.invalid> - 2016-05-02 00:53 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:42 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-02 01:50 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 19:17 -0700
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:40 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-02 01:49 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 19:16 -0700
Re: done ronb <ronb02NOSPAM@gmail.com> - 2016-05-02 01:02 +0000
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 01:08 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:33 -0700
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 18:43 -0700
Re: done William Poaster <wp@dev.null> - 2016-05-02 09:30 +0100
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 16:02 -0700
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 20:36 -0700
Re: done meat <meat.stretcher@linuxmail.org> - 2016-05-02 03:40 +0000
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-05-01 21:14 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 21:58 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 15:32 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 22:37 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 15:55 -0700
Re: done owl <owl@rooftop.invalid> - 2016-05-01 23:00 +0000
Re: done owl <owl@rooftop.invalid> - 2016-05-01 23:33 +0000
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 17:13 -0700
Re: done Snit <usenet@gallopinginsanity.com> - 2016-05-01 12:01 -0700
Re: done DFS <nospam@dfs.com> - 2016-04-29 23:58 -0400
Re: done owl <owl@rooftop.invalid> - 2016-04-30 04:08 +0000
Re: done Melzzzzz <mel@zzzzz.com> - 2016-04-30 13:12 +0200
Re: done Melzzzzz <mel@zzzzz.com> - 2016-04-30 14:09 +0200
Re: done DFS <nospam@dfs.com> - 2016-04-30 10:02 -0400
Re: done owl <owl@rooftop.invalid> - 2016-04-30 15:05 +0000
Re: done DFS <nospam@dfs.com> - 2016-04-30 11:19 -0400
Re: done owl <owl@rooftop.invalid> - 2016-04-30 15:41 +0000
Re: done DFS <nospam@dfs.com> - 2016-04-30 13:19 -0400
Re: done Chris Ahlstrom <OFeem1987@teleworm.us> - 2016-04-30 13:54 -0400
Re: done DFS <nospam@dfs.com> - 2016-04-30 19:36 -0400
Re: done Steve Carroll <fretwizzer@gmail.com> - 2016-04-30 07:33 -0700
Page 1 of 6 [1] 2 3 4 5 6 Next page →
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-29 22:13 +0000 |
| Subject | done |
| Message-ID | <ghjdie3afugr@rooftop.invalid> |
Elapsed time 3 hours +/- 2 min. Now grep'ing. :) anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ ls -ltrah out* -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$
[toc] | [next] | [standalone]
| From | John Gohde <john.h.gohde@gmail.com> |
|---|---|
| Date | 2016-04-29 15:43 -0700 |
| Message-ID | <aa4953d0-4e3a-4d28-8a1e-23ea38c68694@googlegroups.com> |
| In reply to | #352744 |
On Friday, April 29, 2016 at 6:13:24 PM UTC-4, owl wrote: > Elapsed time 3 hours +/- 2 min. > Now grep'ing. :) > anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ ls -ltrah out* > -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 > -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 > -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 Shut up, Freak!
[toc] | [prev] | [next] | [standalone]
| From | DFS <nospam@dfs.com> |
|---|---|
| Date | 2016-04-29 19:26 -0400 |
| Message-ID | <ng0qcs$eco$1@dont-email.me> |
| In reply to | #352744 |
On 4/29/2016 6:13 PM, owl wrote: > Elapsed time 3 hours +/- 2 min. > Now grep'ing. :) The beady-eyes narrow down while the stalking prey is hunted. > anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ ls -ltrah out* > -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 > -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 > -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 > -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 > -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 > -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 > -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 > -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 > anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > That's on the order of 398,000 per second. Did I do the math right? 256*256*256*256 = 4,294,967,296 hashes to generate 60 secs/minute * 60 min/hour * 3 hrs = 10,800 seconds 4,294,967,296 / 10,800 = 397,682 <quote> ./md5ip 0.0.0.0 32.255.255.255 >> out32 & ./md5ip 33.0.0.0 64.255.255.255 >> out64 & ./md5ip 65.0.0.0 96.255.255.255 >> out96 & ./md5ip 97.0.0.0 128.255.255.255 >> out128 & ./md5ip 129.0.0.0 160.255.255.255 >> out160 & ./md5ip 161.0.0.0 192.255.255.255 >> out192 & ./md5ip 193.0.0.0 224.255.255.255 >> out224 & ./md5ip 225.0.0.0 255.255.255.255 >> out255 & </quote>
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 03:50 +0000 |
| Message-ID | <f14heuf00a.a3@rooftop.invalid> |
| In reply to | #352765 |
DFS <nospam@dfs.com> wrote: > On 4/29/2016 6:13 PM, owl wrote: > >> Elapsed time 3 hours +/- 2 min. >> Now grep'ing. :) > > The beady-eyes narrow down while the stalking prey is hunted. > > > >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ ls -ltrah out* >> -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 >> -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 >> -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 >> -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 >> -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 >> -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> > > > That's on the order of 398,000 per second. > > Did I do the math right? > > 256*256*256*256 = 4,294,967,296 hashes to generate > 60 secs/minute * 60 min/hour * 3 hrs = 10,800 seconds > > 4,294,967,296 / 10,800 = 397,682 > > Sounds about right. I didn't get a match on the one string I tested. Takes anywhere from 11 to 13 minutes to grep through *one* of the 8 files. I scrounged around for speed enhancement techniques, and that's about the best I could get it to do. $ LANG=C grep -m 1 -F <hash> <file> Anyway, I may try hashing with a newline.
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2016-04-30 05:51 +0200 |
| Message-ID | <20160430055112.5ed9b1ea@maxa-pc> |
| In reply to | #352806 |
On Sat, 30 Apr 2016 03:50:02 +0000 (UTC) owl <owl@rooftop.invalid> wrote: > DFS <nospam@dfs.com> wrote: > > On 4/29/2016 6:13 PM, owl wrote: > > > >> Elapsed time 3 hours +/- 2 min. > >> Now grep'ing. :) > > > > The beady-eyes narrow down while the stalking prey is hunted. > > > > > > > >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> ls -ltrah out* -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 > >> -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 > >> -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 > >> -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 > >> -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 > >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 > >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 > >> -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 > >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> > > > > > > That's on the order of 398,000 per second. > > > > Did I do the math right? > > > > 256*256*256*256 = 4,294,967,296 hashes to generate > > 60 secs/minute * 60 min/hour * 3 hrs = 10,800 seconds > > > > 4,294,967,296 / 10,800 = 397,682 > > > > > > Sounds about right. I didn't get a match on the one string > I tested. Takes anywhere from 11 to 13 minutes to grep through > *one* of the 8 files. I scrounged around for speed enhancement > techniques, and that's about the best I could get it to do. > > $ LANG=C grep -m 1 -F <hash> <file> > > Anyway, I may try hashing with a newline. > Why don't you first try on known ip address?
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 03:55 +0000 |
| Message-ID | <ghjdo03.arg@rooftop.invalid> |
| In reply to | #352807 |
Melzzzzz <mel@zzzzz.com> wrote: > On Sat, 30 Apr 2016 03:50:02 +0000 (UTC) > owl <owl@rooftop.invalid> wrote: > >> DFS <nospam@dfs.com> wrote: >> > On 4/29/2016 6:13 PM, owl wrote: >> > >> >> Elapsed time 3 hours +/- 2 min. >> >> Now grep'ing. :) >> > >> > The beady-eyes narrow down while the stalking prey is hunted. >> > >> > >> > >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> >> ls -ltrah out* -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> >> >> > >> > >> > That's on the order of 398,000 per second. >> > >> > Did I do the math right? >> > >> > 256*256*256*256 = 4,294,967,296 hashes to generate >> > 60 secs/minute * 60 min/hour * 3 hrs = 10,800 seconds >> > >> > 4,294,967,296 / 10,800 = 397,682 >> > >> > >> >> Sounds about right. I didn't get a match on the one string >> I tested. Takes anywhere from 11 to 13 minutes to grep through >> *one* of the 8 files. I scrounged around for speed enhancement >> techniques, and that's about the best I could get it to do. >> >> $ LANG=C grep -m 1 -F <hash> <file> >> >> Anyway, I may try hashing with a newline. >> > > Why don't you first try on known ip address? You got one?
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2016-04-30 05:57 +0200 |
| Message-ID | <20160430055743.150023f9@maxa-pc> |
| In reply to | #352810 |
On Sat, 30 Apr 2016 03:55:05 +0000 (UTC) owl <owl@rooftop.invalid> wrote: > Melzzzzz <mel@zzzzz.com> wrote: > > On Sat, 30 Apr 2016 03:50:02 +0000 (UTC) > > owl <owl@rooftop.invalid> wrote: > > > >> DFS <nospam@dfs.com> wrote: > >> > On 4/29/2016 6:13 PM, owl wrote: > >> > > >> >> Elapsed time 3 hours +/- 2 min. > >> >> Now grep'ing. :) > >> > > >> > The beady-eyes narrow down while the stalking prey is hunted. > >> > > >> > > >> > > >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> >> ls -ltrah out* -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 > >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 > >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 > >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 > >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 > >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 > >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 > >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 > >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> >> > >> > > >> > > >> > That's on the order of 398,000 per second. > >> > > >> > Did I do the math right? > >> > > >> > 256*256*256*256 = 4,294,967,296 hashes to generate > >> > 60 secs/minute * 60 min/hour * 3 hrs = 10,800 seconds > >> > > >> > 4,294,967,296 / 10,800 = 397,682 > >> > > >> > > >> > >> Sounds about right. I didn't get a match on the one string > >> I tested. Takes anywhere from 11 to 13 minutes to grep through > >> *one* of the 8 files. I scrounged around for speed enhancement > >> techniques, and that's about the best I could get it to do. > >> > >> $ LANG=C grep -m 1 -F <hash> <file> > >> > >> Anyway, I may try hashing with a newline. > >> > > > > Why don't you first try on known ip address? > > You got one? > 109.72.51.248 , this is my ip address posting from eternal.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 04:04 +0000 |
| Message-ID | <fas00a3fa.44@rooftop.invalid> |
| In reply to | #352811 |
Melzzzzz <mel@zzzzz.com> wrote: > On Sat, 30 Apr 2016 03:55:05 +0000 (UTC) > owl <owl@rooftop.invalid> wrote: > >> Melzzzzz <mel@zzzzz.com> wrote: >> > On Sat, 30 Apr 2016 03:50:02 +0000 (UTC) >> > owl <owl@rooftop.invalid> wrote: >> > >> >> DFS <nospam@dfs.com> wrote: >> >> > On 4/29/2016 6:13 PM, owl wrote: >> >> > >> >> >> Elapsed time 3 hours +/- 2 min. >> >> >> Now grep'ing. :) >> >> > >> >> > The beady-eyes narrow down while the stalking prey is hunted. >> >> > >> >> > >> >> > >> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> >> >> ls -ltrah out* -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 >> >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 >> >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 >> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 >> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 >> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 >> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 >> >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 >> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> >> >> >> >> > >> >> > >> >> > That's on the order of 398,000 per second. >> >> > >> >> > Did I do the math right? >> >> > >> >> > 256*256*256*256 = 4,294,967,296 hashes to generate >> >> > 60 secs/minute * 60 min/hour * 3 hrs = 10,800 seconds >> >> > >> >> > 4,294,967,296 / 10,800 = 397,682 >> >> > >> >> > >> >> >> >> Sounds about right. I didn't get a match on the one string >> >> I tested. Takes anywhere from 11 to 13 minutes to grep through >> >> *one* of the 8 files. I scrounged around for speed enhancement >> >> techniques, and that's about the best I could get it to do. >> >> >> >> $ LANG=C grep -m 1 -F <hash> <file> >> >> >> >> Anyway, I may try hashing with a newline. >> >> >> > >> > Why don't you first try on known ip address? >> >> You got one? >> > > 109.72.51.248 , this is my ip address posting from eternal. > Cool. It matches with my first code. anon@lowtide:~$ echo 109.72.51.248 |md5sum fd81dcdbef0d516b4ec84ec977a7b6d0 - anon@lowtide:~$ echo -n 109.72.51.248 |md5sum c5fd5ec5996a00946001a1952cc5e09b - anon@lowtide:~$ cd code/md5 anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b anon@lowtide:~/code/md5$ I don't know why the other eternal hash didn't match. I'll see if grep finds yours in out128. Back in a few...
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 04:07 +0000 |
| Message-ID | <sdfhjv03.ar3@rooftop.invalid> |
| In reply to | #352813 |
owl <owl@rooftop.invalid> wrote: > Melzzzzz <mel@zzzzz.com> wrote: >> On Sat, 30 Apr 2016 03:55:05 +0000 (UTC) >> owl <owl@rooftop.invalid> wrote: >> >>> Melzzzzz <mel@zzzzz.com> wrote: >>> > On Sat, 30 Apr 2016 03:50:02 +0000 (UTC) >>> > owl <owl@rooftop.invalid> wrote: >>> > >>> >> DFS <nospam@dfs.com> wrote: >>> >> > On 4/29/2016 6:13 PM, owl wrote: >>> >> > >>> >> >> Elapsed time 3 hours +/- 2 min. >>> >> >> Now grep'ing. :) >>> >> > >>> >> > The beady-eyes narrow down while the stalking prey is hunted. >>> >> > >>> >> > >>> >> > >>> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >>> >> >> ls -ltrah out* -rw-r--r-- 1 anon anon 25G Apr 29 18:01 out32 >>> >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:02 out64 >>> >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:03 out96 >>> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:03 out128 >>> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:04 out160 >>> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out192 >>> >> >> -rw-r--r-- 1 anon anon 25G Apr 29 18:05 out224 >>> >> >> -rw-r--r-- 1 anon anon 24G Apr 29 18:06 out255 >>> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >>> >> >> >>> >> > >>> >> > >>> >> > That's on the order of 398,000 per second. >>> >> > >>> >> > Did I do the math right? >>> >> > >>> >> > 256*256*256*256 = 4,294,967,296 hashes to generate >>> >> > 60 secs/minute * 60 min/hour * 3 hrs = 10,800 seconds >>> >> > >>> >> > 4,294,967,296 / 10,800 = 397,682 >>> >> > >>> >> > >>> >> >>> >> Sounds about right. I didn't get a match on the one string >>> >> I tested. Takes anywhere from 11 to 13 minutes to grep through >>> >> *one* of the 8 files. I scrounged around for speed enhancement >>> >> techniques, and that's about the best I could get it to do. >>> >> >>> >> $ LANG=C grep -m 1 -F <hash> <file> >>> >> >>> >> Anyway, I may try hashing with a newline. >>> >> >>> > >>> > Why don't you first try on known ip address? >>> >>> You got one? >>> >> >> 109.72.51.248 , this is my ip address posting from eternal. >> > > Cool. It matches with my first code. > > anon@lowtide:~$ echo 109.72.51.248 |md5sum > fd81dcdbef0d516b4ec84ec977a7b6d0 - > anon@lowtide:~$ echo -n 109.72.51.248 |md5sum > c5fd5ec5996a00946001a1952cc5e09b - > anon@lowtide:~$ cd code/md5 > anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 > 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b > anon@lowtide:~/code/md5$ > > I don't know why the other eternal hash didn't match. > I'll see if grep finds yours in out128. Back in a few... > anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ time LANG=C grep -m 1 -F c5fd5ec5996a00946001a1952cc5e09b out128 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b real 3m24.053s user 0m10.160s sys 0m8.512s anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ Excellent. It found it. Thank, Melzzzzz.
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2016-04-30 06:08 +0200 |
| Message-ID | <20160430060847.69c21def@maxa-pc> |
| In reply to | #352814 |
On Sat, 30 Apr 2016 04:07:21 +0000 (UTC) owl <owl@rooftop.invalid> wrote: > > Excellent. It found it. > Thank, Melzzzzz. > > Great!
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 14:35 +0000 |
| Message-ID | <ghjdie993.ga@rooftop.invalid> |
| In reply to | #352814 |
Sandman <mr@sandman.net> wrote: > In article <sdfhjv03.ar3@rooftop.invalid>, owl wrote: > >> > > Melzzzzz: >> > > 109.72.51.248 , this is my ip address posting from eternal. >> > >> > owl: >> > Cool. It matches with my first code. >> >> > anon@lowtide:~$ echo 109.72.51.248 |md5sum >> > fd81dcdbef0d516b4ec84ec977a7b6d0 - >> > anon@lowtide:~$ echo -n 109.72.51.248 |md5sum >> > c5fd5ec5996a00946001a1952cc5e09b - >> > anon@lowtide:~$ cd code/md5 >> > anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 >> > 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b >> > anon@lowtide:~/code/md5$ >> >> > I don't know why the other eternal hash didn't match. >> > I'll see if grep finds yours in out128. Back in a few... >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> time LANG=C grep -m 1 -F c5fd5ec5996a00946001a1952cc5e09b out128 >> 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b > >> real 3m24.053s user 0m10.160s sys 0m8.512s >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> Excellent. It found it. >> Thank, Melzzzzz. > > I got you beat: > > Applications/Shell> time ./ipdecode.sh c5fd5ec5996a00946001a1952cc5e09b > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 > > real 0m51.322s > user 13m11.226s > sys 0m2.687s > That's impressive. Can you do these? 73bc0032541f55c8e8b7366f126961f0 1ab71f9efbdd66785a8ee9e31cf301e5 One of them I know is an ipv4 address. The other I don't know.
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2016-04-30 17:20 +0200 |
| Message-ID | <20160430172045.126c1a77@maxa-pc> |
| In reply to | #352861 |
On Sat, 30 Apr 2016 14:35:08 +0000 (UTC) owl <owl@rooftop.invalid> wrote: > Sandman <mr@sandman.net> wrote: > > In article <sdfhjv03.ar3@rooftop.invalid>, owl wrote: > > > >> > > Melzzzzz: > >> > > 109.72.51.248 , this is my ip address posting from eternal. > >> > > >> > owl: > >> > Cool. It matches with my first code. > >> > >> > anon@lowtide:~$ echo 109.72.51.248 |md5sum > >> > fd81dcdbef0d516b4ec84ec977a7b6d0 - > >> > anon@lowtide:~$ echo -n 109.72.51.248 |md5sum > >> > c5fd5ec5996a00946001a1952cc5e09b - > >> > anon@lowtide:~$ cd code/md5 > >> > anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 > >> > 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b > >> > anon@lowtide:~/code/md5$ > >> > >> > I don't know why the other eternal hash didn't match. > >> > I'll see if grep finds yours in out128. Back in a few... > >> > >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> time LANG=C grep -m 1 -F c5fd5ec5996a00946001a1952cc5e09b out128 > >> 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b > > > >> real 3m24.053s user 0m10.160s sys 0m8.512s > >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > > > >> Excellent. It found it. > >> Thank, Melzzzzz. > > > > I got you beat: > > > > Applications/Shell> time ./ipdecode.sh > > c5fd5ec5996a00946001a1952cc5e09b > > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 > > real 0m51.322s > > user 13m11.226s > > sys 0m2.687s > > > > That's impressive. Can you do these? > > 73bc0032541f55c8e8b7366f126961f0 10.0.128.33 > 1ab71f9efbdd66785a8ee9e31cf301e5 This one isn't ip address.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 15:40 +0000 |
| Message-ID | <fhjgd903.a300@rooftop.invalid> |
| In reply to | #352875 |
Melzzzzz <mel@zzzzz.com> wrote: > On Sat, 30 Apr 2016 14:35:08 +0000 (UTC) > owl <owl@rooftop.invalid> wrote: > >> Sandman <mr@sandman.net> wrote: >> > In article <sdfhjv03.ar3@rooftop.invalid>, owl wrote: >> > >> >> > > Melzzzzz: >> >> > > 109.72.51.248 , this is my ip address posting from eternal. >> >> > >> >> > owl: >> >> > Cool. It matches with my first code. >> >> >> >> > anon@lowtide:~$ echo 109.72.51.248 |md5sum >> >> > fd81dcdbef0d516b4ec84ec977a7b6d0 - >> >> > anon@lowtide:~$ echo -n 109.72.51.248 |md5sum >> >> > c5fd5ec5996a00946001a1952cc5e09b - >> >> > anon@lowtide:~$ cd code/md5 >> >> > anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 >> >> > 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b >> >> > anon@lowtide:~/code/md5$ >> >> >> >> > I don't know why the other eternal hash didn't match. >> >> > I'll see if grep finds yours in out128. Back in a few... >> >> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> >> time LANG=C grep -m 1 -F c5fd5ec5996a00946001a1952cc5e09b out128 >> >> 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b >> > >> >> real 3m24.053s user 0m10.160s sys 0m8.512s >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> > >> >> Excellent. It found it. >> >> Thank, Melzzzzz. >> > >> > I got you beat: >> > >> > Applications/Shell> time ./ipdecode.sh >> > c5fd5ec5996a00946001a1952cc5e09b >> > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 >> > real 0m51.322s >> > user 13m11.226s >> > sys 0m2.687s >> > >> >> That's impressive. Can you do these? >> >> 73bc0032541f55c8e8b7366f126961f0 > 10.0.128.33 Did you use the collision algorithm you spoke of earlier? >> 1ab71f9efbdd66785a8ee9e31cf301e5 > This one isn't ip address. > Good to know. No wonder I couldn't find it in the list.
[toc] | [prev] | [next] | [standalone]
| From | Melzzzzz <mel@zzzzz.com> |
|---|---|
| Date | 2016-04-30 18:11 +0200 |
| Message-ID | <20160430181126.66d40921@maxa-pc> |
| In reply to | #352884 |
On Sat, 30 Apr 2016 15:40:00 +0000 (UTC) owl <owl@rooftop.invalid> wrote: > Melzzzzz <mel@zzzzz.com> wrote: > > On Sat, 30 Apr 2016 14:35:08 +0000 (UTC) > > owl <owl@rooftop.invalid> wrote: > > > >> Sandman <mr@sandman.net> wrote: > >> > In article <sdfhjv03.ar3@rooftop.invalid>, owl wrote: > >> > > >> >> > > Melzzzzz: > >> >> > > 109.72.51.248 , this is my ip address posting from > >> >> > > eternal. > >> >> > > >> >> > owl: > >> >> > Cool. It matches with my first code. > >> >> > >> >> > anon@lowtide:~$ echo 109.72.51.248 |md5sum > >> >> > fd81dcdbef0d516b4ec84ec977a7b6d0 - > >> >> > anon@lowtide:~$ echo -n 109.72.51.248 |md5sum > >> >> > c5fd5ec5996a00946001a1952cc5e09b - > >> >> > anon@lowtide:~$ cd code/md5 > >> >> > anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 > >> >> > 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b > >> >> > anon@lowtide:~/code/md5$ > >> >> > >> >> > I don't know why the other eternal hash didn't match. > >> >> > I'll see if grep finds yours in out128. Back in a few... > >> >> > >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> >> time LANG=C grep -m 1 -F c5fd5ec5996a00946001a1952cc5e09b out128 > >> >> 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b > >> > > >> >> real 3m24.053s user 0m10.160s sys 0m8.512s > >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ > >> > > >> >> Excellent. It found it. > >> >> Thank, Melzzzzz. > >> > > >> > I got you beat: > >> > > >> > Applications/Shell> time ./ipdecode.sh > >> > c5fd5ec5996a00946001a1952cc5e09b > >> > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 > >> > real 0m51.322s > >> > user 13m11.226s > >> > sys 0m2.687s > >> > > >> > >> That's impressive. Can you do these? > >> > >> 73bc0032541f55c8e8b7366f126961f0 > > 10.0.128.33 > > Did you use the collision algorithm you spoke of earlier? No. I just hash all ip values. Time needed to hash all of them is 26 minutes on my comp.
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 16:17 +0000 |
| Message-ID | <fhjid903.a4@rooftop.invalid> |
| In reply to | #352890 |
Melzzzzz <mel@zzzzz.com> wrote: > On Sat, 30 Apr 2016 15:40:00 +0000 (UTC) > owl <owl@rooftop.invalid> wrote: > >> Melzzzzz <mel@zzzzz.com> wrote: >> > On Sat, 30 Apr 2016 14:35:08 +0000 (UTC) >> > owl <owl@rooftop.invalid> wrote: >> > >> >> Sandman <mr@sandman.net> wrote: >> >> > In article <sdfhjv03.ar3@rooftop.invalid>, owl wrote: >> >> > >> >> >> > > Melzzzzz: >> >> >> > > 109.72.51.248 , this is my ip address posting from >> >> >> > > eternal. >> >> >> > >> >> >> > owl: >> >> >> > Cool. It matches with my first code. >> >> >> >> >> >> > anon@lowtide:~$ echo 109.72.51.248 |md5sum >> >> >> > fd81dcdbef0d516b4ec84ec977a7b6d0 - >> >> >> > anon@lowtide:~$ echo -n 109.72.51.248 |md5sum >> >> >> > c5fd5ec5996a00946001a1952cc5e09b - >> >> >> > anon@lowtide:~$ cd code/md5 >> >> >> > anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 >> >> >> > 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b >> >> >> > anon@lowtide:~/code/md5$ >> >> >> >> >> >> > I don't know why the other eternal hash didn't match. >> >> >> > I'll see if grep finds yours in out128. Back in a few... >> >> >> >> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> >> >> time LANG=C grep -m 1 -F c5fd5ec5996a00946001a1952cc5e09b out128 >> >> >> 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b >> >> > >> >> >> real 3m24.053s user 0m10.160s sys 0m8.512s >> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >> >> > >> >> >> Excellent. It found it. >> >> >> Thank, Melzzzzz. >> >> > >> >> > I got you beat: >> >> > >> >> > Applications/Shell> time ./ipdecode.sh >> >> > c5fd5ec5996a00946001a1952cc5e09b >> >> > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 >> >> > real 0m51.322s >> >> > user 13m11.226s >> >> > sys 0m2.687s >> >> > >> >> >> >> That's impressive. Can you do these? >> >> >> >> 73bc0032541f55c8e8b7366f126961f0 >> > 10.0.128.33 >> >> Did you use the collision algorithm you spoke of earlier? > > No. I just hash all ip values. Time needed to hash all of them is 26 > minutes on my comp. > Yeah. I realized that and modified my code. anon@lowtide:~/code/md5$ time ./checkip 0.0.0.0 255.255.255.255 73bc0032541f55c8e8b7366f126961f0 >/dev/null matched. 73bc0032541f55c8e8b7366f126961f0 10.0.128.33 real 1m54.965s user 1m54.760s sys 0m0.164s anon@lowtide:~/code/md5$ I'll set this in parallel and test a random one. Will be nice to free up that 200GB. :)
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 17:23 +0000 |
| Message-ID | <fhjf02.fa4r@rooftop.invalid> |
| In reply to | #352892 |
owl <owl@rooftop.invalid> wrote: > Melzzzzz <mel@zzzzz.com> wrote: >> On Sat, 30 Apr 2016 15:40:00 +0000 (UTC) >> owl <owl@rooftop.invalid> wrote: >> >>> Melzzzzz <mel@zzzzz.com> wrote: >>> > On Sat, 30 Apr 2016 14:35:08 +0000 (UTC) >>> > owl <owl@rooftop.invalid> wrote: >>> > >>> >> Sandman <mr@sandman.net> wrote: >>> >> > In article <sdfhjv03.ar3@rooftop.invalid>, owl wrote: >>> >> > >>> >> >> > > Melzzzzz: >>> >> >> > > 109.72.51.248 , this is my ip address posting from >>> >> >> > > eternal. >>> >> >> > >>> >> >> > owl: >>> >> >> > Cool. It matches with my first code. >>> >> >> >>> >> >> > anon@lowtide:~$ echo 109.72.51.248 |md5sum >>> >> >> > fd81dcdbef0d516b4ec84ec977a7b6d0 - >>> >> >> > anon@lowtide:~$ echo -n 109.72.51.248 |md5sum >>> >> >> > c5fd5ec5996a00946001a1952cc5e09b - >>> >> >> > anon@lowtide:~$ cd code/md5 >>> >> >> > anon@lowtide:~/code/md5$ ./md5ip 109.72.51.248 109.72.51.248 >>> >> >> > 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b >>> >> >> > anon@lowtide:~/code/md5$ >>> >> >> >>> >> >> > I don't know why the other eternal hash didn't match. >>> >> >> > I'll see if grep finds yours in out128. Back in a few... >>> >> >> >>> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >>> >> >> time LANG=C grep -m 1 -F c5fd5ec5996a00946001a1952cc5e09b out128 >>> >> >> 109.72.51.248 c5fd5ec5996a00946001a1952cc5e09b >>> >> > >>> >> >> real 3m24.053s user 0m10.160s sys 0m8.512s >>> >> >> anon@lowtide:/media/anon/5331134e-f853-4f49-876b-863d26af6261/ips$ >>> >> > >>> >> >> Excellent. It found it. >>> >> >> Thank, Melzzzzz. >>> >> > >>> >> > I got you beat: >>> >> > >>> >> > Applications/Shell> time ./ipdecode.sh >>> >> > c5fd5ec5996a00946001a1952cc5e09b >>> >> > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 >>> >> > real 0m51.322s >>> >> > user 13m11.226s >>> >> > sys 0m2.687s >>> >> > >>> >> >>> >> That's impressive. Can you do these? >>> >> >>> >> 73bc0032541f55c8e8b7366f126961f0 >>> > 10.0.128.33 >>> >>> Did you use the collision algorithm you spoke of earlier? >> >> No. I just hash all ip values. Time needed to hash all of them is 26 >> minutes on my comp. >> > Yeah. I realized that and modified my code. > anon@lowtide:~/code/md5$ time ./checkip 0.0.0.0 255.255.255.255 73bc0032541f55c8e8b7366f126961f0 >/dev/null > > matched. > 73bc0032541f55c8e8b7366f126961f0 > 10.0.128.33 > > real 1m54.965s > user 1m54.760s > sys 0m0.164s > anon@lowtide:~/code/md5$ > > I'll set this in parallel and test a random one. > Will be nice to free up that 200GB. :) > Yay. anon@lowtide:~/code/md5$ echo -n 132.37.105.4 |md5sum 171b0339925a83f7d4daffaf580abfa9 - anon@lowtide:~/code/md5$ time ./docheckip.sh 171b0339925a83f7d4daffaf580abfa9 2>/dev/null matched. 171b0339925a83f7d4daffaf580abfa9 132.37.105.4 real 1m24.074s user 10m58.648s sys 0m1.508s anon@lowtide:~/code/md5$ That's with breaking along the same 8 boundaries as before for parallelizing. I might explore narrowing and removal of ranges and see if it gets better.
[toc] | [prev] | [next] | [standalone]
| From | Peter Köhlmann <peter-koehlmann@t-online.de> |
|---|---|
| Date | 2016-05-01 00:56 +0200 |
| Message-ID | <ng3d0j$kvq$1@dont-email.me> |
| In reply to | #352861 |
The lying imbecile Snit Michael Glasser snotted: > On 4/30/16, 3:31 PM, in article > sandman-7271c4fad61d7b5e25b4868bf66da5e4@individual.net, "Sandman" > <mr@sandman.net> wrote: > >> In article <ghjdie993.ga@rooftop.invalid>, owl wrote: >> >>>> Sandman: >>>> I got you beat: >>> >>>> Applications/Shell>time ./ipdecode.sh >>>> c5fd5ec5996a00946001a1952cc5e09b >>>> c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 >>> >>>> real 0m51.322s >>>> user 13m11.226s >>>> sys 0m2.687s >>> >>> That's impressive. Can you do these? >> >>> 73bc0032541f55c8e8b7366f126961f0 >>> 1ab71f9efbdd66785a8ee9e31cf301e5 >> >>> One of them I know is an ipv4 address. The other I don't know. >> >> 73bc0032541f55c8e8b7366f126961f0 = 10.0.128.33 >> >> 1ab71f9efbdd66785a8ee9e31cf301e5 ≈ 199.48.241.55, known TOR proxy >> by Snit. > > To be clear: this is a direct lie from Sandman... with a repulsive > insinuation tied to it. Repulsive is only one person here: You You are not worth to be pissed on, you lying parasetic imbecile Haven't you learned something from the jail time you spent early this year?
[toc] | [prev] | [next] | [standalone]
| From | Peter Köhlmann <peter-koehlmann@t-online.de> |
|---|---|
| Date | 2016-05-01 01:30 +0200 |
| Message-ID | <ng3f0m$adn$1@dont-email.me> |
| In reply to | #352964 |
The lying imbecile Snit Michael Glasser snotted: > On 4/30/16, 3:56 PM, in article ng3d0j$kvq$1@dont-email.me, "Peter > Köhlmann" <peter-koehlmann@t-online.de> wrote: > >>>>> One of them I know is an ipv4 address. The other I don't know. >>>> >>>> 73bc0032541f55c8e8b7366f126961f0 = 10.0.128.33 >>>> >>>> 1ab71f9efbdd66785a8ee9e31cf301e5 ≈ 199.48.241.55, known TOR proxy >>>> by Snit. >>> >>> To be clear: this is a direct lie from Sandman... with a repulsive >>> insinuation tied to it. >> >> Repulsive is only one person here: You > > So you do not think it is repulsive for Sandman to lie about me. OK. > >> You are not worth to be pissed on, you lying parasetic imbecile >> >> Haven't you learned something from the jail time you spent early this >> year? > > And you do not think it is repulsive for you to lie about me. Feel free to prove that I lied, Fraud Do you really think that people haven't noticed your conspicious "absence"? You have not worked for several years, so you don't have any believable "excuse" why you should be totally off the net for month. Someone who works and is very busy has at least time enough to be visible sometimes. You have vanished totally for several month. There are only 2 possible reasons: You were in hospital because of severe medical problems (and you would have told us), or you have been in jail You have exactly one guess what is more likely. You were in jail. And given your history of fraudulent behaviour, it is not so difficult to see why
[toc] | [prev] | [next] | [standalone]
| From | owl <owl@rooftop.invalid> |
|---|---|
| Date | 2016-04-30 23:11 +0000 |
| Message-ID | <ghnvmfj939a.afju@rooftop.invalid> |
| In reply to | #352861 |
Sandman <mr@sandman.net> wrote: > In article <ghjdie993.ga@rooftop.invalid>, owl wrote: > >> > Sandman: >> > I got you beat: >> >> > Applications/Shell>time ./ipdecode.sh >> > c5fd5ec5996a00946001a1952cc5e09b >> > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 >> >> > real 0m51.322s >> > user 13m11.226s >> > sys 0m2.687s >> >> That's impressive. Can you do these? > >> 73bc0032541f55c8e8b7366f126961f0 >> 1ab71f9efbdd66785a8ee9e31cf301e5 > >> One of them I know is an ipv4 address. The other I don't know. > > 73bc0032541f55c8e8b7366f126961f0 = 10.0.128.33 > > 1ab71f9efbdd66785a8ee9e31cf301e5 ≈ 199.48.241.55, known TOR proxy by Snit. > What was the original string on that one? It's not a hash of just "199.48.241.55" with or without newline. anon@lowtide:~$ echo -n 199.48.241.55 |md5sum a90b6fea5f35669a90d5f0ef20a40366 - anon@lowtide:~$ echo 199.48.241.55 |md5sum 33ced598cb650c2157f4a99cde0303db - anon@lowtide:~$
[toc] | [prev] | [next] | [standalone]
| From | Sandman <mr@sandman.net> |
|---|---|
| Date | 2016-05-01 08:38 +0000 |
| Message-ID | <sandman-2f3d08a25915707781db047bc35b4457@individual.net> |
| In reply to | #352965 |
In article <ghnvmfj939a.afju@rooftop.invalid>, owl wrote: > > > > Sandman: > > > > I got you beat: > > > > > > > Applications/Shell>time ./ipdecode.sh > > > > c5fd5ec5996a00946001a1952cc5e09b > > > > c5fd5ec5996a00946001a1952cc5e09b:109.72.51.248 > > > > > > > real 0m51.322s > > > > user 13m11.226s > > > > sys 0m2.687s > > > > > > owl: > > > That's impressive. Can you do these? > > > > > 73bc0032541f55c8e8b7366f126961f0 > > > 1ab71f9efbdd66785a8ee9e31cf301e5 > > > > > One of them I know is an ipv4 address. The other I don't know. > > > > Sandman: > > 73bc0032541f55c8e8b7366f126961f0 = 10.0.128.33 > > > 1ab71f9efbdd66785a8ee9e31cf301e5 ≈ 199.48.241.55, known TOR > > proxy by Snit. > > What was the original string on that one? It's not a hash > of just "199.48.241.55" No, hence the "≈". The host "1ab71f9efbdd66785a8ee9e31cf301e5" has been used by: - Edward Stansfield - Big Fish in a Small Crotch - Barry H - anonymous - mike antipasto - Nobody - Omar - Richard King - Richard Bone And going through them, "Barry H" has also used the host "a90b6fea5f35669a90d5f0ef20a40366", which is 199.48.241.55. You can use this page to search a bit: <http://usenet.sandman.net/misc/eternal.php>? hash=1ab71f9efbdd66785a8ee9e31cf301e5> <http://usenet.sandman.net/misc/eternal.php?name=Barry+H> It's not so much about what the actual host is, we all know all the gym's above are Snit sock puppets. :) -- Sandman
[toc] | [prev] | [next] | [standalone]
Page 1 of 6 [1] 2 3 4 5 6 Next page →
Back to top | Article view | comp.os.linux.advocacy
csiph-web