Subject | Re: [firebird-support] Can non-sysdba really alter users? |
---|---|
Author | Tomasz Tyrakowski |
Post date | 2012-09-18T08:55:49Z |
On 2012-09-18 09:39, Mark Rotteveel wrote:
to a copy of security2.fdb with WIN1250, FlameRobin warned me that the
database encoding is NONE, so I changed the connection encoding to match
it. I've just tried UTF8 and UNICODE_FSS and I can still see
80-characters long ciphers. An example (I split the lines for the
readability's sake - in the DB that's the content of the RDB$PASS in a
single record):
45645867684b6f324465
3156324a354c4f514f59
71653550417572706147
78704a7569637650383d
regards
Tomasz
--
__--==============================--__
__--== Tomasz Tyrakowski ==--__
__--== SOL-SYSTEM ==--__
__--== http://www.sol-system.pl ==--__
__--==============================--__
>> could you spend half a minute and look into your security2.fdb to checkIn fact it's "NONE". Usually I use WIN1250, but when I tried to connect
>> if your varchar(64) RDB$USERS.RDB$PASS field also contains 80-character
>> long ciphers?
>> That's kind of intriguing, isn't it?
>
> What is your connection characterset? What happens if you connect using
> UTF8 or UNICODE_FSS?
to a copy of security2.fdb with WIN1250, FlameRobin warned me that the
database encoding is NONE, so I changed the connection encoding to match
it. I've just tried UTF8 and UNICODE_FSS and I can still see
80-characters long ciphers. An example (I split the lines for the
readability's sake - in the DB that's the content of the RDB$PASS in a
single record):
45645867684b6f324465
3156324a354c4f514f59
71653550417572706147
78704a7569637650383d
regards
Tomasz
--
__--==============================--__
__--== Tomasz Tyrakowski ==--__
__--== SOL-SYSTEM ==--__
__--== http://www.sol-system.pl ==--__
__--==============================--__