• Case Number: a20120304.1
• Status: running

• Claimants: <anonymized>

• Respondents: CAcert

• Case Manager: BernhardFröhlich

• Arbitrator: UlrichSchroeter

• Date of arbitration start: 2012-03-06
• Date of ruling: 201Y-MM-DD
• Case closed: 201Y-MM-DD
• Complaint: Account Removal
• Relief: TBD

Before: Arbitrator UlrichSchroeter (A), Respondent: CAcert (R), Claimant: <anonymized> (C), Case: a20120304.1

History Log

• 2012-03-04 (issue.c.o) case s20120304.54

• 2012-03-06 (A): added to wiki
• 2012-03-06 (A): I'll take this case as (A) and appoint (CM)
• 2012-03-06 (A): Intermediate ruling, sent to (Support) to lock account in question
• 2012-03-06 (Support): locked the acccount [s20120305.137]
• 2012-03-06 (A): initmailing + intermediate ruling notification sent to (C) with request for a statement by (C) regarding discrepancies in account data

Original Dispute, Discovery (Private Part) (optional)

• Link to Arbitration case a20120304.1 (Private Part)

EOT Private Part

Discovery

• Name mismatches between (C) and account name
• Potential Junior member case (to anonymize user data in arbitration case)
• 3 certs issued, revoked, latest expires Aug 2012, out of range for precedent case a20111128.3

Intermediate Ruling

• I hereby came to the following intermediate ruling:
  1. user data has to be anonymized in arbitration file: reason - potential Junior member
  2. Support should lock the account immediately to prevent further potential misusage

Frankfurt/Main, 2012-03-06

Discovery II

• Support reported that the account is now locked [s20120305.137]
• by issueing certificates, (C) is bound to the CAcert Community Agreement.
  • in (C)'s account 3 revoked client certificates are identified.
  • The latest expire date is 2012-08-31
  • This means, CCA termination cannot be given before latest expire date + 3 months, this is: 2012-11-30
• With the account infos given by Support
  • 0 assurance points, 3 client certs issued, revoked, latest expire 2012-08-31
  • the remaining lifetime before expire of the certs indicates, that the certificates have been created within the last few days (client certs valid for 6 months if user account has 0 assurance points)
  • expire date 2012-08-31 - 6 months = issue date around 2012-02-30 - 2012-03-01
• With these informations, I assume, that (C) created an account to test the certificate handling, created an pseudonymous account with a fake name and fake DoB.
• This indicates that this case probably may fall under CCA violation 2.3.1 and 2.3.2

  • CCA
    1.1 Agreement:
    agreement has been given by:
     * your request on the website to join the Community and create an
    account, 
     * your request for issuing of certificates
    
    2.1  Risks 
     3. You may find yourself subject to Arbitration (DRP => COD7)
    
    2.2  Liabilities
     1. You are liable for any penalties as awarded against you by the
    Arbitrator.
     2. Remedies are as defined in the DRP (COD7). An Arbitrator's ruling may
    include monetary amounts, awarded against you.
     3. Your liability is limited to a total maximum of 1000 Euros. 
    
    2.3  Obligations
    You are obliged
       1. to provide accurate information as part of Assurance. You give
    permission for verification of the information using CAcert-approved
    methods.
       2. to make no false representations. 

• If the account was created for testing purposes only, the CCA violation can be set into account, that (C) didn't tried to get assured

Ruling

Execution

Similiar Cases

---

• CategoryArbitration

• CategoryArbCaseAccountDelNonAssurer

• CategoryArbCaseCCAViolation

• CategoryArbCaseOthers

• CategoryArbCaseExternal