<div>Michael, Other Chris and everyone else,</div><div><br></div><div>Thanks for your help on this. I was able to get setting ACEs working as I required with your advice.</div><div><br></div><div>I put together a short post describing what I was looking to do:</div>
<div><a href="http://chrisdail.com/2012/03/15/hacking-jcifs-set-permissions/">http://chrisdail.com/2012/03/15/hacking-jcifs-set-permissions/</a><br></div><div><br></div><div>Also, I have made all of the code changes available on GitHub here:</div>
<div><a href="https://github.com/chrisdail/jcifs">https://github.com/chrisdail/jcifs</a><br></div><div><br></div><div>Thanks</div><div><br></div><div>Chris</div><br><br><div class="gmail_quote">On Fri, Mar 9, 2012 at 1:26 PM, <a href="mailto:christofer.dutz@c-ware.de">christofer.dutz@c-ware.de</a> <span dir="ltr"><<a href="mailto:christofer.dutz@c-ware.de">christofer.dutz@c-ware.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Geee ... certainly a lot of Chris' her recently :-)<br>
<br>
Well I was simply assuming that the midlc tool came from the samba guys, because the idls shipped with it were a perfect match with the knowledge base of them in the year 2000 - At least what I found regarding the svcctl mentioned in that book I talked about (DCE/RPC over SMB - Samba and Windows NT domain internals). Especially the names of the fields and commands. It seemed to me the latest information from the official MS IDLs never made it there. And the support of samba and c output lead me tot hat assumption. If this was wrong, I am realy sorry.<br>
<br>
I am also sorry that you find my documentation rather "unqualified" but that's what you get if you users have to reverse engineer something, because support is allmost not existent. What I am doing is that I am trying to get something running and am documenting what I am doing so I can read what I did sometime in the future and mabe it would help someone on the same path.<br>
<br>
It would be great if you would please correct me, wehere my assumtions were wrong, cause this would prevent wrong information form spreading. All I can say is: It works the way I did it. And my work on the svcctl.idl is proceding nicely.<br>
<br>
With kind regards,<br>
<div class="im"> Chris<br>
<br>
<br>
[ C h r i s t o f e r D u t z ]<br>
<br>
C-Ware IT-Service<br>
Inhaber<br>
Dipl. Inf. Christofer Dutz<br>
Karlstraße. 104, 64285 Darmstadt<br>
<br>
</div><div class="im">fon: 0 61 51 / 27315 - 61<br>
fax: 0 61 51 / 27315 - 64<br>
mobil: 0171 / 7 444 2 33<br>
email: <a href="mailto:christofer.dutz@c-ware.de">christofer.dutz@c-ware.de</a><br>
<a href="http://www.c-ware.de" target="_blank">http://www.c-ware.de</a><br>
<br>
UStId-Nr. DE195700962<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div>-----Ursprüngliche Nachricht-----<br>
Von: Michael B Allen [mailto:<a href="mailto:ioplex@gmail.com">ioplex@gmail.com</a>]<br>
Gesendet: Freitag, 9. März 2012 17:03<br>
An: <a href="mailto:christofer.dutz@c-ware.de">christofer.dutz@c-ware.de</a><br>
Cc: <a href="mailto:jcifs@lists.samba.org">jcifs@lists.samba.org</a><br>
<div class="im HOEnZb">Betreff: Re: [jcifs] Updating ACE[] using jcifs<br>
<br>
</div><div class="HOEnZb"><div class="h5">On Fri, Mar 9, 2012 at 3:10 AM, <a href="mailto:christofer.dutz@c-ware.de">christofer.dutz@c-ware.de</a> <<a href="mailto:christofer.dutz@c-ware.de">christofer.dutz@c-ware.de</a>> wrote:<br>
> One thing I should comment on ist hat the idl files provided with<br>
> midlc are not the ones provided by microsoft.<br>
><br>
> They were the result of intense reverse engineering oft he Samba guys.<br>
> Microsoft published their IDLs afterwards and the format is similar,<br>
> but not identical. So you will have to manually translate them into<br>
> the format midlc understands. I'm doing this for the missing calls in svcctl.idl.<br>
<br>
Hi Chris,<br>
<br>
The midlc tool and idl used by midlc is has absolutely nothing to do with what Samba uses. Samba's "pidl" utility (which is written in<br>
Perl) uses a derivative of MS IDL syntax that is quite different. Pidl has many "extensions" that midl does not have. The JCIFS midlc utility uses a strict subset of MS IDL syntax. With the exception of the [op()] attribute extension, the syntax understood by midlc is identical to that of midl. Meaning IDL written for midlc would work with midl whereas IDL written for pidl would absolutely not work with midl.<br>
<br>
Also, I'm sorry to say that your documentation would probably mislead people more than it helped them. Please do not post that link here.<br>
<br>
Mike<br>
</div></div></blockquote></div><br>