[WMS-114] Purger still uses 512bits in an hard-coded routine which update wms's proxy Created: 16/Jan/14  Updated: 16/Jan/14  Resolved: 16/Jan/14

Status: Resolved
Project: WMS
Component/s: None
Affects Version/s: 3.6.2 WMS Server
Fix Version/s: 3.6.3 WMS Server
Security Level: Public (Visbile by non-authn users.)

Type: Bug Priority: Major
Reporter: Alvise Dorigo Assignee: Alvise Dorigo
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

https://ggus.eu/ws/ticket_info.php?ticket=100237



 Comments   
Comment by Alvise Dorigo [ 16/Jan/14 ]

The fix has just been made on the org.glite.wms/org.glite.wms.purger/src/ssl_utils.cpp, by substituting the 512 by the 1024 in the proxy_init() function.

Reproducing the problem is a little bit tricky; you need to disable the cron which periodically updates the WMS's proxy: /etc/cron.d/glite-wms-create-host-proxy.cron.
When disabled the cron, during a normal functioning of the WMS (submissions, cancel, output-retrieval) another WMS's mechanism occurs (which doesn't normally do anything if the cron is enabled): a routine in the purger (ssl_utils.cpp:proxy_init()) is invoked, and it has (in the current version of WMS) the number of 512bit for the proxy generation hard-coded.

After upgrading the rpm glite-wms-purger (which also contains another fix to WMS-113 again related to this problem of 512bits), if you disable the cron, the purger will take care of wms.proxy's update, now with 1024 bit, as needed.

Generated at Thu Apr 25 01:29:20 CEST 2024 using Jira 9.12.5#9120005-sha1:fa8821cdb090f6b5ec0424ddb13fa19bc92d8429.