Is the flyweight pattern a good security choice for managing permissions?
I’m designing a system, and it needs future expandability for the use of a permission system of some kind. I’m wondering if the flyweight pattern would be a good choice to implement this. I’m not responsible for the implementation right now, as it is just a prototype, and we’re not prototyping any parts that need the right system. However, because of the demand for future extensibility to parts that need permission management the interface needs to be solid. This means that in the end it will be a thought experiment, rather than a real part of what I have to work on. However, I do need to be able to explain and justify my design in this area of the application.
Enforcing manual inclusion of a specific header file (banned.h)
Banned.h is a list of ANSI C functions that Microsoft is trying to persuade programmers to deprecate. I already know how to enforce automatic inclusion of banned.h (such as the answer to Ensuring that headers are explicitly included in CPP file). Unfortunately, that answer has an important drawback.
Enforcing manual inclusion of a specific header file (banned.h)
Banned.h is a list of ANSI C functions that Microsoft is trying to persuade programmers to deprecate. I already know how to enforce automatic inclusion of banned.h (such as the answer to Ensuring that headers are explicitly included in CPP file). Unfortunately, that answer has an important drawback.
What is a simple, correct and secure way of executing code stored in database?, that is also sandboxed
Webhooks can be a very powerful thing when you try to automate or integrate software, however, handling their deployment in a controlled environment can suck in terms of security and deployment alone.
What is a simple, correct and secure way of executing code stored in database?, that is also sandboxed
Webhooks can be a very powerful thing when you try to automate or integrate software, however, handling their deployment in a controlled environment can suck in terms of security and deployment alone.
What is a simple, correct and secure way of executing code stored in database?, that is also sandboxed
Webhooks can be a very powerful thing when you try to automate or integrate software, however, handling their deployment in a controlled environment can suck in terms of security and deployment alone.
What is a simple, correct and secure way of executing code stored in database?, that is also sandboxed
Webhooks can be a very powerful thing when you try to automate or integrate software, however, handling their deployment in a controlled environment can suck in terms of security and deployment alone.
Is there any point in preventing developers from having a local copy of the database in their machine?
Is there any point to having a dedicated development database server(s) that all developers can use, i.e. they don’t have a local copy of the db in their machines. Quite clearly, this will slow down development but I’m curious whether anyone actually does this in the enterprise level. I know I should trust the devs we hire and I’m guessing this will mostly be the kind of answers that I will be getting but if anyone actually does this I would want to know if it’s even worth doing.