SnipSnap Users Mailing List for discussions about the use and installation of SnipSnap. ()

headers dodo | 7 Sep 05:04

dodoflying <at> gmail.com

_______________________________________________
SnipSnap-Users Mailing List
snipsnap-users <at> snipsnap.org | http://snipsnap.org/
http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
Hi Carsten,

no problem here, running a slightly modified version of 1.0b2. Works on 
snipsnap.org, too.

Regards,
Michael

Hi all,
I created a link like this:
{link 
excel|http://intranet/livelink/livelink.exe?func=ll&objId=1105426&objAction=Open}

This creates a clickable link(with the correct URL shown), but by clicking 
on the URL its wrong. Its somethink like:
http://intranet/livelink/livelink.exe?func=ll&#38;objId=1105426&#38;objAction=Open

I think the ';' in it makes problems.

Did somebody have the same problem ? I suppose it's a bug.

Carsten_______________________________________________
SnipSnap-Users Mailing List
snipsnap-users <at> snipsnap.org | http://snipsnap.org/
http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users

=============================================================================================================================
The information contained in this communication is confidential, may be subject to legal privileges, may
constitute inside information, and is intended only for the use of the addressee.  It is the property of
Abbott Laboratories or its relevant affiliate.  Unauthorized use, disclosure or copying of this
communication or any part thereof is strictly prohibited and may be unlawful.  If you have received this
communication in error, please notify Abbott Laboratories immediately by return e-mail and destroy
this communication and all copies thereof, including all attachments.
=============================================================================================================================

_______________________________________________
SnipSnap-Users Mailing List
snipsnap-users <at> snipsnap.org | http://snipsnap.org/
http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
Is there anyway to make the images align correctly with wrapped words?

For instance:

+---------+ Hello, this is just an example
| Image   | in ASCII that probably will not
|         | look right on most email
+---------+ clients because they are not using
a fixed width font like I am. Regardless, this
is the example that I am talking about.

It seems that {image:align=flow-left|img=pic.jpg} does not accomplish 
the above task like I thought it would.

Thanks for any info!

Jeremy

Is it possible to have a page not visible to people not logged in? or 
maybe a only a select few people?

Jeremy

This would need some hacking in 1.0b2-uttoxeter. It can be achieved  
by using the label mechanism in conjunction with a small script.
It will only protect the content of the snip, not labels, attachments  
or the meta-data, but its a start:

Create a Snip somewhere, like SnipSnap/SecuredContentViewer

Paste the following into this snip:

<%
org.snipsnap.app.Application app = org.snipsnap.app.Application.get();
org.snipsnap.user.User user = app.getUser();
org.snipsnap.user.Roles roles = new org.snipsnap.user.Roles();
roles.add(org.snipsnap.user.Roles.AUTHENTICATED);

if(org.snipsnap.user.Security.hasRoles(user, roles)) {
println(app.getParameters().get("viewed").getXMLContent());
} else {
println("You are not allowed to view the contents of this snip.");
}
%>

Then add a label to this snip, Select TypeLabel and use text/gsp as  
type.
Go back to the normal view of this snip and click [lock] as an admin  
user (important!)

Then go to the snip you want to protect:

add a TypeLabel and select anything (i.e. Summary) and select  
SecuredContentViewer as the view handler.

Now only authenticated users can view your snip.

Leo.

On 18.09.2005, at 05:03, Jeremy Cowgar wrote:

> Is it possible to have a page not visible to people not logged in?  
> or maybe a only a select few people?
>
> Jeremy
>
> _______________________________________________
> SnipSnap-Users Mailing List
> snipsnap-users <at> snipsnap.org | http://snipsnap.org/
> http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
>

--
Mud.DE -- Gemeinschaft Virtueller Welten Deutschland
Matthias L. Jugel http://www.mud.de  Info: info <at> mud.de

The script is nice, but I just tested and it does not really protect  
the contents, as the /raw/SnipSnap still shows the raw content ...

We have started implementing a real security model for the next  
release which currently has no release data, unfortunately :( There  
is a light at the horizon as we have an internal project which needs  
this too.

Leo.

On 18.09.2005, at 05:03, Jeremy Cowgar wrote:

> Is it possible to have a page not visible to people not logged in?  
> or maybe a only a select few people?
>
> Jeremy
>
> _______________________________________________
> SnipSnap-Users Mailing List
> snipsnap-users <at> snipsnap.org | http://snipsnap.org/
> http://snipforge.org/cgi-bin/mailman/listinfo/snipsnap-users
>

--
Mud.DE -- Gemeinschaft Virtueller Welten Deutschland
Matthias L. Jugel http://www.mud.de  Info: info <at> mud.de

On Sun, 18 Sep 2005, Matthias L. Jugel wrote:

> The script is nice, but I just tested and it does not really protect the
> contents, as the /raw/SnipSnap still shows the raw content ...
> 
> We have started implementing a real security model for the next release which
> currently has no release data, unfortunately :( There is a light at the
> horizon as we have an internal project which needs this too.
> 
> Leo.

If you're implementing a "real" security model, will this extend "under 
the hood" - are you thinking about locking down security policies and 
scripting capabilities? Currently embedding scripting capabilities into 
snipsnap means exposing the entire app to the danger of malicious 
scripts: hence the "it is only permitted for admin users" types of 
workarounds.

When I last had a look at Rhino for the purposes of plugging it into 
snipsnap, it transpired that it needed quite a few security capabilities 
in order to operate properly. To get properly "sandboxed" script 
capabilities really means adequately separating the rendering and 
storage engines and having the storage layer require some kind of 
credential (capability?) in order to perform storage ops. If you have 
that, you're a smallish step away from wrapping the privileged 
operations in doPrivileged and being able to properly sandbox 
user-supplied scripts.

--

-- 
jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/
Tel +44 (0)117 3317661   http://ioctl.org/jan/
"...perl has been dead for more than 4 years." - Abigail in the Monastery

Mon	Tue	Wed	Thu	Fri	Sat	Sun

			1	2	3	4
5	6	7	8	9	10	11
12	13	14	15	16	17	18
19	20	21	22	23	24	25
26	27	28	29	30

6	May 2008
10	April 2008
4	February 2008
1	November 2006
4	October 2006
4	September 2006
12	August 2006
18	July 2006
24	June 2006
12	May 2006
8	April 2006
3	February 2006
13	January 2006
9	December 2005
6	November 2005
11	October 2005
9	September 2005
7	August 2005
5	July 2005

snipsnap

link not working with parameters

Re: link not working with parameters

Disabling access to snipsnap unless authenticated

Image Alignment

Protected Page

Re: Protected Page

Re: Protected Page

Re: Protected Page