Re: Failing to known state - Mailing list pgsql-general

From Joshua D. Drake
Subject Re: Failing to known state
Date
Msg-id 568C52BC.7030703@commandprompt.com
Whole thread Raw
In response to Re: Failing to known state  (oleg yusim <olegyusim@gmail.com>)
Responses Re: Failing to known state  (oleg yusim <olegyusim@gmail.com>)
List pgsql-general
On 01/05/2016 03:21 PM, oleg yusim wrote:
> Thanks JD.
>
>  From what I read about WAL (you have been referring to this:
> http://www.postgresql.org/docs/current/static/wal-internals.html
> pg_xlog, right?) it allows us to know what happened, but does it
> warranty known secure state? I mean, I do not think it would help with this:
>
> "In general, security mechanisms should be designed so that a failure
> will follow the same execution path as disallowing the operation. For
> example, application security methods, such as isAuthorized(),
> isAuthenticated(), and validate(), should all return false if there is
> an exception during processing. If security controls can throw
> exceptions, they must be very clear about exactly what that condition
> means. "

You are correct, that isn't the pg_xlog but yes, PostgreSQL will throw
an exception in those types of cases.

Sincerely,

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/  503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Announcing "I'm offended" is basically telling the world you can't
control your own emotions, so everyone else should do it for you.


pgsql-general by date:

Previous
From: oleg yusim
Date:
Subject: Re: Failing to known state
Next
From: Adrian Klaver
Date:
Subject: Re: Failing to known state