setacl-devel — Discussion Regarding SetACL's Development

[Setacl-devel] setacl

[ismail K. <is...@si...>]

The setacl service returns an error. source code or support to
troubleshoot the issue.

Faulting application name: **.exe, version: 1.0.0.8, time stamp: 0x5e05c698
Faulting module name: SetACL.dll, version: 3.0.6.0, time stamp: 0x504e4c4f
Exception code: 0xc0000005
Fault offset: 0x000000000003b4a1
Faulting process id: 0x1d30
Faulting application start time: 0x01d5bca48c28f87b
Faulting application path: C:
Faulting module path: C:\Program Files\SetACL.dll
Report Id: 4e180e4d-28a0-11ea-80e9-000c29e6fe37
Faulting package full name:
Faulting package-relative application ID:

İyi Çalışmalar

İsmail KAYAKIRAN
Siber Güvenlik Uzmanı
Sistem Danışmanı Bilişim Hizmetleri
0533 215 73 95
is...@si...
www.sistemdanismani.com

[Setacl-devel] SetACL is nearly finished

[Helge K. <hel...@ne...>]

The new version of SetACL is nearly finished. I just coded the last function
(restore entire SDs from a file). What remains to be done are very much
testing, the command line interface and the OCX interface. Testing is, of
course, a lot of tedious work, but the two interfaces should be easy to
implement.

Since none of you contributed a single line of code I consider the
cooperation I was hoping for failed and have consequently removed you from
the project's list of developers.

Helge

[Setacl-devel] Re: COM and SetACL

[Helge K. <hel...@ne...>]

Comments below.

Helge

----- Original Message -----
From: "Howard W Wortley"
To: <set...@li...>
Sent: Thursday, January 23, 2003 8:11 PM
Subject: [Setacl-devel] COM and SetACL


> >> COM control: Howard, would you like to start with the
> control?
>
> sure
>
> >> When I started to work on the main class CSetACL I
> implemented the interface to the outside world first - it
> should be complete enough by now to be able to build a
> control (and a console EXE) around it. My plan was to expose
> the public funtions in the control which are all input
> functions to pass data to the class. There is, of course,
> the need to pass strings back to the calling
> class/function/EXE, like detailed error/success/status
> messages which might be needed by the caller. I used a
> callback function for that purpose to be able to send any
> message in realtime while the program is still working.
> Example: someone uses the OCX to build a GUI around SetACL.
> The user of this GUI wants to create a permission listing of
> a large partition which might take a while. Via the callback
> function the GUI can display in real time the permissions
> that currently processed by SetACL. Is a callback function a
> viable way to do it and does it work with COM?
>
> Hum ho.
>
> (1) where are the current classes there are no files to download on the
> site.
> Are we working from a clean sheet ?

This is an easy one (file releases refer only to files that are made
available to the end user - which we do not have yet):

https://sourceforge.net/cvs/?group_id=69165

You can access the CVS from there with your browser. It is of course easier
(and for uploading mandatory) to use the CVS client WinCVS. There are
detailed descriptions of how to set up Putty (for SSH encryption) and WinCVS
in sourceforge's docs section.

In the CVS I have created a directory called "baseclasses" which contains my
work to date. It consists of an MFC console app (for testing purposes) built
around the main classes which reside in the file CSetACL.cpp.

I am afraid I do not quite understand your question regarding the "clean
sheet" (sorry, my native language is german). Do you mean if we start from
scratch? I would say yes, the new baseclasses (see above) have nothing in
common with the old SetACL, except for some of the internal logic.

> (2) what kind(s) of COM objects do you want to implement. It is not
possible
> to have one ATL COM object which will run as a console app, a COM server
and
> as an ActiveX control, though of course there are common elements.
> It looks to me that the wish list consist of
> a. a classic ATL COM application that does pretty much the same as the
> current setACL
> b. a COM server that can be called from any C++ application; a version
that
> supports VB6 is a little different cos of the wacky VB6 strings
> c. a console version of (a)
> d. an OCX control for scripters / VB6
>
> My suggestion is to implement (a) amd (c) first. (b) can be derived from
> that fairly easily. (d) is a different bag of tricks - an ActiveX OCX
> control runs in the thread of the app that invokes it remember, and VB6
> cannot do free threading except by black arts. Getting back to the COM
> object generally with COM u define the interfaces and methods and then
build
> a UI to express them rather than developinf downwards from the UI
VisualC++
> wizard style. Do u have the resource files for the dialogs anyway ?
> It would help a lot if u can post the souce for the original SetACL so i
can
> get my head aorund your thinking, plus anything for the new one u have
apart
> from specs. which I have.
>

