You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by Jim Arnott <ja...@bridge.com> on 2002/12/10 17:08:34 UTC

Bugs 14907, 15000 Security problems (bluesunrise)

Just a heads up...

I assume someone reads this jetspeed-dev list, if not I'll post this
to jetspeed-user, later.

These bugs are still there if bluesunrise is up to date. I just gave myself
admin privileges and I can see everyone's e-mail address.

Did I place the bug reports in the wrong version? I just selected the latest 
from the menu. Sorry if I did. (they get posted to this list also)

Jetspeed is useless with these security problems.

Bluesunrise and everyone else, I would not place any of the latest version
on the net until these are resolved or at least warn those who login that
there accounts are open to world.

-jim
Reuters R&D

Ya, I Know, what do you want for nothing.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: The Tutorial

Posted by Gary Lawrence Murphy <ga...@canada.com>.
You can't save DOC files in DocBook because DOC files only describe
what the document looks like, whereas DocBook describes the semantics
of what the words mean.

What you /can/ do is to cut a few corners by using OpenOffice to
export into an XML which you might transform into the beginnings of
DocBook, then go in by hand and add the required markup.  I've had
some success exporting to HTML and starting from there towards
creating DocBook.  There are some excellent tips on how to do this
in the Linux Documentation Project's authoring guide (www.tldp.org)

The big danger is that once you introduce any sequence of strings that
breaks the DTD, with such a large document, you might spend a lot of
your time debugging XML rather than doing something productive.  In
the long run, it may even be more economical to use cut and paste and
completely rebuild the document using LyX or some other DocBook-aware
editing system.

let this be a lesson to the DOC-heads out there: When you lock your
files into a vendor format, you lock yourself into a vendor format ;)

-- 
Gary Lawrence Murphy - garym@teledyn.com - TeleDynamics Communications
   - blog: http://www.teledyn.com/mt/ - biz: http://teledyn.com/ -
  "Computers are useless. They can only give you answers." (Picasso)

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


Re: The Tutorial

Posted by Christophe <ch...@skynet.be>.
> Has anyone ever converted a Word document to docbook?

I think OpenOffice can do it. Open your word doc in this nice word processor
and save it to docbook format.
Check in the save as ...  if you see the docbook format


Christophe


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


The Tutorial

Posted by David Sean Taylor <da...@bluesunrise.com>.
I was talking with Paul last night, and he asked me if I had any plans to
put the tutorial document on the jakarta site.
After giving some thought, I decided it would be best to do so.
That way everyone can contribute the tutorial.

The document is currently written in Microsoft Word, you know that word
processor that crashes all the time right before you save your work.

Before moving it to Jakarta, I'd like to convert the document over to
Docbook format.
Has anyone ever converted a Word document to docbook?
Do you think that Docbook is a good format. I'd personally like to get some
experience writing to it.
I started writing a book with Docbook once before, and I liked it.

The JPortal project could also be moved into the jakarta cvs.
However I really wanted to emphasize that it is a separate project, and for
it to emulate a real life project being housed outside of the jetspeed cvs.
For the JPortal example source, I propose a subproject of Jetspeed,
jakarta-jetspeed-jportal, which is a different cvs.

David



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>


RE: Bugs 14907, 15000 Security problems (bluesunrise)

Posted by David Sean Taylor <da...@bluesunrise.com>.

> -----Original Message-----
> From: Jim Arnott [mailto:jarnott@bridge.com]
> Sent: Tuesday, December 10, 2002 8:09 AM
> To: jetspeed-dev@jakarta.apache.org
> Subject: Bugs 14907, 15000 Security problems (bluesunrise)
>
>
> Just a heads up...
>
> I assume someone reads this jetspeed-dev list, if not I'll post this
> to jetspeed-user, later.

Not the most active list in the world. But we do get a lot of work done for
a small team.
You can see the list activity here:

http://nagoya.apache.org/eyebrowse/SummarizeList?listId=22

>
> These bugs are still there if bluesunrise is up to date. I just
> gave myself
> admin privileges and I can see everyone's e-mail address.

Its a beta release. Stated very clearly.
The bugs will be fixed before the final 1.4 Jetspeed release, which we hope
to put out within a month or so.

As Mark has pointed out, bug #14907 is a configuration issue. Please close
the bug.
I'll look into bug 15000 today. Looks like an easy fix.
References are a fairly new feature and haven't been used much up until
recently.

Bluesunrise is an 'out-of-the-box' demo site.
Its not a production site. Its just there for you to see Jetspeed running
live and take it for a test run, thats it.
It serves no other purpose.
All accounts are deleted with every beta release.

>
> Did I place the bug reports in the wrong version? I just selected
> the latest
> from the menu. Sorry if I did. (they get posted to this list also)
>
> Jetspeed is useless with these security problems.

I think you meant to say "useless to me". I don't find it useless, and
neither do my clients.
On all of my installations, we remove the User Admin functions from the
deployment.
We have our own admin forms for entering users, which do not use the
controller with the security hole.
There security hole is only with this one controller.

My Jetspeed deployments have undergone in-depth and critical security
reviews by third party security experts, and passed.

>
> Bluesunrise and everyone else, I would not place any of the latest version
> on the net until these are resolved or at least warn those who login that
> there accounts are open to world.

No problem.
I've just shutdown the bluesunrise site.
I'll start it up again when bug #15000 is fixed.

>
> -jim
> Reuters R&D
>
> Ya, I Know, what do you want for nothing.

Thats a strange sig.
I could be wrong, but some open source people may find it offensive.
I don't find it offensive. I could care less if you see open source as
nothing more than a place for you to come and get free software.
But it does leave an impression.

Regards,

David



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>