mei_rt2mei_rt2_fix_1
Last change
on this file since bde4e91 was
549656e,
checked in by Mei <mei@…>, 13 years ago
|
1) modify some doc files
|
-
Property mode set to
100644
|
File size:
1.2 KB
|
Line | |
---|
1 | |
---|
2 | ABAC 2.1.0 |
---|
3 | ---------- |
---|
4 | - libcreddy has been merged into libabac and creddy |
---|
5 | id and attribute credential generations are invoking |
---|
6 | libabac to do the work |
---|
7 | - add a new '--subject-link' option to creddy --attribute |
---|
8 | to hold the linking role |
---|
9 | - add --dbdump option to abac_prover_yap to retrieve |
---|
10 | all prolog clauses stored in the db |
---|
11 | - updated to use strongswan 4.6.4 |
---|
12 | - There are occasional error messages originated |
---|
13 | from Strongswan during access of the attribute |
---|
14 | credentials, but ABAC is still working as it should. |
---|
15 | Those messages are due to libstrongswan not |
---|
16 | handling certain value of authorizedKeyIdentifier |
---|
17 | as expected even though it really should not need |
---|
18 | to process for it (it does not need it). |
---|
19 | |
---|
20 | Here are sample of messages coming through the |
---|
21 | stderr pipe, |
---|
22 | |
---|
23 | L6 - keyIdentifier: length of ASN.1 object invalid or too large |
---|
24 | L6 - authorityCertSerialNumber: length of ASN.1 object invalid or too large |
---|
25 | |
---|
26 | You might also see messages about authorityCertIssuer |
---|
27 | |
---|
28 | Do report to us if your ABAC is not behaving as |
---|
29 | expected and messages like above seem to be a factor.. |
---|
30 | |
---|
31 | ABAC 2.0.0 |
---|
32 | ---------- |
---|
33 | - libabac now can handle RT2 attribute rules |
---|
34 | with dynamic and static constraints |
---|
35 | |
---|
Note: See
TracBrowser
for help on using the repository browser.