And are the implementations not prone to modification?<br>As in we could specify a particular #print_port to bypass them?<br><br><div class="gmail_quote">On Wed, Mar 18, 2009 at 6:58 PM, Vamsi Krishna Davuluri <span dir="ltr"><<a href="mailto:vamsi.davuluri@gmail.com">vamsi.davuluri@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>The link you gave didn't work, so I checked this page<br><a href="http://wiki.laptop.org/go/OLPC_Bitfrost" target="_blank">http://wiki.laptop.org/go/OLPC_Bitfrost</a><br>
I have gone through security models listed, umm ... was there anything specific I was to look into?<div><div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On Wed, Mar 18, 2009 at 6:42 PM, Luke Faraone <span dir="ltr"><luke@faraone.cc></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote">2009/3/18 Vamsi Krishna Davuluri <span dir="ltr"><<a href="mailto:vamsi.davuluri@gmail.com" target="_blank">vamsi.davuluri@gmail.com</a>></span><div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div><div class="gmail_quote">I'd grant them only if the user is the owner of that specific document or is master root. This will be most useful in case the machine acts as a cups server and a request comes from the network, we could see that other than the local master, no one else on the network has access to that particular job, or stop that printing event from taking place.<br>
<br>btw thought of another thing, when the print button is clicked in an activity, the request metadata (object) is sent to the journal, but the journal doesnt have to immediately take over control, instead within the activity a pop up comes which says 'print jobs in queue('this can be closed, or clicked to go to the journal where the job can be canceled, or started) and when loging in into sugar, if pending jobs are there again a notification is displayed, and if a print job is of a particular activity, and they are pending, and if the same activity is opened again it notification is displayed.<br>
</div></div></div></blockquote></div></div><br>You might want to review the OLPC project (and therefore sugar's) security model: <a href="http://dev.laptop.org/git?p=security;a=blob;f=bitfrost.txt" target="_blank">http://dev.laptop.org/git?p=security;a=blob;f=bitfrost.txt</a><div>
<div></div><div><br>
<br clear="all"><br>-- <br>Luke Faraone<br><a href="http://luke.faraone.cc" target="_blank">http://luke.faraone.cc</a><br>
</div></div></blockquote></div><br>
</div></div></blockquote></div><br>