You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the current method of sending credentials from GlideinWMS Frontends to GlideinWMS Factories is secure, there is an opportunity to further enhance our security measures. Currently, the frontend pickles the credentials before sending them, and they are encrypted. Unpickling them on the Factory side could present a potential risk if the encryption key were ever compromised.
Details:
Current Method: The frontend pickles the credentials before sending them.
Security Measures: The credentials are encrypted, making the current implementation safe for production use.
Potential Risk: In the unlikely event that the encryption key is compromised, unpickling credentials could pose a security risk.
Recommendation:
Even though the current implementation with pickling and encryption is secure, we recommend exploring alternative serialization methods or additional safeguards during unpickling to further fortify our security.
The text was updated successfully, but these errors were encountered:
While the current method of sending credentials from GlideinWMS Frontends to GlideinWMS Factories is secure, there is an opportunity to further enhance our security measures. Currently, the frontend pickles the credentials before sending them, and they are encrypted. Unpickling them on the Factory side could present a potential risk if the encryption key were ever compromised.
Details:
Recommendation:
Even though the current implementation with pickling and encryption is secure, we recommend exploring alternative serialization methods or additional safeguards during unpickling to further fortify our security.
The text was updated successfully, but these errors were encountered: