Difference: VomsTestsP3142 (1 vs. 18)

Revision 182010-04-13 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 105 to 105
 
  • BUG #60912: "VOMS Java API: not possible to create a VOMSTrustManager without the /etc/grid-security/certificates directory" FIXED in the source CODE
  • BUG #63714: "Add support for Issuing Distribution Point CRL extension to the Java APIs" FIXED see GGUS ticket
  • BUG #63928: "_VOMS Java API: VOMSKeyManager_ constructor fails"FIXED in the source CODE
Added:
>
>
  • BUG #65129: "VOMS: threading problems in the vomsdata class" FIXED in the source CODE
  • BUG #64632: "voms-proxy-init occationally fails due to an uninitialized variable (ctx.db_meth)" FIXED
  -- ElisabettaMolinari - 21 Oct 2009

Revision 172010-03-18 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 99 to 99
 
  • BUG #57473: "Email and emailAddress in LSC files not equivalent" FIXED
  • BUG #58515: "The VOMS Java APIs fail when email is present in the server certificate" FIXED
Changed:
<
<
  • BUG #60394: "VOMS: memory leak in fs.c:fileoutputter()"
>
>
  • BUG #60394: "VOMS: memory leak in fs.c:fileoutputter()"FIXED
    • tested submittting a thread of 100000 voms-proxy-init in sequentially
 
  • BUG #60908: "VOMS Java API: VOMSTrustManager.getAcceptedIssuers() is completely wrong!" FIXED in the source code
  • BUG #60912: "VOMS Java API: not possible to create a VOMSTrustManager without the /etc/grid-security/certificates directory" FIXED in the source CODE
  • BUG #63714: "Add support for Issuing Distribution Point CRL extension to the Java APIs" FIXED see GGUS ticket

Revision 162010-03-17 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 94 to 94
 
  • BUG #53450: "voms-proxy-init 1.8.8 fails silently on bad vomses file" FIXED

New Bugs:

Changed:
<
<
  • BUG #53527: "org.glite.security.voms using wrong libdir setting after ETICS ${libdir} fix"
>
>
  • BUG #53527: "org.glite.security.voms using wrong libdir setting after ETICS ${libdir} fix" FIXED
 
  • BUG #56687: "VOMS Java API: org.glite.voms.PKIStore doesn't referesh after fetch-crl update" FIXED in the source CODE
  • BUG #57473: "Email and emailAddress in LSC files not equivalent" FIXED

Revision 152010-03-17 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 95 to 95
 

New Bugs:

  • BUG #53527: "org.glite.security.voms using wrong libdir setting after ETICS ${libdir} fix"
Changed:
<
<
  • BUG #56687: "VOMS Java API: org.glite.voms.PKIStore doesn't referesh after fetch-crl update"
  • BUG #57473: "Email and emailAddress in LSC files not equivalent"
  • BUG #58515: "The VOMS Java APIs fail when email is present in the server certificate"
>
>
  • BUG #56687: "VOMS Java API: org.glite.voms.PKIStore doesn't referesh after fetch-crl update" FIXED in the source CODE
  • BUG #57473: "Email and emailAddress in LSC files not equivalent" FIXED
  • BUG #58515: "The VOMS Java APIs fail when email is present in the server certificate" FIXED
 
  • BUG #60394: "VOMS: memory leak in fs.c:fileoutputter()"
Changed:
<
<
  • BUG #60908: "VOMS Java API: VOMSTrustManager.getAcceptedIssuers() is completely wrong!"
  • BUG #60912: "VOMS Java API: not possible to create a VOMSTrustManager without the /etc/grid-security/certificates directory"
  • BUG #63714: "Add support for Issuing Distribution Point CRL extension to the Java APIs"
  • BUG #63928: "_VOMS Java API: VOMSKeyManager_ constructor fails"
>
>
  • BUG #60908: "VOMS Java API: VOMSTrustManager.getAcceptedIssuers() is completely wrong!" FIXED in the source code
  • BUG #60912: "VOMS Java API: not possible to create a VOMSTrustManager without the /etc/grid-security/certificates directory" FIXED in the source CODE
  • BUG #63714: "Add support for Issuing Distribution Point CRL extension to the Java APIs" FIXED see GGUS ticket
  • BUG #63928: "_VOMS Java API: VOMSKeyManager_ constructor fails"FIXED in the source CODE
  -- ElisabettaMolinari - 21 Oct 2009

Revision 142010-03-15 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 101 to 101
 
  • BUG #60394: "VOMS: memory leak in fs.c:fileoutputter()"
  • BUG #60908: "VOMS Java API: VOMSTrustManager.getAcceptedIssuers() is completely wrong!"
  • BUG #60912: "VOMS Java API: not possible to create a VOMSTrustManager without the /etc/grid-security/certificates directory"
Changed:
<
<
  • #63714: "Add support for Issuing Distribution Point CRL extension to the Java APIs"
  • #63928: "_VOMS Java API: VOMSKeyManager_ constructor fails"
>
>
  • BUG #63714: "Add support for Issuing Distribution Point CRL extension to the Java APIs"
  • BUG #63928: "_VOMS Java API: VOMSKeyManager_ constructor fails"
  -- ElisabettaMolinari - 21 Oct 2009

Revision 132010-03-15 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 95 to 95
 

New Bugs:

  • BUG #53527: "org.glite.security.voms using wrong libdir setting after ETICS ${libdir} fix"
Changed:
<
<
  • BUG #56687: "VOMS Java API: org.glite.voms.PKIStore doesn't referesh after fetch-crl update"
>
>
  • BUG #56687: "VOMS Java API: org.glite.voms.PKIStore doesn't referesh after fetch-crl update"
 
  • BUG #57473: "Email and emailAddress in LSC files not equivalent"
  • BUG #58515: "The VOMS Java APIs fail when email is present in the server certificate"
Changed:
<
<
>
>
  • BUG #60394: "VOMS: memory leak in fs.c:fileoutputter()"
  • BUG #60908: "VOMS Java API: VOMSTrustManager.getAcceptedIssuers() is completely wrong!"
  • BUG #60912: "VOMS Java API: not possible to create a VOMSTrustManager without the /etc/grid-security/certificates directory"
  • #63714: "Add support for Issuing Distribution Point CRL extension to the Java APIs"
  • #63928: "_VOMS Java API: VOMSKeyManager_ constructor fails"
  -- ElisabettaMolinari - 21 Oct 2009

Revision 122010-03-12 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 93 to 93
 03D95CC3B5504696A1EB8EFF5995B334
  • BUG #53450: "voms-proxy-init 1.8.8 fails silently on bad vomses file" FIXED

Added:
>
>

New Bugs:

  • BUG #53527: "org.glite.security.voms using wrong libdir setting after ETICS ${libdir} fix"
  • BUG #56687: "VOMS Java API: org.glite.voms.PKIStore doesn't referesh after fetch-crl update"
  • BUG #57473: "Email and emailAddress in LSC files not equivalent"
  • BUG #58515: "The VOMS Java APIs fail when email is present in the server certificate"

 -- ElisabettaMolinari - 21 Oct 2009

Revision 112009-11-17 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 8 to 8
 of returning a valid AC for the user.
  • BUG #18371: "voms-proxy-init giving unclear message: GGUS-Ticket-ID: #10466"FIXED
    • tested by issuing a voms-proxy-init with no file under $HOME/.glite/vomses and the message cannot find file is returned only if the '--debug' option is enabled
Changed:
<
<
  • BUG #19217: "voms-proxy-init fails to report bad permissions: GGUS-ID 8871"
>
>
  • BUG #19217: "voms-proxy-init fails to report bad permissions: GGUS-ID 8871" FIXED
 
  • BUG #33326: "VOMS: voms-proxy-fake multi-VO support" FIXED
    • tested with the following file:
       cat vo_fake_test
      [sa3test]
Line: 44 to 44
 
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning" FIXED
  • BUG #39642: "Man page for voms-proxy-init contains EDG bugzilla." FIXED
    • Checked with 'man voms-proxy-init | grep -i edg'