Maybe I was not specific enough on this one (It does not help that I am no
COM expert, though I implemented an ATL COM DLL to be used from VB five
years ago). I believe SetACL is and will mainly be used by systems
administrators. These people need (in decreasing order):

1. a console app to be used from the command line or in scripts or batch
files
2. an ActiveX DLL to be used from OLE/ActiveX enabled scripting languages
like VBS or Perl

There are a few actual programmers who use SetACL (one guy mailed me who
develops an installation program like InstallShield) from languages like C++
who would need:

3. an ATL COM object


Some more remarks on my points with regard to the callback function:

To 1) The console app should be fairly straightforward much like the one
used by me for testing purposes (in the CVS/baseclasses) which already uses
the callback function.

To 2) I had the following in mind: to build an ActiveX DLL in C++ which can
be used easily from VBS / VB. I imagined the callback could be implemented
nicely using (ActiveX) events which are supported in VB (I do not know about
VBS). Even if VBS does _not_ have events one could still use the console
version from VBS if the status strings passed via the callbacks/events are
needed.

Some background: the callback function is only needed to pass status strings
to the caller, for example the name of the directory that is being
processed. The ActiveX DLL would implement a function that is being called
and passed these strings. Each time the function is called it fires an event
that can be caught in VB with an event handler similar to "OnClick".

To 3) This should be fairly straightforward, too.


Does all this make sense? I hope I am not terribly wrong, especially with
2).

I think 1) and 2) are the most important implementations for our target
audience.

Howard: just to be sure: when I asked if you'd like to program the COM
control I really meant the ActiveX DLL from 2).

[Setacl-devel] COM and SetACL

[Howard W W. <hwo...@ms...>]

>> COM control: Howard, would you like to start with the
control?

sure

>> When I started to work on the main class CSetACL I
implemented the interface to the outside world first - it
should be complete enough by now to be able to build a
control (and a console EXE) around it. My plan was to expose
the public funtions in the control which are all input
functions to pass data to the class. There is, of course,
the need to pass strings back to the calling
class/function/EXE, like detailed error/success/status
messages which might be needed by the caller. I used a
callback function for that purpose to be able to send any
message in realtime while the program is still working.
Example: someone uses the OCX to build a GUI around SetACL.
The user of this GUI wants to create a permission listing of
a large partition which might take a while. Via the callback
function the GUI can display in real time the permissions
that currently processed by SetACL. Is a callback function a
viable way to do it and does it work with COM?

Hum ho.

(1) where are the current classes there are no files to download on the
site.
Are we working from a clean sheet ?
(2) what kind(s) of COM objects do you want to implement. It is not possible
to have one ATL COM object which will run as a console app, a COM server and
as an ActiveX control, though of course there are common elements.
It looks to me that the wish list consist of
a. a classic ATL COM application that does pretty much the same as the
current setACL
b. a COM server that can be called from any C++ application; a version that
supports VB6 is a little different cos of the wacky VB6 strings
c. a console version of (a)
d. an OCX control for scripters / VB6

My suggestion is to implement (a) amd (c) first. (b) can be derived from
that fairly easily. (d) is a different bag of tricks - an ActiveX OCX
control runs in the thread of the app that invokes it remember, and VB6
cannot do free threading except by black arts. Getting back to the COM
object generally with COM u define the interfaces and methods and then build
a UI to express them rather than developinf downwards from the UI VisualC++
wizard style. Do u have the resource files for the dialogs anyway ?
It would help a lot if u can post the souce for the original SetACL so i can
get my head aorund your thinking, plus anything for the new one u have apart
from specs. which I have.

