Kevin,
It is understood. But doesn't change things from my perspective. It would
anyway be user, with sole access, nobody can elevate privileges to and only
root can su to. The name, in that case, is irrelevant, but answer postgres
gave me idea of the protection level here.
Thanks,
Oleg
On Wed,
On Wed, Jan 13, 2016 at 3:54 PM, oleg yusim wrote:
> Answer "postgres" would suffice.
But the user would not always be "postgres". To be accurate, it is
the user which owns the files for the "cluster" (database instance)
and which runs the database service. If a machine contains
multiple clust
David,
Answer "postgres" would suffice. I have fairly decent idea of what happens
below that (you are right system utility - Memory Manager is what
marshaling data back and forth to RAM, abstracting absolute addresses from
application along the way, and once in RAM, security kernel of the system
p
On Wed, Jan 13, 2016 at 2:37 PM, oleg yusim wrote:
> OK, Kevin, David,
>
> Thanks you very much for explanation. Now who is the owner of this
> process? My understanding is, data then located physically in RAM, in the
> memory stack assigned by OS to this process. Now the question is who owns
> t
OK, Kevin, David,
Thanks you very much for explanation. Now who is the owner of this process?
My understanding is, data then located physically in RAM, in the memory
stack assigned by OS to this process. Now the question is who owns the
process?
Thanks,
Oleg
On Wed, Jan 13, 2016 at 3:29 PM, Dav
On Wed, Jan 13, 2016 at 2:19 PM, Kevin Grittner wrote:
> On Wed, Jan 13, 2016 at 2:57 PM, oleg yusim wrote:
>
> > Say, I got network package. The package was decrypted by OpenSSL. Where
> this
> > data are, physically, at this moment?
>
> Process-local memory for the PostgreSQL backend process a
On Wed, Jan 13, 2016 at 2:57 PM, oleg yusim wrote:
> Say, I got network package. The package was decrypted by OpenSSL. Where this
> data are, physically, at this moment?
Process-local memory for the PostgreSQL backend process associated
with the database connection.
> Opposite situation: we are
Kevin,
Thank you for your reply. I understand what you are saying, but I guess I
need a bit deeper understanding for my assessment. Let's dive a bit here:
Say, I got network package. The package was decrypted by OpenSSL. Where
this data are, physically, at this moment?
Opposite situation: we are
On Tue, Jan 12, 2016 at 10:00 PM, oleg yusim wrote:
> Important: let's assume data at rest is encrypted using EFS and data at
> transit is encrypted using ciphers, provided by OpenSSL.
>
> So, with that in mind, please, help me to understand movement and location
> of the data between the moment
Greetings,
I have matching couple of security requirements, speaking about preserving
data confidentiality and integrity in PostgreSQL DB during packaging for
transmission / unpacking from transmission.
Important: let's assume data at rest is encrypted using EFS and data at
transit is encrypted u
10 matches
Mail list logo
