| From: | Horst Herb <hherb(at)malleenet(dot)net(dot)au> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: RFC: CRC datatype |
| Date: | 2000-12-13 04:06:24 |
| Message-ID: | 00121315062405.03185@munin.midgard |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
O
> > Always remember that a psotgres data base on the harddisk can be
> > manipulated accidentally / maliciously without postgres even running.
> > These are the cases where you need row level CRCs.
>
> "There is no security without physical security." If somebody can
> change the row contents, they can also change the row and/or block
> checksum to match.
They may, but in a proper setup they won't be able to access the CRC log
files. That way, you can still detect alterations. I presume anyway that most
alterations would be rather accidental than malicious, and in that case the
CRC is extremely helpful
Horst
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-12-13 04:56:22 | Re: Re: COPY BINARY file format proposal |
| Previous Message | mlw | 2000-12-13 00:41:36 | Re: external function proposal for 7.2 |