Re: [WebDNA] WebDNA 8.2 and BioType
This WebDNA talk-list message is from 2016
It keeps the original formatting.
numero = 112588
interpreted = N
texte = 170 Sure, you could build something like that already.. Especially since you can= do almost everything in [table]'s that you can when interacting with a .db f= ile.=20 I'm not necessarily against an encryption method for .db files.. But I would= point out that WebDNA is not the be all end all of security.=20 One can already lock down .db files using the Linux tools so that only root o= r a super user can get to the contents.=20 If you are then worried about an HD being stolen or root being cracked, AND,= if you don't like encrypting individual values for some reason, I think on= e could then employ the hard drive encryption methods of the OS.=20 So, my point being that there is already lots of options for security.=20 D. Brooke Mobile > On Feb 24, 2016, at 9:20 AM, christophe.billiottet@webdna.us wrote: >=20 > It would be an interesting feature: we could imagine the database would ru= n NOT encrypted from RAM (to allow regular database operations), and that ea= ch time WebDNA needs to update the disk, it builds an encrypted copy: this i= s this copy that would be written to disk. There would be a speed impact onl= y when writing to or reading from disk. >=20 > I wonder if you cannot already build something like that with the current t= ools. >=20 > - chris >=20 >=20 >=20 >=20 >=20 >>> On Feb 24, 2016, at 18:12, Kenneth Grome
wrote= : >>>=20 >>> The security tools that are now built into WebDNA are among the >>> best you can find anywhere >>=20 >> Yet it still cannot encrypt an entire database thus eliminating >> the need to encrypt specific field values. >>=20 >> Seems strange to think that templates and include files can be >> encrypted yet our databases cannot, even though our most critical >> data is stored in these db files. >>=20 >> I hereby request a new feature that encrypts all the data in our >> dbs by default. I would use a feature like this. >>=20 >> Regards, >> Kenneth Grome >> WebDNA Solutions >> http://www.webdnasolutions.com >> Web Database Systems and Linux Server Administration >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Associated Messages, from the most recent to the oldest:
170 Sure, you could build something like that already.. Especially since you can= do almost everything in [table]'s that you can when interacting with a .db f= ile.=20 I'm not necessarily against an encryption method for .db files.. But I would= point out that WebDNA is not the be all end all of security.=20 One can already lock down .db files using the Linux tools so that only root o= r a super user can get to the contents.=20 If you are then worried about an HD being stolen or root being cracked, AND,= if you don't like encrypting individual values for some reason, I think on= e could then employ the hard drive encryption methods of the OS.=20 So, my point being that there is already lots of options for security.=20 D. Brooke Mobile > On Feb 24, 2016, at 9:20 AM, christophe.billiottet@webdna.us wrote: >=20 > It would be an interesting feature: we could imagine the database would ru= n NOT encrypted from RAM (to allow regular database operations), and that ea= ch time WebDNA needs to update the disk, it builds an encrypted copy: this i= s this copy that would be written to disk. There would be a speed impact onl= y when writing to or reading from disk. >=20 > I wonder if you cannot already build something like that with the current t= ools. >=20 > - chris >=20 >=20 >=20 >=20 >=20 >>> On Feb 24, 2016, at 18:12, Kenneth Grome wrote= : >>>=20 >>> The security tools that are now built into WebDNA are among the >>> best you can find anywhere >>=20 >> Yet it still cannot encrypt an entire database thus eliminating >> the need to encrypt specific field values. >>=20 >> Seems strange to think that templates and include files can be >> encrypted yet our databases cannot, even though our most critical >> data is stored in these db files. >>=20 >> I hereby request a new feature that encrypts all the data in our >> dbs by default. I would use a feature like this. >>=20 >> Regards, >> Kenneth Grome >> WebDNA Solutions >> http://www.webdnasolutions.com >> Web Database Systems and Linux Server Administration >>=20 >> --------------------------------------------------------- >> This message is sent to you because you are subscribed to >> the mailing list . >> To unsubscribe, E-mail to: >> archives: http://mail.webdna.us/list/talk@webdna.us >> Bug Reporting: support@webdna.us >=20 > --------------------------------------------------------- > This message is sent to you because you are subscribed to > the mailing list . > To unsubscribe, E-mail to: > archives: http://mail.webdna.us/list/talk@webdna.us > Bug Reporting: support@webdna.us --------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdna.us .
Donovan Brooke
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
[searchString] (1997)
Amusement (2004)
Locking up with WebCatalog... (1997)
webcat NT (1998)
[WebDNA] Record click-thrus (2008)
User/Pass dialogue issue [AOL?] (2002)
Not really WebCat (1997)
WebCat2 Append problem (B14Macacgi) (1997)
WebCat2b13MacPlugIn - [include] doesn't allow creator (1997)
form data submission gets truncated (1997)
Web Logs (1998)
Webcatalog, Webstar and Crasharama (1999)
Sorting search by date. (2000)
Question about [encrypt] (1998)
Referrer field to header field conversion (1997)
RE: IIS4b2 and WebCatalog b19 (1997)
Formulas.db (2001)
I give up!! (1997)
Location of Browser Info.txt file (1997)
RE:It just Does't add up!!! (1997)