Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > microsoft.public.scripting.vbscript > #11839
| From | GS <gs@v.invalid> |
|---|---|
| Newsgroups | microsoft.public.scripting.vbscript |
| Subject | Re: Decode-email |
| Date | 2018-02-16 23:32 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <p68b8t$9kh$1@dont-email.me> (permalink) |
| References | <p65b0i$lv6$1@dont-email.me> <ljcgouzp7580$.vcj771vl6v39.dlg@40tude.net> <p67qbo$kag$1@dont-email.me> <p67v6u$euc$1@dont-email.me> <p68aec$4gu$1@dont-email.me> |
> "GS" <gs@v.invalid> wrote > >>>> You might be interrested on CloudFlare's encrypted email. >>> >>> Cloudflare is the one I wrote it for. Though I'd >>> guess there may be other sites using it. I had >>> to figure it out by tracking the values as the >>> loop ran. >> >> I'm thinking they use their own proprietary version since a generic version >> would be too easy to hack. More likely that Perl(1) or PHP(2) is used! >> > No, they're using javascript. It's a popular, small script > that's available online: > > http://codegists.com/snippet/javascript/email-decodeminjs_zhanglianxin_javascript > > Nobody does proprietary. :) Most webmasters don't > knw how to write code. They just use stuff others > have written. If you pull in the various script llibraries > used by big websites you'll usually see things like > an MIT license and author info in them. > > The way I worked out the code was to run the > link to the javascript file in the source code, get > that into the browser, and copy it. What surprises > me is how complex it is. There's no concern with > hacking. They'd need something a lot more fancy > for that. > > I think I figured out why some numbers don't work. > I'm curious how you found the range that fails. In > any case, I tried 44, in one of the ranges you noted > didn't work. Then I looked at the result and realized > that the problem was a single-character hex code. > A period is 46. 44 xor 46 is 2. That results in all following > characters being misread. But it can be fixed by adding a 0. > > s2 = Hex(iKey) > For i = 1 to Len(sEmail) > iVal = Asc(Mid(sEmail, i, 1)) > iVal = iVal XOR iKey > '-- make sure a 0 is prepended if Hex result is only one character. > s2 = s2 & Right( "00" & Hex(iVal), 2) > Next I tested each 2 digit possibility. I'll modify your code with this update and redo the tests... -- Garry Free usenet access at http://www.eternal-september.org Classic VB Users Regroup! comp.lang.basic.visual.misc microsoft.public.vb.general.discussion
Back to microsoft.public.scripting.vbscript | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-15 20:09 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-15 22:52 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-15 23:02 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-15 23:34 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-16 00:44 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-16 09:46 -0500
Re: Decode-email JJ <jj4public@vfemail.net> - 2018-02-17 22:00 +0700
Re: Decode-email JJ <jj4public@vfemail.net> - 2018-02-17 01:46 +0700
Re: Decode-email GS <gs@v.invalid> - 2018-02-16 15:30 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-17 09:29 -0500
Re: Decode-email JJ <jj4public@vfemail.net> - 2018-02-17 21:47 +0700
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 19:51 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-17 20:33 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 21:40 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 21:43 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-17 22:57 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 23:10 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-17 23:18 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 23:41 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-18 10:23 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-18 10:38 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-18 11:09 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-18 13:20 -0500
Re: Decode-email JJ <jj4public@vfemail.net> - 2018-02-18 09:47 +0700
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 21:50 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-16 18:43 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-16 20:06 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-16 23:18 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-16 23:32 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 00:00 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-17 09:24 -0500
Re: Decode-email "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2018-02-17 16:07 +0100
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-17 10:46 -0500
Re: Decode-email "Evertjan." <exxjxw.hannivoort@inter.nl.net> - 2018-02-17 18:18 +0100
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 21:46 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-17 23:09 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 23:13 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-17 23:23 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-18 10:32 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-18 10:41 -0500
Re: Decode-email "Mayayana" <mayayana@invalid.nospam> - 2018-02-18 16:30 -0500
Re: Decode-email GS <gs@v.invalid> - 2018-02-18 16:41 -0500
csiph-web