[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    Re: [kdepim-users] Re: Problem with pinentry
From:       Miles Sabin <miles () milessabin ! com>
Date:       2004-05-31 13:02:46
Message-ID: 200405311402.46946.miles () milessabin ! com
[Download RAW message or body]

Ingo Klöcker wrote,
> On Monday 31 May 2004 13:54, Miles Sabin wrote:
> > What determines how big the secure memory pool needs to be? It's a
> > bit ugly to have to hard-code a limit like this.
>
> It probably depends on the widget style that you use. In pinentry-qt
> 0.7.x the whole secure memory handling has been completely rewritten.

FWIW, I'm using the Plastik style.

> On Monday 31 May 2004 14:31, Miles Sabin wrote:
> > I haven't tried pinentry-gtk (it's not built by default with
> > Konstruct, and I don't have time to mess around at the mo'), but I
> > don't think that option's likely to work: it uses the default pool
> > size which is #defined to 16384 in secmem.c ... which is much to
> > small if 16384*8 is.
> >
> > Either that or I'm completely misunderstanding the meaning of the
> > size_t arg to secmem_init.
>
> pinentry-gtk uses much less secure memory because it already uses
> specifically designed widgets which only use the secure memory for
> the passphrase. The same has been done for pinentry-qt 0.7.x.

Ahh ... understood. Thanks for the explanation.

Cheers,


Miles
_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users

[prev in list] [next in list] [prev in thread] [next in thread]