Re: debugger from superuser only.... why?

From: "Alexander Petrossian (PAF)" <alexander(dot)petrossian(at)gmail(dot)com>
To: Luca Ferrari <fluca1978(at)gmail(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: debugger from superuser only.... why?
Date: 2023-09-22 12:00:30
Message-ID: CA+VOcq820hDvE8063xdJ8hiozbzj8B+=S1EoXrWqqnKR0y=GdQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

>
>
> > SELECT * FROM pldbg_set_global_breakpoint(1, 65695, -1, NULL);
> > ERROR: must be a superuser to create a breakpoint
> > I am wondering why is this, why not allow debugging for non-privileged
> users?
>
> Again, I'm suspecting that this debugger works by performing a
> sandboxing and attaching your session back. In order to communicate
> back and forth, you probably need such privileges.
> You should ask the developers why they need such privileges, or dig
> the code by yourself.
>

Some mail list you would suggest, Luka?

> > SELECT * FROM pldbg_create_listener();
> uh oh, it mentions a listener...then there must be some "sender"
> somehwere, that probably needs privileges.
>

Surprisingly this passes OK under non-privileged user.

PAF

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dominique Devienne 2023-09-22 13:24:18 Re: How to fork pg_dump or psql w/o leaking secrets?
Previous Message Luca Ferrari 2023-09-22 11:49:14 Re: debugger from superuser only.... why?