Howard






If an ActiveX control for VB6/vbscript were available, it would help to
 server is other additional applications, i.e. ASP-based web applications
and
 VBA.

[Setacl-devel] exp. Unicode support added

[Helge K. <hel...@ne...>]

I have just updated our CVS repository - the current version should already
set file system DACLs and SACLs as well as owner and group correctly.

I have also added Unicode support - although still experimental. I have
defined the two necessary macros UNICODE and _UNICODE and corrected all
compiler errors. My first tests show that "normal" (ANSI) and Unicode file
names do work.

Anyone with Unicode experience please review the code and tell us if this is
OK.

Helge

Re: [Setacl-devel] Another thing: Unicode support

[Kenneth C. <krc...@ms...>]

Not sure on this one, myself.

Seems like you would at least need a String class that supports Unicode.

Maybe some info at these links:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_2so5.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_6ort.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unicode_0a5v.asp




>From: Helge Klein <hel...@ne...>
>Reply-To: set...@li...
>To: set...@li...
>Subject: [Setacl-devel] Another thing: Unicode support
>Date: Thu, 16 Jan 2003 11:46:53 +0100
>
>I got E-Mail a few days ago from someone who tried to use
>the current version of SetACL on files/dirs that contain
>unicode characters. It does not work, of course.
>
>Until then it was not really clear to me that unicode IS
>supported in the NTFS file system. I just tried it out with
>theWwindows utility character map - I was able to insert an
>arabic character into a file name and explorer displayed it
>correctly!
>
>Obviously it would be very nice to have SetACL support this.
>It should work with any kind of character encoding (ANSI,
>unicode) that Explorer allows. My own knowledge of unicode
>is nearly nonexistent. Does anyone have experience with this
>and a suggestion as to how we best (and easiest ;-)
>implement this?
>
>Helge
>
>
>-------------------------------------------------------
>This SF.NET email is sponsored by: Thawte.com
>Understand how to protect your customers personal information by 
>implementing
>SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
>Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
>_______________________________________________
>Setacl-devel mailing list
>Set...@li...
>https://lists.sourceforge.net/lists/listinfo/setacl-devel


_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*  
http://join.msn.com/?page=features/junkmail

Re: [Setacl-devel] Active Directory Support and my skills

[Kenneth C. <krc...@ms...>]

I have some experience with AD in .NET applications.... mainly in 
creating/deleting/moving users and modifying attributes, including an 
object's "memberof" attribute, which is what you would use to add a user to 
a given security list.

So, I may be able to assist with questions on those items.


>From: Casey Smith <red...@ya...>
>Reply-To: set...@li...
>To: set...@li...
>CC: hel...@ne...
>Subject: [Setacl-devel] Active Directory Support and my skills
>Date: Wed, 15 Jan 2003 21:18:05 -0800 (PST)
>
>
>  I have written programs in VB using ADSI for Active directory.  Now, I 
>don't know how much of that will over lap into VC++, but I would be willing 
>to try it or help out in that area.  I am not familiar with SDDL strings 
>though.  So until you are to that point I may just have to play the role of 
>tester.  I do know the naming convention for AD very well (e.g. 
>CN=Someone,OU=Software,OU=Engineering,DC=Microsoft,DC=Com.).  If anyone 
>wants a good reference tool or code for enumerating any of the objects I 
>can provide that.
>I am looking over DSAcls.exe to see what exactly that does so i can get an 
>idea of what you want to be able to do.
>So, I will keep figuring out this program.  If someone has a task that I 
>might be able to do let me know otherwise I will just be waiting.  Thanks 
>Everyone!
>Helge:  I am going through your code trying to figure everything out and I 
>have to say that your program is very well commented and written.  It has 
>so far been one of the easiest programs that I have jumped into the middle 
>of and tried to figure out.
>  Helge Klein <hel...@ne...> wrote: Active Directory support 
>_could_ be included in SetACL in
>the future (when everything else works ;-). I do know that
>it is quite complex; also, there is a tool in the Reskit
>called DSAcls.exe that already does the job. I suggest we
>talk about this again later.
>
>NT4-Support: until now I have only come across one function
>(regarding SDDL strings) that is not available in NT. We
>_could_ drop NT support which would open the path to
>exporting AND importing complete security descriptors with
>all DACL and SACL settings (as SDDL strings), and enable AD
>support. What do you think?
>
>COM control: Howard, would you like to start with the
>control? When I started to work on the main class CSetACL I
>implemented the interface to the outside world first - it
>should be complete enough by now to be able to build a
>control (and a console EXE) around it. My plan was to expose
>the public funtions in the control which are all input
>functions to pass data to the class. There is, of course,
>the need to pass strings back to the calling
>class/function/EXE, like detailed error/success/status
>messages which might be needed by the caller. I used a
>callback function for that purpose to be able to send any
>message in realtime while the program is still working.
>Example: someone uses the OCX to build a GUI around SetACL.
>The user of this GUI wants to create a permission listing of
>a large partition which might take a while. Via the callback
>function the GUI can display in real time the permissions
>that currently processed by SetACL. Is a callback function a
>viable way to do it and does it work with COM?
>
>CVS: I started a new dir/tree called baseclasses for the
>main classes. I think it would be wise to use a separate
>dir/tree for the OCX and another one for the console UI.
>
>Helge
>
>
>
>---------------------------------
>Do you Yahoo!?
>Yahoo! Mail Plus - Powerful. Affordable. Sign up now