Changed:
<
<
  • BUG #42919: "Cannot find file or dir: /afs/cern.ch/user/a/anduaga/.glite/vomses"
>
>
  • BUG #42919: "Cannot find file or dir: /afs/cern.ch/user/a/anduaga/.glite/vomses" HOPEFULLY FIXED
 
  • BUG #43942: "voms-proxy-info error for non standard location of CA files" FIXED
    • tested by doing the following:
      • create a proxy by using 'voms-proxy-init'
Line: 64 to 64
 0 voms-proxy-info -exists -bits 1050 ;echo $?
Changed:
<
<
  • BUG #45318: "gLite CE submission with RFC proxy chain failed"
>
>
  • BUG #45318: "gLite CE submission with RFC proxy chain failed" FIXED
    • tested by doing the following:
      • create a rfc proxy as in:
         voms-proxy-init -rfc -vomses .glite/vomses/sa3test-cert-10.cnaf.infn.it --voms sa3test
      • try a globus job run on a classic CE as in:
        globus-job-run t2-ce-01.mi.infn.it /bin/date
        Tue Nov 17 15:52:38 CET 2009
 
  • BUG #46132: "[VOMS] bad warnings and errors from voms-proxy-init" FIXED
    • tested using VO 'sa3test' by doing the following:
      • remove voms certificate from the '/etc/grid-security/vomsdir/' and remove the .lsc file from /etc/grid-security/vomsdir/sa3test/

Revision 102009-11-16 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 41 to 41
 uri :
  • BUG #34705: "Clarify the user of option --hours in the documentation Softwareversion: glite 3.1, voms-proxy-init 1.7.22" FIXED
  • BUG #35346: "voms-proxy-init hangs on receiving data from VOMS server" HOPEFULLY FIXED
Changed:
<
<
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
>
>
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning" FIXED
 
  • BUG #39642: "Man page for voms-proxy-init contains EDG bugzilla." FIXED
    • Checked with 'man voms-proxy-init | grep -i edg'
  • BUG #42919: "Cannot find file or dir: /afs/cern.ch/user/a/anduaga/.glite/vomses"

Revision 92009-11-09 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 40 to 40
 timeleft : 6:59:54 uri :
  • BUG #34705: "Clarify the user of option --hours in the documentation Softwareversion: glite 3.1, voms-proxy-init 1.7.22" FIXED
Changed:
<
<
  • BUG #35346: "voms-proxy-init hangs on receiving data from VOMS server"
>
>
  • BUG #35346: "voms-proxy-init hangs on receiving data from VOMS server" HOPEFULLY FIXED
 
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
  • BUG #39642: "Man page for voms-proxy-init contains EDG bugzilla." FIXED
    • Checked with 'man voms-proxy-init | grep -i edg'

Revision 82009-11-06 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED

Revision 72009-11-05 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 76 to 76
 
    • tested by:
       openssl x509 -text -noout -in /tmp/x509up_u0 | grep "Signature Algorithm"
              Signature Algorithm: sha1WithRSAEncryption
          Signature Algorithm: sha1WithRSAEncryption
Deleted:
<
<
  • BUG #49119: "VOMS Java API jar should follow glite package name conventions"
 
  • BUG #49614: "[voms-proxy-info] Voms proxy info -acexists flag broken?" FIXED
    • tested by doing the following:
      • create a proxy for the VO 'sa3test
      • check the following:
        voms-proxy-info -acexists sa3test; echo $?;
        0
        voms-proxy-info -acexists dummy; echo $?;
        1
Changed:
<
<
  • BUG #52394: "VOMS 1.9.x clients fail to compile when configured with --with-globus-flavor option"
  • BUG #52661: "Proxy generated by voms-proxy-init share the same serial number"
>
>
  • BUG #52394: "VOMS 1.9.x clients fail to compile when configured with --with-globus-flavor option" HOPEFULLY FIXED
  • BUG #52661: "Proxy generated by voms-proxy-init share the same serial number" FIXED
    • create two proxies for the same user
    • compare the serial numbers using the option '-serial' to the 'voms-proxy-info' command, such as:
      voms-proxy-info -serial
      03D95CC3B5504696A1EB8EFF5995B334
 
  • BUG #53450: "voms-proxy-init 1.8.8 fails silently on bad vomses file" FIXED

-- ElisabettaMolinari - 21 Oct 2009

Revision 62009-11-05 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 6 to 6
  None of the contacted servers for sa3test were capable of returning a valid AC for the user.
Deleted:
<
<
  • BUG #18367: "ambiguous error message from voms-proxy-init"
 
  • BUG #18371: "voms-proxy-init giving unclear message: GGUS-Ticket-ID: #10466"FIXED
    • tested by issuing a voms-proxy-init with no file under $HOME/.glite/vomses and the message cannot find file is returned only if the '--debug' option is enabled
  • BUG #19217: "voms-proxy-init fails to report bad permissions: GGUS-ID 8871"
Changed:
<
<
  • BUG #33326: "VOMS: voms-proxy-fake multi-VO support"
>
>
  • BUG #33326: "VOMS: voms-proxy-fake multi-VO support" FIXED
    • tested with the following file:
       cat vo_fake_test
      [sa3test]
      -vomslife = 10
      -hostcert = hostcert.pem
      -hostkey = hostkey.pem
      [vomstest]
      -vomslife = 7
      -hostcert = hostcert.pem
      -hostkey = hostkey.pem
    • it correctly generates the proxy:
      voms-proxy-info -all
      subject   : /C=IT/O=INFN/OU=Host/L=CNAF/CN=cert-10.cnaf.infn.it/CN=proxy
      issuer    : /C=IT/O=INFN/OU=Host/L=CNAF/CN=cert-10.cnaf.infn.it
      identity  : /C=IT/O=INFN/OU=Host/L=CNAF/CN=cert-10.cnaf.infn.it
      type      : proxy
      strength  : 1024 bits
      path      : /tmp/x509up_u0
      timeleft  : 11:59:54
      === VO sa3test extension information ===
      VO        : sa3test
      subject   : /C=IT/O=INFN/OU=Host/L=CNAF/CN=cert-10.cnaf.infn.it
      issuer    : /C=IT/O=INFN/OU=Host/L=CNAF/CN=cert-10.cnaf.infn.it
      timeleft  : 9:59:54
      uri       :
      === VO vomstest extension information ===
      VO        : vomstest
      subject   : /C=IT/O=INFN/OU=Host/L=CNAF/CN=cert-10.cnaf.infn.it
      issuer    : /C=IT/O=INFN/OU=Host/L=CNAF/CN=cert-10.cnaf.infn.it
      timeleft  : 6:59:54
      uri       :
 
  • BUG #34705: "Clarify the user of option --hours in the documentation Softwareversion: glite 3.1, voms-proxy-init 1.7.22" FIXED
  • BUG #35346: "voms-proxy-init hangs on receiving data from VOMS server"
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
  • BUG #39642: "Man page for voms-proxy-init contains EDG bugzilla." FIXED
    • Checked with 'man voms-proxy-init | grep -i edg'
  • BUG #42919: "Cannot find file or dir: /afs/cern.ch/user/a/anduaga/.glite/vomses"
Deleted:
<
<
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
 
  • BUG #43942: "voms-proxy-info error for non standard location of CA files" FIXED
    • tested by doing the following:
      • create a proxy by using 'voms-proxy-init'
Line: 58 to 85
 1
  • BUG #52394: "VOMS 1.9.x clients fail to compile when configured with --with-globus-flavor option"
  • BUG #52661: "Proxy generated by voms-proxy-init share the same serial number"
Changed:
<
<
  • BUG #53450: "voms-proxy-init 1.8.8 fails silently on bad vomses file"
>
>
  • BUG #53450: "voms-proxy-init 1.8.8 fails silently on bad vomses file" FIXED
  -- ElisabettaMolinari - 21 Oct 2009

Revision 52009-11-04 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 11 to 11
 
    • tested by issuing a voms-proxy-init with no file under $HOME/.glite/vomses and the message cannot find file is returned only if the '--debug' option is enabled
  • BUG #19217: "voms-proxy-init fails to report bad permissions: GGUS-ID 8871"
  • BUG #33326: "VOMS: voms-proxy-fake multi-VO support"
Changed:
<
<
  • BUG #34705: "Clarify the user of option --hours in the documentation Softwareversion: glite 3.1, voms-proxy-init 1.7.22"
>
>
  • BUG #34705: "Clarify the user of option --hours in the documentation Softwareversion: glite 3.1, voms-proxy-init 1.7.22" FIXED
 
  • BUG #35346: "voms-proxy-init hangs on receiving data from VOMS server"
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
  • BUG #39642: "Man page for voms-proxy-init contains EDG bugzilla." FIXED

Revision 42009-10-27 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 27 to 27
 unable to access trusted certificates in:x509_cert_dir=/etc/grid-security/certificates Function: proxy_init_cred

Changed:
<
<
  • BUG #45146: "voms options (-quiet, -bits, -valid) and man page don't match."
>
>
  • BUG #45146: "voms options (-quiet, -bits, -valid) and man page don't match." FIXED
    • Except for the '-quiet' option that is still there (see comment in the bug), the other options work, see the following:
 voms-proxy-info -exists -valid 23:00 ;echo $?
1
voms-proxy-info -exists -valid 1:00 ;echo $?
0
 voms-proxy-info -exists -bits 32 ;echo $?
0
voms-proxy-info -exists -bits 1050 ;echo $?
 
  • BUG #45318: "gLite CE submission with RFC proxy chain failed"
Changed:
<
<
  • BUG #46132: "[VOMS] bad warnings and errors from voms-proxy-init"
  • BUG #46382: "There is a vulnerability issue concerning VOMS"
>
>
  • BUG #46132: "[VOMS] bad warnings and errors from voms-proxy-init" FIXED
    • tested using VO 'sa3test' by doing the following:
      • remove voms certificate from the '/etc/grid-security/vomsdir/' and remove the .lsc file from /etc/grid-security/vomsdir/sa3test/
      • issue a 'voms-proxy-init -voms sa3test', the following is returned:
        Error: verify failed.
        Cannot verify AC signature!
      • issue a 'voms-proxy-info' it should return anything <> 0, such as for ex.
        echo $? 127

  • BUG #46382: "There is a vulnerability issue concerning VOMS" FIXED
    • tested by:
       openssl x509 -text -noout -in /tmp/x509up_u0 | grep "Signature Algorithm"
              Signature Algorithm: sha1WithRSAEncryption
          Signature Algorithm: sha1WithRSAEncryption
 
  • BUG #49119: "VOMS Java API jar should follow glite package name conventions"
Changed:
<
<
  • BUG #49614: "[voms-proxy-info] Voms proxy info -acexists flag broken?"
>
>
  • BUG #49614: "[voms-proxy-info] Voms proxy info -acexists flag broken?" FIXED
    • tested by doing the following:
      • create a proxy for the VO 'sa3test
      • check the following:
        voms-proxy-info -acexists sa3test; echo $?;
        0
        voms-proxy-info -acexists dummy; echo $?;
        1
 
  • BUG #52394: "VOMS 1.9.x clients fail to compile when configured with --with-globus-flavor option"
  • BUG #52661: "Proxy generated by voms-proxy-init share the same serial number"
  • BUG #53450: "voms-proxy-init 1.8.8 fails silently on bad vomses file"

Revision 32009-10-23 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
Line: 18 to 18
 
    • Checked with 'man voms-proxy-init | grep -i edg'
  • BUG #42919: "Cannot find file or dir: /afs/cern.ch/user/a/anduaga/.glite/vomses"
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
Changed:
<
<
  • BUG #43942: "voms-proxy-info error for non standard location of CA files"
