X-Git-Url: http://wien.tomnetworks.com/gitweb/?a=blobdiff_plain;f=web%2Fmono-hacking-roadmap.html;h=134a1d425412fd51c2b2754a5c7beb949543d754;hb=4347c57e9783cf9348af2e0ec773024ab6d9b9fc;hp=9c822e915f57d9e1cd5b404160c169b7f0d86d70;hpb=06707a449b65e60c261902ee93a4add0861298fb;p=mono.git
diff --git a/web/mono-hacking-roadmap.html b/web/mono-hacking-roadmap.html
index 9c822e915f5..134a1d42541 100644
--- a/web/mono-hacking-roadmap.html
+++ b/web/mono-hacking-roadmap.html
@@ -129,9 +129,50 @@ vertical-align: top;
ECMA profile: We will like take care of this one
at Novell.
- Assembly signing: I do not know what is the state
- of this feature currently in Mono, maybe Sebastien and
- Zoltan could give us an update here.
+ Assembly signing: There are two ways to sign
+ assemblies.
+
+ StrongNames - It is possible to sign
+ and verify strongname signatures using the
+ sn.exe security tool. This same tool can also
+ create the required key pairs to sign the
+ assemblies. What we are lacking:
+
+ - The runtime doesn't check
+ strongname signatures (if present)
+ when loading an assembly outside the
+ GAC;
+
- sn.exe cannot be used to sign,
+ nor verify, an assembly that contains
+ the "ECMA public key";
+
- sn.exe doesn't support all options
+ to turn on/off runtime verification
+ for some assemblies;
+
- StrongNameIdentityPermission
+ support isn't complete as it depends
+ on CAS.
+
+
+ Authenticode - It is possible today
+ to sign assemblies (in fact any PE file) with
+ an Authenticode(r) compatible signature (with
+ or without a timestamp) using the security
+ tools cert2spc.exe and signcode.exe. We also
+ have support to test this using the tools
+ makecert.exe, chktrust.exe and setreg.exe.
+ What we are lacking:
+
+ - Currently our X.509 certificate
+ chaining is very limited and we do
+ not support certificate revocation
+ in anyway;
+
- Not every options are implemented
+ in all tools (and some do not really
+ apply to Mono);
+
- PublisherIdentityPermission
+ support isn't complete as it depends
+ on CAS.
+
ASP.NET caching: Non-existant at this point, this
needs to be implemented.
@@ -152,6 +193,13 @@ vertical-align: top;
welcomes the contribution of the rest of the Mono team and
encourage the developers to focus on 1.0, to have a solid
release, and a solid foundation that can lead to 1.2
+
+ We will use Bugzilla milestones to track these issues.
+
+
Synchronized releases
+
+ It would be great if we can ship Mono 1.0 with Gtk# 1.0 and
+ a preview of Monodoc with the early documentation.
Alpha components.
@@ -220,7 +268,7 @@ vertical-align: top;
Avalon plans
- On the surface Avalaon seems like it uses something like
+
On the surface Avalon seems like it uses something like
GdiPlus/Cairo for rendering. That was my initial feeling, but
it turns out that they had to rewrite everything to have a
performing rendering engine, and implement some very advanced
@@ -248,7 +296,7 @@ vertical-align: top;
Indigo Plans
Indigo is still an early product (FAQ,
+ href="http://msdn.microsoft.com/Longhorn/understanding/pillars/Indigo/default.aspx?pull=/library/en-us/dnlong/html/indigofaq1.asp">FAQ),
but it could benefit from continued development of our WSE1
and WSE2 components, later to bring some of the code to it.