_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail

[Setacl-devel] Another thing: Unicode support

[Helge K. <hel...@ne...>]

I got E-Mail a few days ago from someone who tried to use 
the current version of SetACL on files/dirs that contain 
unicode characters. It does not work, of course.

Until then it was not really clear to me that unicode IS 
supported in the NTFS file system. I just tried it out with 
theWwindows utility character map - I was able to insert an 
arabic character into a file name and explorer displayed it 
correctly!

Obviously it would be very nice to have SetACL support this. 
It should work with any kind of character encoding (ANSI, 
unicode) that Explorer allows. My own knowledge of unicode 
is nearly nonexistent. Does anyone have experience with this 
and a suggestion as to how we best (and easiest ;-) 
implement this?

Helge

[Setacl-devel] Active Directory Support and my skills

[Casey S. <red...@ya...>]

 I have written programs in VB using ADSI for Active directory.  Now, I don't know how much of that will over lap into VC++, but I would be willing to try it or help out in that area.  I am not familiar with SDDL strings though.  So until you are to that point I may just have to play the role of tester.  I do know the naming convention for AD very well (e.g. CN=Someone,OU=Software,OU=Engineering,DC=Microsoft,DC=Com.).  If anyone wants a good reference tool or code for enumerating any of the objects I can provide that. 
I am looking over DSAcls.exe to see what exactly that does so i can get an idea of what you want to be able to do.
So, I will keep figuring out this program.  If someone has a task that I might be able to do let me know otherwise I will just be waiting.  Thanks Everyone!
Helge:  I am going through your code trying to figure everything out and I have to say that your program is very well commented and written.  It has so far been one of the easiest programs that I have jumped into the middle of and tried to figure out.
 Helge Klein <hel...@ne...> wrote: Active Directory support _could_ be included in SetACL in 
the future (when everything else works ;-). I do know that 
it is quite complex; also, there is a tool in the Reskit 
called DSAcls.exe that already does the job. I suggest we 
talk about this again later.

NT4-Support: until now I have only come across one function 
(regarding SDDL strings) that is not available in NT. We 
_could_ drop NT support which would open the path to 
exporting AND importing complete security descriptors with 
all DACL and SACL settings (as SDDL strings), and enable AD 
support. What do you think?

COM control: Howard, would you like to start with the 
control? When I started to work on the main class CSetACL I 
implemented the interface to the outside world first - it 
should be complete enough by now to be able to build a 
control (and a console EXE) around it. My plan was to expose 
the public funtions in the control which are all input 
functions to pass data to the class. There is, of course, 
the need to pass strings back to the calling 
class/function/EXE, like detailed error/success/status 
messages which might be needed by the caller. I used a 
callback function for that purpose to be able to send any 
message in realtime while the program is still working. 
Example: someone uses the OCX to build a GUI around SetACL. 
The user of this GUI wants to create a permission listing of 
a large partition which might take a while. Via the callback 
function the GUI can display in real time the permissions 
that currently processed by SetACL. Is a callback function a 
viable way to do it and does it work with COM?

