Re: exporting _gtk_selection_request for selection manager use

Thanks I'll look at the gnome-settings-daemon. A little background,
the problem I'm looking to address is the one related to MCS/MLS
policy in the SELinux world where you are copying and pasting between
windows of different contexts and or levels. In particular my concern
is MLS where you need a 'middle man' to be able to downgrade
information in a secure way when copying from a higher level
window/app and pasting to a lower level window/app. Could you please
expand upon what types of problems 'eager' clipboard managers cause?


On Sat, Mar 15, 2008 at 11:57 AM, Matthias Clasen
<matthias clasen gmail com> wrote:
> On Thu, Mar 13, 2008 at 1:38 PM, Xavier Toth <txtoth gmail com> wrote:
>  > I'm working on a secure selection manager based on glipper. What it
>  >  needs to be able to do is intervene and make a security determination
>  >  when a paste is requested. 'glipper' currently monitors clipboard
>  >  ownership changes at which time is gets the clipboard contents. I've
>  >  modified glipper to become the selection owner after it get the
>  >  clipboard contents and connected a 'selection-request-event' handler
>  >  to process pastes. I'd like to make the security decision and then
>  >  either send a selection notify with GDK_NONE or use the default
>  >  behavior of _gtk_selection_request but this function isn't exported,
>  >  could it be?
>  I hope you are aware that such 'eager' clipboard manager can cause a
>  lot of problems.
>  GTK+ supports a protocol that lets clipboard manager defer getting the
>  actual clipboard contents until the clipboard owner is about to die.
>  An implementation of such a clipboard manager can be found  in
>  gnome-settings-daemon.
>  Matthias

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]