Re: [sqlmap-users] Back-end DBMS charset encoding
Brought to you by:
inquisb
From: mitchell <mit...@tu...> - 2011-01-18 11:20:09
|
Will do :) # mitchell On 18 Jan 2011 13:11, "Miroslav Stampar" <mir...@gm...> wrote: > hi mitchell. > > thank you for your answer. i thought that nobody would :) > > we've done some serious work these days in this field and would like > to have it "stabilized". plz report any "strange" behavior in this > field if you encounter it. > > kr > > On Tue, Jan 18, 2011 at 12:01 PM, mitchell <mit...@tu...> wrote: >> Hi Miroslav, >> >> In say 80% of the cases I delt with Bulgarian sites, the data in the >> database used the same encoding as the encoding announced on the webpage, >> usually CP-1251. The rest use UTF. >> >> # mitchell >> >> On 17 Jan 2011 16:52, "Miroslav Stampar" <mir...@gm...> wrote: >>> Hi all. >>> >>> I have a general question to all those pentesters that are retrieving data >>> from sites with "funny" charset encodings (...russian, chinese...). >>> >>> What's should be the general "consensus" for data retrieval: >>> >>> A) assume that the backend DBMS uses the "utf8" charset encoding >>> or >>> B) treat data retrieved with the same encoding as used in the page >>> or >>> C) find out the proper collation used and use that one? (i am not a fan of >>> this one :) >>> or >>> D) don't care (some people tend to use mixed collations which is quite >>> romantic) >>> >>> Also, I would like to ask you all to try out the latest revision with >>> cases >>> that could be problematic and report impressions. >>> >>> Kind regards >> > > > > -- > Miroslav Stampar > > E-mail / Jabber: miroslav.stampar (at) gmail.com > Mobile: +385921010204 (HR 0921010204) > PGP Key ID: 0xB5397B1B > Location: Zagreb, Croatia |