VOMS Development

Detailed list of version-by-version changes:

VOMS Core

• bug: #xxxxx Added support for generic attributes
• bug: #xxxxx New C/C++ API libraries that do not depend on Globus
• bug: #xxxxx Integration of Java APIs in the main package (JNI version)
• bug: #xxxxx Fix problem with UID/USERID in CA names (reported by GIN)
• bug: #16576 voms-proxy-init failure leaves tmp_x509up_u$(id -u)_$$ file on failure without a debugging wish from the user
• bug: #15436 [ VOMS ] voms-proxy-init execution errors: default vomses file and --vomses option
• bug: #15572 [VOMS] Invalid use of '~' in looking for vomses directory
• bug: #12514 Specifying multiple roles
• bug: #10967 (java part. C and C++ were already fixed) \ GSVG: look yourself
• bug: #14026 (Easier configuration for clients) /

1.7.1

• bug: #17748 Incorrect proxy format for GT 4
• bug: #17747 Errors in DB Access

1.7.2

• bug: #17747 Errors in DB Access (previous fix was incomplete)

1.7.3

• bug: #17831 voms-proxy-init doesn't work with single quote in DN

1.7.4:

• bug: #xxxxx Solves general case of bug #17831

1.7.5:

• bug: #17747 again!

1.7.6:

• Not existant

1.7.7:

• bug: #xxxxx Rewrites Java APIs to a pure java implementation

1.7.8:

• bug: #19349 voms start script for a vo kills other vos
• bug: #19230 voms-proxy-init --valid 168:00 result not clearly explained situation
• bug: #19217 voms-proxy-init fails to report bad permissions: GGUS-ID 8871
• bug: #19145 voms-proxy-* commands should be able to use p12 formatted certificate
• bug: #18371 voms-proxy-init giving unclear message: GGUS-Ticket-ID: #10466
• bug: #18367 ambiguous error message from voms-proxy-init
• bug: #17863 voms-proxy-info man page and -help inconsistency
• bug: #17362 voms-proxy-fake uses the holder's cert to sign the AC
• bug: #16540 voms-proxy-init -hours and -valid difference
• bug: #15794 voms and voms-admin status script return value incorrect
• bug: #15238 [VOMS] init script start function is unclear or incorrect
• bug: #15239 [VOMS] init script displays incomplete usage
• bug: #15700 [VOMS] Apparent bug in open() of fifo
• bug: #13675 voms-proxy-init doesn't complain about wrong parameters or junk in the command line, just silently fails
• bug: #10830 output of voms-proxy-init --help misleading
• bug: #10035 voms_install_replica.sgml problem
• bug: #11335 (GGUS) Globus vulnerabilities

1.7.9:

• bug: #17750 voms core logs: give explicit reason when proxy refused due to invalid crl or other problem with user's CA.
• bug: #xxxxx startup script handles missing parameter in voms.conf
• bug: #xxxxx some logging corrections

1.7.10

• bug: #21033 Signing policy verifies first tripplet with matching access_id_CA in policy files only.
• bug: #20984 Ip address information in logs when a proxy is requested in VOMS Server
• bug: #20508 simplified Java VOMS API
• bug: #20502 A memory leak in vomsdata::Retrieve()

1.7.11

• internal

1.7.12

• bug: #20805 voms-proxy-info showing the delegation chain
• bug: #xxxxx Fixed compatibilty problem with Java 1.5 in java APIs
• bug: #xxxxx Accepted patch from Jim Basney for GT4 compatibilty
• bug: #xxxxx Corrected typos in replica script

1.7.13

• bug: #xxxxx Fixed security vulnerability in vomsd.

1.7.14:

• bug: #20879 VOMS authenticates by issuer name

1.7.15:

• bug: #22832 Proxy renewal doesn't work
• bug: #14026 VOMS clients to be configured with the trusted certificate subjects, not the whole certificate
• bug: #xxxxx Integration in the Java API of the capability to create proxies
• bug: #xxxxx Fixed 64bit compilation problem

1.7.16:

• bug: #24294 Unharmonized indexing of voms_api.c/h interface
• bug: #24373 Exit codes for voms-proxy-init no unique

1.7.17:

• bug: #24556 Seg fault in voms-proxy-info

1.7.18:

• bug #26260: VOMS reorders certificates in proxy when MyProxy proxy certificate is used
• bug #26672: VOMS Java API: Not able to specify the location of user credentials

1.7.19:

• Internal revisions. disregard

1.7.20:

