RE: [oic] OIC SVN Web Manifests - Challenges

["Dennis E. Hamilton" <dennis.hamilton@acm.org>]

I wanted to set the svn:mime-type automatically without having to remember.
Unfortunately, the config file at the client does not allow MIME Type
parameters, such as character set encoding to specify UTF-8, that sort of
thing (the needed ";" is treated as a separator in the config file and I
found no way to escape it).  So to specify the character-set encoding I
would have to do it manually all of the time.

I got around that simply putting the mime.types file in the appropriate tree
on the SVN Server.  I no longer have to remember to set the mime type
manually and I get the parameters I want using that file.  Of course, your
mileage may vary.  (Mine is in miles/gallon, yours is in liters/kilometer, I
say tomato, you say potato, that sort of thing. [;<)

Have fun with the encryption stuff.  I know Wouter also got it to work.  I'd
be curious how you figure it out without consulting an implementation.

I have a pent-up pending analysis and blog post on the ODF 1.x package
encryption scheme's vulnerability to known-plaintext attacks.  The fact that
the digital signature files cannot be encrypted is also something that
should raise eyebrows in document security circles.

 - Dennis 

-----Original Message-----
From: Hanssens Bart [mailto:Bart.Hanssens@fedict.be] 
http://lists.oasis-open.org/archives/oic/200912/msg00034.html
Sent: Thursday, December 10, 2009 23:13

To: oic@lists.oasis-open.org
Subject: RE: [oic] OIC SVN Web Manifests - Challenges

Dennis,

probably setting the svn:mime-type when doing an svn commit does
the trick, I forgot to do this for the (x)html I've uploaded, but I'll
correct
it when reworking it (today or in the weekend :-)


I'm now at the encryption part, writing a small python script (perhaps
I change to java/groovy (there is a PBKDF2 for python out there for, 
but haven't tried it yet)

I've did signing before, so if all goes well, 1.2 part 3 is "covered" by
the end of next week (well, at least for my purposes)

Bart

________________________________________
From: Dennis E. Hamilton [dennis.hamilton@acm.org]
http://lists.oasis-open.org/archives/oic/200912/msg00033.html
Sent: Friday, December 11, 2009 12:13 AM
To: Hanssens Bart; oic@lists.oasis-open.org
Subject: RE: [oic] OIC SVN Web Manifests - Challenges

Bart, I got the XHTML to serve up properly from the OIC SVN Server by
copying into my sandbox folder at SpecAnalysis/construction/sandbox/3/

1. Notice that
<http://tools.oasis-open.org/version-control/svn/oic/SpecAnalysis/constructi
on/sandbox/3/001.html>
serves up properly.

2. All I did was copy the folder at
<http://tools.oasis-open.org/version-control/svn/oic/TestSuite/branches/bart
h/odf12/scenarios/part3/3/3/>.

3. I then updated the layout.css link to have the actually layout.css file
(since the 001.html file refers to the link location by relative URL).

4. I think the difference is the file mime.types that is at
<http://tools.oasis-open.org/version-control/svn/oic/SpecAnalysis/>.  Try
something similar at TestSuite/ or TestSuite/branches/barth/ to see if that
works for your material in its location.

5. That should take care of the XHTML being recognized properly by browsers.
To get the CSS to work, you'll have to make a copy in the same folder or
else change the XHTML to refer to a global location of a CSS file that is
used by multiple XHTML pages.

 - Dennis

PS: When I open the file from my file system, my browser recognizes the
XHTML because of its filename extension, it seems.  The problem on pages
from the SVN Server is that is won't provide an appropriate MIME type in the
HTTP response header automatically.


---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php