CVS: I started a new dir/tree called baseclasses for the 
main classes. I think it would be wise to use a separate 
dir/tree for the OCX and another one for the console UI.

Helge



---------------------------------
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now

Re: [Setacl-devel] ATL COM, Active Directory Support

[Helge K. <hel...@ne...>]

Active Directory support _could_ be included in SetACL in 
the future (when everything else works ;-). I do know that 
it is quite complex; also, there is a tool in the Reskit 
called DSAcls.exe that already does the job. I suggest we 
talk about this again later.

NT4-Support: until now I have only come across one function 
(regarding SDDL strings) that is not available in NT. We 
_could_ drop NT support which would open the path to 
exporting AND importing complete security descriptors with 
all DACL and SACL settings (as SDDL strings), and enable AD 
support. What do you think?

COM control: Howard, would you like to start with the 
control? When I started to work on the main class CSetACL I 
implemented the interface to the outside world first - it 
should be complete enough by now to be able to build a 
control (and a console EXE) around it. My plan was to expose 
the public funtions in the control which are all input 
functions to pass data to the class. There is, of course, 
the need to pass strings back to the calling 
class/function/EXE, like detailed error/success/status 
messages which might be needed by the caller. I used a 
callback function for that purpose to be able to send any 
message in realtime while the program is still working. 
Example: someone uses the OCX to build a GUI around SetACL. 
The user of this GUI wants to create a permission listing of 
a large partition which might take a while. Via the callback 
function the GUI can display in real time the permissions 
that currently processed by SetACL. Is a callback function a 
viable way to do it and does it work with COM?

CVS: I started a new dir/tree called baseclasses for the 
main classes. I think it would be wise to use a separate 
dir/tree for the OCX and another one for the console UI.

Helge

---- Original message ----
>Datum: Tue, 14 Jan 2003 20:18:48 +0100
>Von: "Howard W Wortley" <hwo...@ms...>  
>Betreff: [Setacl-devel] ATL COM  
>An: <set...@li...>
>Cc: <hel...@ne...>
>
>Hi
>
>I am familiar with building COM components (clients, 
servers, console apps) etc using Visual C++ and ATL/COM. It 
is essential for building ATL/COM that the developer has SP5 
installed. Pro edition is OK no need for Enterprise stuff. I 
thought I had posted before Christmas that I thought ATL/COM 
was by far the best way to go on this project as it enables 
all of H.K. design goals to be met within a single code 
source. FWIW I am also familiar with Active Directory but I 
am not sure if SetACL is meant to get into that area or not. 
There are differences between supporting NT4 and Win2000. 
NT4 is sorta fading I suggest Win2000 and up support only.
>
>It would be possible to build using VC++ an activex OCX for 
use by VB6 if anybody thought that a good idea.
>
>
>Howard
>
>From: Helge Klein <helge@ne...>
> Language for COM control
>2003-01-14 11:44
> As already discussed in the forum SetACL is and will be
> written in VC++. There are mainly three reasons for this:
>
> a) SetACL is to run without any additional runtime files.
> Just the EXE (or OCX) is to be needed to use the program.
> Especially larger organizations will never install runtime
> libraries or even the .NET framework on production servers
> just to use a tool.
>
> b) SetACL is to fully support NT4 SP4+, W2k, XP, Windows
> Server 2003.
>
> c) SetACL needs serveral rather complex API functions which
> require pointers (to functions, too) and unicode.
>
> Those three points refer to the main program. I do not
> think, though, that it would make _any_ sense to implement
> other parts in another language. It would be very 
difficult,
> too, since the main program consists of several C++ classes
> which are _not_ wrapped in a DLL.
>
> Who has experience in building COM controls in VC++ using
> ATL or MFC?
>
> Helge

Re: [Setacl-devel] ATL COM

[Kenneth C. <krc...@ms...>]