• bug: #26395 VOMS server 1.7.* fails to handle an AC request with more than a few FQAN
• bug: #27546 voms-proxy-init adding extended attributes multiple times
• bug: #26866 Globus initialization within VOMS API
• bug: #26804 [VOMS 1.7.16-2] voms-proxy-init fails on some x86 platforms
• bug: #26870 [VOMS 1.7.16-2] voms-proxy-init segfaults on x86 RHEL 4 (different than 26803)
• bug: #26803 [VOMS 1.7.16-2] voms-proxy-init segfaults on x86-64 RHEL 4
• bug: #26602 Apparently uninitalised 'it' element in VOMS initEx(), for sl4 (vdt 1.6) build

1.7.21:

• bug: #15436 [ VOMS ] voms-proxy-init execution errors: default vomses file and --vomses option
• bug: #23010 [ VOMS ] Certain options of the voms-proxy-* commands do not have the expected effect
• bug: #25887 name of p12 credential differs from that used by globus
• bug: #23905 [ VOMS ] voms-proxy-init -list without voms specified neither creates proxy nor lists attributes
• bug: #25242 [ voms-proxy-init ] command options should return 0 exit code in case of success
• bug: #23902 [ VOMS ] voms-proxy-info -vo should return non-zero exit code for proxy with no VOMS extension
• bug: #22270 voms-proxy-init problems

1.7.22:

• bug: #xxxxx Fixed problem with French CA

1.7.23:

• bug #28740: [VOMS 1.7.20-1] voms-proxy-info has a bus error on Mac OS X 10.4 (Akos, this is the closedir() bug you are interested into)
• bug #29656: Incorrect treatment of VO nicks in vomses by VOMS 1.7 client
• Plus all the short term fixes from the review. A note about this: The option to compile only the java APIs is called '--with-java-only' This means that is possible to compile the -api-java configuration (not the CVS module) without compiling the main module. This is not done yet, but a _2 of that module may follow, or it may be done for 1.8.0

1.7.24:

• bug #28740: Really fixed it this time.

1.8.0:

• bug #31191: VOMS build errors on SL5
• bug #30454: VOMS libraries doesn't use symlink
• bug #28753: [VOMS 1.7.20-1] strange time offset on Mac OS X 10.4
• bug #27496: A new voms's API is needed
• bug #27431: [VOMS] 64 bit compatibility issue: comparison is always true due to limited range of data type
• bug #26832: VOMS incorrectly checks ownership of vomses file
• bug #23291: [ VOMS ] voms-proxy-info fails to analyse voms-proxy-fake proxy
• bug #15023: VOMS: bad oracle performance caused by storing AC SN in database
• bug #10729: VOMS API should return clean FQAN
• bug #22437: Problems with voms validation at tomcat startup
• Implemented first step of globus independence plan
• Integrated patch for MacOSX compilation
• Integrated patch for OpenSSL 0.9.8 compilation

1.8.1:

• bug #32310: VOMS: Segfault while processing signing_policy file
• bug #31800: voms-proxy-info returns 1 in v1.8.0
• bug #32353: VOMS Server error when trying to create a proxy
• bug #32147: Include voms-ping and voms-admin-ping in the packaging (partial: voms-ping is included)
• bug #xxxxx: removed segfault in oracle interface following problems in communication with the DB.

1.8.2:

• bug #31476: voms stops adding entries in log file
• bug #32689: Problem validating Short lived certificates with the new org.glite.voms package
• bug #32694: VOMS on MySQL loses FQANs
• bug #32262: [voms-1.7.22] Regular crashes! (this turned out to be a duplicate of bug #31476)

1.8.3:

• bug #31476: voms stops adding entries in log file (really, this time) (tracked)
• bug #33259: VOMS-CORE: misleading error message displayed by voms-proxy-init
• bug #33212: VOMS-CORE: missing user-level attribute value in the proxy

1.8.4:

• bug #33902: VOMS MySQL replication: adapt for 2.x schema, add encryption
• bug #35569: glite-security-voms-api-noglobus-1.8.3-3 and glite-security-voms-api-cpp-1.8.3-3 contain the same files
• bug #36502: voms-proxy-info shouldn't require AC check in all cases
• bug #36092: [VOMS 1.8.3] VOMS server log file created with bizarre permissions
• bug #36573: voms-proxy-info has bad return codes
• bug #37008: VOMS server is always returning a short FQAN
• bug #37071: VOMS api should specify in error cases whether the voms AC is expired or not yet valid.
• bug #37704: There is a possible vulnerability concerning proxies
• bug #38506: Previous Predictable Order with --voms flags was lost.
• bug #38824: VOMS doesn't build with VDT globus 1.10.1-1 because it uses system OpenSSL

VOMS Admin

• Voms-Admin server NEWS: NEWS and CHANGES in voms-admin server 1.2.19

-- AndreaCeccanti - 26 Oct 2006