## page was renamed from Software/Projects/BirdShack
## page was renamed from Software/Porjects/BirdShack
## page was renamed from Software/BirdShack

 . '''NOTA BENE - WORK IN PROGRESS''' - [[Technology/Laboratory/Software/BirdShack#Inputs_&_Thoughts|Your Inputs & Thoughts]] :-)

 . '''To Technology''' '''[[Technology#Technology_Laboratory| Laboratory]]''' - '''To Technology ''' '''[[Technology/Laboratory| Laboratory - Overview Projects]]'''

----

== CAcert.org BirdShack Project ==
BirdShack Project is the Next-Generation Design of CAcert.org Open Source Software.  '''See [[Software#BirdShack]].'''

<<BR>>

----
== Inputs & Thoughts ==

 . 20091001-BernhardFröhlich

 . {{{

Requirements for Support Application

During several Arbitrations I noticed that there is some important information about a user's account which is not available by the support page, so it sometimes is necessary to "hijack" an account. IMHO the following information about an account should be available in addition to the information currently available:

* The list of domain names associated to an account
* The list of mail adresses associated to an account
* The list of certificates issued by an account (especially their expiring dates), maybe the non-expired ones are enough?
* Revocation of single certificates of an account
* Modification of the primary email address of an account. Of course this is a critical piece of data, since it is the only way to find an account. So there should be additional safeguards against accidential modification!
* Support should be able to see the time a notarisation was recorded (notary.when)
* Support should be able to modify the date a notarisation was done (notary.date)


Another thing that could be handy during Arbitrations would be the possibility to add and show (several) texts to an account, for example if an Arbitrator has issued a caution to the account's owner for some misbehavior.

Of course this is open to discussion.

  }}}

----

 . 20091110-BernhardFröhlich

 . {{{
Requested Features for Organisation Admin Interface

* Create client certificate from CSR. IMHO this is essential to work with Org-client certificates in real life.
* Associate an existing CAcert account with the Organisation. This should allow the other account to add the Org's name and maybe a OrgUnit to requested client certificates. Nice to have.

  }}}

----

 . YYYYMMDD-YourName

 . {{{
Text / Your Statements, thoughts and e-mail snippets, Please
  }}}

----
<<BR>>
'''Category''' or '''Categories'''<<BR>>

CategorySoftware<<BR>>
CategoryAudit