If an ActiveX control for VB6/vbscript were available, it would help to 
server is other additional applications, i.e. ASP-based web applications and 
VBA.



>From: "Howard W Wortley" <hwo...@ms...>
>Reply-To: set...@li...
>To: <set...@li...>
>CC: <hel...@ne...>
>Subject: [Setacl-devel] ATL COM
>Date: Tue, 14 Jan 2003 20:18:48 +0100
>
>Hi
>
>I am familiar with building COM components (clients, servers, console apps) 
>etc using Visual C++ and ATL/COM. It is essential for building ATL/COM that 
>the developer has SP5 installed. Pro edition is OK no need for Enterprise 
>stuff. I thought I had posted before Christmas that I thought ATL/COM was 
>by far the best way to go on this project as it enables all of H.K. design 
>goals to be met within a single code source. FWIW I am also familiar with 
>Active Directory but I am not sure if SetACL is meant to get into that area 
>or not. There are differences between supporting NT4 and Win2000. NT4 is 
>sorta fading I suggest Win2000 and up support only.
>
>It would be possible to build using VC++ an activex OCX for use by VB6 if 
>anybody thought that a good idea.
>
>
>Howard
>
>From: Helge Klein <helge@ne...>
>  Language for COM control
>2003-01-14 11:44
>  As already discussed in the forum SetACL is and will be
>  written in VC++. There are mainly three reasons for this:
>
>  a) SetACL is to run without any additional runtime files.
>  Just the EXE (or OCX) is to be needed to use the program.
>  Especially larger organizations will never install runtime
>  libraries or even the .NET framework on production servers
>  just to use a tool.
>
>  b) SetACL is to fully support NT4 SP4+, W2k, XP, Windows
>  Server 2003.
>
>  c) SetACL needs serveral rather complex API functions which
>  require pointers (to functions, too) and unicode.
>
>  Those three points refer to the main program. I do not
>  think, though, that it would make _any_ sense to implement
>  other parts in another language. It would be very difficult,
>  too, since the main program consists of several C++ classes
>  which are _not_ wrapped in a DLL.
>
>  Who has experience in building COM controls in VC++ using
>  ATL or MFC?
>
>  Helge


_________________________________________________________________
MSN 8: advanced junk mail protection and 2 months FREE*. 
http://join.msn.com/?page=features/junkmail

[Setacl-devel] ATL COM

[Howard W W. <hwo...@ms...>]

Hi

I am familiar with building COM components (clients, servers, console =
apps) etc using Visual C++ and ATL/COM. It is essential for building =
ATL/COM that the developer has SP5 installed. Pro edition is OK no need =
for Enterprise stuff. I thought I had posted before Christmas that I =
thought ATL/COM was by far the best way to go on this project as it =
enables all of H.K. design goals to be met within a single code source. =
FWIW I am also familiar with Active Directory but I am not sure if =
SetACL is meant to get into that area or not. There are differences =
between supporting NT4 and Win2000. NT4 is sorta fading I suggest =
Win2000 and up support only.

It would be possible to build using VC++ an activex OCX for use by VB6 =
if anybody thought that a good idea.


Howard

From: Helge Klein <helge@ne...>
 Language for COM control
2003-01-14 11:44
 As already discussed in the forum SetACL is and will be
 written in VC++. There are mainly three reasons for this:

 a) SetACL is to run without any additional runtime files.
 Just the EXE (or OCX) is to be needed to use the program.
 Especially larger organizations will never install runtime
 libraries or even the .NET framework on production servers
 just to use a tool.

 b) SetACL is to fully support NT4 SP4+, W2k, XP, Windows
 Server 2003.

 c) SetACL needs serveral rather complex API functions which
 require pointers (to functions, too) and unicode.

 Those three points refer to the main program. I do not
 think, though, that it would make _any_ sense to implement
 other parts in another language. It would be very difficult,
 too, since the main program consists of several C++ classes
 which are _not_ wrapped in a DLL.

 Who has experience in building COM controls in VC++ using
 ATL or MFC?

 Helge

[Setacl-devel] Language for COM control

[Helge K. <hel...@ne...>]