>
>
  • BUG #43942: "voms-proxy-info error for non standard location of CA files" FIXED
    • tested by doing the following:
      • create a proxy by using 'voms-proxy-init'
      • move the '/etc/grid-security/certificates' dir under $HOME/
      • do not define the env variable X509_CERT_DIR
      • try a 'voms-proxy-info', it should return the following
         voms-proxy-info -all
        unable to access trusted certificates in:x509_cert_dir=/etc/grid-security/certificates
        Function: proxy_init_cred

 
  • BUG #45146: "voms options (-quiet, -bits, -valid) and man page don't match."
  • BUG #45318: "gLite CE submission with RFC proxy chain failed"
  • BUG #46132: "[VOMS] bad warnings and errors from voms-proxy-init"

Revision 22009-10-23 - ElisabettaMolinari

Line: 1 to 1
 

Check Bugs:

Changed:
<
<
  • BUG #12578: "Error message mentions certificate when it means proxy"
>
>
  • BUG #12578: "Error message mentions certificate when it means proxy" FIXED
    • Tested with an expired proxy certificate and the following was returned:
      Error: Error during SSL handshake:Either proxy or user certificate are expired.
       
      None of the contacted servers for sa3test were capable
      of returning a valid AC for the user.
 
  • BUG #18367: "ambiguous error message from voms-proxy-init"
Changed:
<
<
  • BUG #18371: "voms-proxy-init giving unclear message: GGUS-Ticket-ID: #10466"
>
>
  • BUG #18371: "voms-proxy-init giving unclear message: GGUS-Ticket-ID: #10466"FIXED
    • tested by issuing a voms-proxy-init with no file under $HOME/.glite/vomses and the message cannot find file is returned only if the '--debug' option is enabled
 
  • BUG #19217: "voms-proxy-init fails to report bad permissions: GGUS-ID 8871"
  • BUG #33326: "VOMS: voms-proxy-fake multi-VO support"
  • BUG #34705: "Clarify the user of option --hours in the documentation Softwareversion: glite 3.1, voms-proxy-init 1.7.22"

Revision 12009-10-21 - ElisabettaMolinari

Line: 1 to 1
Added:
>
>

Check Bugs:

  • BUG #12578: "Error message mentions certificate when it means proxy"
  • BUG #18367: "ambiguous error message from voms-proxy-init"
  • BUG #18371: "voms-proxy-init giving unclear message: GGUS-Ticket-ID: #10466"
  • BUG #19217: "voms-proxy-init fails to report bad permissions: GGUS-ID 8871"
  • BUG #33326: "VOMS: voms-proxy-fake multi-VO support"
  • BUG #34705: "Clarify the user of option --hours in the documentation Softwareversion: glite 3.1, voms-proxy-init 1.7.22"
  • BUG #35346: "voms-proxy-init hangs on receiving data from VOMS server"
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
  • BUG #39642: "Man page for voms-proxy-init contains EDG bugzilla." FIXED
    • Checked with 'man voms-proxy-init | grep -i edg'
  • BUG #42919: "Cannot find file or dir: /afs/cern.ch/user/a/anduaga/.glite/vomses"
  • BUG #35535: "voms-proxy-init 1.8.3 gives confusing warning"
  • BUG #43942: "voms-proxy-info error for non standard location of CA files"
  • BUG #45146: "voms options (-quiet, -bits, -valid) and man page don't match."
  • BUG #45318: "gLite CE submission with RFC proxy chain failed"
  • BUG #46132: "[VOMS] bad warnings and errors from voms-proxy-init"
  • BUG #46382: "There is a vulnerability issue concerning VOMS"
  • BUG #49119: "VOMS Java API jar should follow glite package name conventions"
  • BUG #49614: "[voms-proxy-info] Voms proxy info -acexists flag broken?"
  • BUG #52394: "VOMS 1.9.x clients fail to compile when configured with --with-globus-flavor option"
  • BUG #52661: "Proxy generated by voms-proxy-init share the same serial number"
  • BUG #53450: "voms-proxy-init 1.8.8 fails silently on bad vomses file"

-- ElisabettaMolinari - 21 Oct 2009

 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback