What if there are alterations you do not know about?
Well that comes back to the trust issue. I do not use any other social media because I have seen how they change the rules at will and bury any information about the changes in very small print, if at all.
They will quite happily share my information (which is illegal in the EU without my express permission) because it is seen as having some monetary value.
If you mean what happens if the code that we are running is changed maliciously, then the blockchain idea might be useful as a flag, but then you would have to diff everything with a known good release and try to find what the changes are. But that makes the role of the administrator more important, not less. If someone has managed to get into your own code base and make changes to it then there is a permissions issue that is wrong. But using our own case as an example - they would have to know also how to build the entire site into containers, how to access the database itself, how to access the various servers that we use etc.
(Score: 0) by Anonymous Coward on Thursday February 26, @06:32PM
(7 children)
by Anonymous Coward
on Thursday February 26, @06:32PM (#1435048)
Blockchain would make it simple to run a verification on the database. Every byte of content added creates a signature, so uf someone changes a few bytes then the signature changes. Your current situation would require a complete diff against a backup.
The database is continually changing. There are internal tasks running all the time which leave results in the database. Records are created in the database when a users is accessing pages, making comments. creating journals, moderating, searching, etc. They all create new data that is saved in the database, some temporarily and some permanently.
At which point should the blockchain be updated? And why compare it with previous backup? What are you expecting it to tell you?
(Score: 0) by Anonymous Coward on Thursday February 26, @11:17PM
(5 children)
by Anonymous Coward
on Thursday February 26, @11:17PM (#1435069)
Your questions would be an important part of the project management and development pipeline. Give me a call if you would like to hire a consultant.
The last question is the most important. It would tell an auditor when unwarranted modifications have been made. I thought that was clear from the beginning, but this thread has involved a lot off tangential and off topic nonsense due to, umm, something.
(Score: 2) by janrinok on Thursday February 26, @03:44PM (8 children)
Well that comes back to the trust issue. I do not use any other social media because I have seen how they change the rules at will and bury any information about the changes in very small print, if at all.
They will quite happily share my information (which is illegal in the EU without my express permission) because it is seen as having some monetary value.
If you mean what happens if the code that we are running is changed maliciously, then the blockchain idea might be useful as a flag, but then you would have to diff everything with a known good release and try to find what the changes are. But that makes the role of the administrator more important, not less. If someone has managed to get into your own code base and make changes to it then there is a permissions issue that is wrong. But using our own case as an example - they would have to know also how to build the entire site into containers, how to access the database itself, how to access the various servers that we use etc.
I agree.
[nostyle RIP 06 May 2025]
(Score: 0) by Anonymous Coward on Thursday February 26, @06:32PM (7 children)
Blockchain would make it simple to run a verification on the database. Every byte of content added creates a signature, so uf someone changes a few bytes then the signature changes. Your current situation would require a complete diff against a backup.
(Score: 3, Informative) by janrinok on Thursday February 26, @08:18PM (6 children)
The database is continually changing. There are internal tasks running all the time which leave results in the database. Records are created in the database when a users is accessing pages, making comments. creating journals, moderating, searching, etc. They all create new data that is saved in the database, some temporarily and some permanently.
At which point should the blockchain be updated? And why compare it with previous backup? What are you expecting it to tell you?
[nostyle RIP 06 May 2025]
(Score: 0) by Anonymous Coward on Thursday February 26, @11:17PM (5 children)
Your questions would be an important part of the project management and development pipeline. Give me a call if you would like to hire a consultant.
The last question is the most important. It would tell an auditor when unwarranted modifications have been made. I thought that was clear from the beginning, but this thread has involved a lot off tangential and off topic nonsense due to, umm, something.
(Score: 2) by janrinok on Friday February 27, @12:15AM (4 children)
A blockchain of the database would tell us no such thing. You would need a blockchain of the source code to identify changes to the source code.
What exactly are you trying to prove again?
This, I assume, is AC's little joke? What is your AC phone number, or your contact address? How exactly does one hire Mr Anonymous Coward?
[nostyle RIP 06 May 2025]
(Score: -1, Redundant) by Anonymous Coward on Friday February 27, @01:33AM (3 children)
Feel free to discuss with people you may actually listen to.