As already discussed in the forum SetACL is and will be 
written in VC++. There are mainly three reasons for this:

a) SetACL is to run without any additional runtime files. 
Just the EXE (or OCX) is to be needed to use the program. 
Especially larger organizations will never install runtime 
libraries or even the .NET framework on production servers 
just to use a tool.

b) SetACL is to fully support NT4 SP4+, W2k, XP, Windows 
Server 2003.

c) SetACL needs serveral rather complex API functions which 
require pointers (to functions, too) and unicode.

Those three points refer to the main program. I do not 
think, though, that it would make _any_ sense to implement 
other parts in another language. It would be very difficult, 
too, since the main program consists of several C++ classes 
which are _not_ wrapped in a DLL.

Who has experience in building COM controls in VC++ using 
ATL or MFC?

Helge

---- Original message ----
>Datum: Mon, 13 Jan 2003 10:53:57 -0700
>Von: "Kenneth Courville" <krc...@ms...>  
>Betreff: RE: [Setacl-devel] Still alive?  
>An: "'Helge Klein'" <hel...@ne...>
>
>Sorry for my lack of response.
>
>I've been a little busy lately with the holidays and 
working on becoming
>an MCP.... later MSCE, hopefully.
>
>I don't have a problem with building a COM control for the 
solution.  My
>only limitations would be that I'd have to do it in either 
VB6 or .NET
>with C#.  I know that your code will primarily be in C/C++, 
but I really
>don't have time to learn how to build a COM control in C++ 
at the
>moment.
>
>Con's for VB6
>--------------
>No longer supported by Microsoft.
>No built-in support for C/C++ pointers.
>
>Pro's for VB6
>-------------
>Easy to use, built-in templates for building COM objects.
>Still in active use by the programming community.
>
>Con's for .NET
>--------------
>Having to install the .NET framework and current service 
packs to make
>use of the control.  This might not be too bad, considering 
that it will
>likely be built in to the OS eventually.
>
>Pro's for .NET
>--------------
>Easy to use, built-in templates for building COM objects.
>Supports pointers.
>
>Tell me what you think.  Given the language that you would 
prefer I use
>and the functions that I have to reference, I can certainly 
work on it
>when you're ready.
>

[Setacl-devel] Still alive?

[Helge K. <hel...@ne...>]

I just want to ask if there was anything wrong with my last 
mail (sent 31.12.2002 via this list) and if you are still 
interested in helping me with SetACL, since I did not get 
any replies?!

Regards, Helge

[Setacl-devel] Alpha version of SetACL base classes in CVS

[Helge K. <hel...@ne...>]

In order to start working on SetACL together a certain basic structure has
to be in place. In the last few days I have created an alpha version of the
main class, CSetACL, and two helper classes, CTrustee and CACE. I have just
uploaded the code to our CVS repository. You can have a first look here:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/setacl/baseclasses/

The intended structure should become clear once you have a look at the file
CSetACL.cpp. From here on, we should be able to work together as a team.

First, I recommend that those of you who are not familiar with CVS yet, read
the extensive documentation on sourceforge.net.

The most important question is: what work packages are there? The following
comes to my mind:

1. command line interface
2. COM control to be used from VB or scripting languages
3. re-implementation of the functionality of the current version 0.904
4. extension of that functionality (see my feature list):
4.1 set owner
4.2 set primary group
4.3 clear
4.4 remove trustee
4.5 enable / disable inheritance from parent
4.6 reset permissions on child objects
5. Active Directory support (?)
6. EXTENSIVE testing
7. documentation, web page

Now, who does what? As I have not worked with you before, I do not know what
you like to do and where your strengths are. Just one suggestion: Kenneth,
would you like to do the COM control?

Everybody: please use this list to express any thoughts or concerns and, of
course, what you would like to do. I for my part am going to do number three
first, re-implementation of the current functionality. In about a week from
now on the baseclasses should contain version 0.904's functionality.

I wish you a great new year's eve party and a happy new year!

Greetings from Cologne, Helge

[Setacl-devel] Testing

[Kenneth C. <krc...@ms...>]

Looks like the mailing list works.

_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail