potiuk commented on PR #40775:
URL: https://github.com/apache/airflow/pull/40775#issuecomment-2237289386

   > On the other hand, I believe it might be possible to implement different 
levels of security or varying access permissions by roles for Connections as 
well.
   
   We have that already - read the Security Model. And those users are already 
highly trusted not to abuse some accidental capabilities of some particular 
drivers. But it's a different thing to give the option to freelly configure 
what will be installed in worker by just configuring connection. That opens 
really huge security attack vector.  Generally speaking "UI" access should be 
considered as potential gate which might allow entering Airflow backend and 
perform more sophisticated attacks.
   
   The code executed in workers by definition should be only controlled by DAG 
Authors and Deployment Managers (see the roles described in the security model).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to