Article View: pl.comp.lang.delphi
Article #346511RODO - szyfrowanie bazy danych ERP
From: kameleonsql
Date: Wed, 04 Apr 2018 11:26
Date: Wed, 04 Apr 2018 11:26
9 lines
1502 bytes
1502 bytes
Witam, Jak uważacie? RODO spowoduje, że szyfrowanie bazy danych stanie się obowiązkiem ? Ps. Jeśli tak, to jak temat ogarnąć w sprytny sposób (baza danych Firebird 3.0, teoretycznie szyfrowanie jest wspierane). Pozdrawiam Roman
Technical Details
Message-ID:
<329fadca-a3e2-4da5-961f-113419382376@googlegroups.com>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!u184-v6no6168572ita.0!news-out.google.com!u64-v6ni7823itb.0!nntp.google.com!k65-v6no4377178ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mailShow Full Headers
Complete Article Headers
X-Received: by 2002:a24:2105:: with SMTP id e5-v6mr3988377ita.55.1522841212232; Wed, 04 Apr 2018 04:26:52 -0700 (PDT) X-Received: by 2002:a9d:e5b:: with SMTP id n27-v6mr1010226otd.2.1522841212027; Wed, 04 Apr 2018 04:26:52 -0700 (PDT) Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!u184-v6no6168572ita.0!news-out.google.com!u64-v6ni7823itb.0!nntp.google.com!k65-v6no4377178ita.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: pl.comp.lang.delphi Date: Wed, 4 Apr 2018 04:26:51 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=155.133.12.237; posting-account=lJNmiQoAAAAcuwZEAibFvFBE7IgRs9bN NNTP-Posting-Host: 155.133.12.237 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <329fadca-a3e2-4da5-961f-113419382376@googlegroups.com> Subject: RODO - szyfrowanie bazy danych ERP From: kameleonsql@gmail.com Injection-Date: Wed, 04 Apr 2018 11:26:52 +0000 X-Received-Bytes: 1440 X-Received-Body-CRC: 2538527302 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit