Bug#773996: assword: Problems with accents in context

[Jameson Graef Rollins]

On Sun, May 08 2016, Jameson Graef Rollins  wrote:
> [ Unknown signature status ]
> On Fri, 26 Dec 2014 23:17:12 +0100 Ivan Vilata i Balaguer  
> wrote:
>> Ivan Vilata i Balaguer (2014-12-26 22:42:15 +0100) wrote:
>> 
>> > […] Maybe it's some kind on encoding problem.  If I dump the database,
>> > I can see that the context is always escaped using ``\u`` (even if
>> > ``\x`` was enough), i.e. it has become ``aix\u00f2``.  There should be
>> > no need of such escaping since JSON documents are UTF-8 native, so
>> > this only adds a chance for encoding errors. […]
>> 
>> Please ignore this, I already checked that this escaping is also native
>> for JSON to fit in ASCII encoding. :-/
>
> Hi, Ivan.  Sorry for the very late reply.
>
> We think the 2to3 conversion we're doing right now will fix this bug.
> We'll be making a new release eminently.

The 0.10 release, which uses python3 in the utility program and seems to
handle accents much better, has been uploaded to unstable.

jamie.


signature.asc
Description: PGP signature

Bug#773996: assword: Problems with accents in context

[Jameson Graef Rollins]

On Fri, 26 Dec 2014 23:17:12 +0100 Ivan Vilata i Balaguer  
wrote:
> Ivan Vilata i Balaguer (2014-12-26 22:42:15 +0100) wrote:
> 
> > […] Maybe it's some kind on encoding problem.  If I dump the database,
> > I can see that the context is always escaped using ``\u`` (even if
> > ``\x`` was enough), i.e. it has become ``aix\u00f2``.  There should be
> > no need of such escaping since JSON documents are UTF-8 native, so
> > this only adds a chance for encoding errors. […]
> 
> Please ignore this, I already checked that this escaping is also native
> for JSON to fit in ASCII encoding. :-/

Hi, Ivan.  Sorry for the very late reply.

We think the 2to3 conversion we're doing right now will fix this bug.
We'll be making a new release eminently.

jamie.


signature.asc
Description: PGP signature

Bug#773996: assword: Problems with accents in context

[Ivan Vilata i Balaguer]

Package: assword
Version: 0.8-1
Severity: normal
Tags: upstream

(First of all thanks for the neat and nice piece of software!)

The Assword GUI cannot match contexts with accents and the like.

For instance, I create a new entry by running ``env ASSWORD_PASSWORD=prompt
assword add``.  I enter ``això`` as a context.  If I run ``assword dump això``
I get the stored password.  So far so good.

The problem shows up when I run ``assword gui`` with no context argument.
If I enter ``això`` or some letter and then select the completion for
``això``, I'm unable to fulfill the password selection with Enter, since the
label above insists in no match, even when the full matching context is in
the text box.

Maybe it's some kind on encoding problem.  If I dump the database, I can see
that the context is always escaped using ``\u`` (even if ``\x`` was enough),
i.e. it has become ``aix\u00f2``.  There should be no need of such escaping
since JSON documents are UTF-8 native, so this only adds a chance for
encoding errors.

Hopefully the fix simply consists of calling some ``.encode()`` or
``.decode()`` at the right spot in the code. :)

Thank you very much!

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages assword depends on:
ii  python2.7.8-2
ii  python-gpgme  0.3-1+b1
ii  python-gtk2   2.24.0-4
ii  python-pkg-resources  5.5.1-1

Versions of packages assword recommends:
ii  python-xdo  0.2-2
ii  xclip   0.12+svn84-4

assword suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773996: assword: Problems with accents in context

[Ivan Vilata i Balaguer]

Ivan Vilata i Balaguer (2014-12-26 22:42:15 +0100) wrote:

 […] Maybe it's some kind on encoding problem.  If I dump the database,
 I can see that the context is always escaped using ``\u`` (even if
 ``\x`` was enough), i.e. it has become ``aix\u00f2``.  There should be
 no need of such escaping since JSON documents are UTF-8 native, so
 this only adds a chance for encoding errors. […]

Please ignore this, I already checked that this escaping is also native
for JSON to fit in ASCII encoding. :-/

-- 
Ivan Vilata i Balaguer -- https://elvil.net/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#773996: assword: Problems with accents in context

[Ivan Vilata i Balaguer]

Ivan Vilata i Balaguer (2014-12-26 22:42:15 +0100) wrote:

 The Assword GUI cannot match contexts with accents and the like. […]
 
 Hopefully the fix simply consists of calling some ``.encode()`` or
 ``.decode()`` at the right spot in the code. :)

I just changed the first line in ``Gui.enter()`` to read:

e = self.entry.get_text().decode()

(note the extra ``.decode()``) so that the Unicode contexts are compared
instead of their encoded string versions, and it seems to work.  I'm not
sure about how correct it is to decode like whis without giving an
explicit encoding, though

-- 
Ivan Vilata i Balaguer -- https://elvil.net/


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org