John
Mon Nov 22 14:22:12 CST 2004
I'm afraid there is no documentation on these functions. I'll talk with our
docs people to get this added for a future release, but I know it's not
going to help you much now. Sorry.
--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation
Check out the new CE Networking Team Blog at
http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.
"Brian Price" <brianprice@appliedcs.com.au> wrote in message
news:cf046cbf.0411212010.b20f51@posting.google.com...
> Thanks John
>
> I played around with this a bit and got the authentication to work for
> Web, Telnet, and FTP.
>
> One question on the NTLMSSP module.
>
> Is there any documentation (except as implied in NatAdmin) on the
> functions that this module exports:
> NTLMGetUserInfo
> NTLMSavePassword
> NTLMAddGroup
> NTLMRemoveGroup
> NTLMEnumGroups
> NTLMAddUserToGroup
> NTLMRemoveUserFromGroup
> NTLMGetUserList
> NTLMGetGroupList
>
> Regards
> Brian Price
> "John Spaith [MS]" <jspaith@ONLINE.microsoft.com> wrote in message
> news:<eukaHmZzEHA.2572@tk2msftngp13.phx.gbl>...
>> I've tried to come up with a high-level overview of HTTPD auth at the CE
>> Networking blog at
>>
http://blogs.msdn.com/cenet/archive/2004/09/21/232604.aspx. The magic
>> API
>> to create users on the CE box is NTLMSetUserInfo().
>>
>> Also in Platform Builder we have sample code that shows an ISAPI
>> extension
>> to configure a headless gateway device. It initially does not require a
>> password, but prompts the first user to enter password stuff. Then the
>> ISAPI changes the web server such that future accesses require password
>> access. In CE 4.2 this lives in
>> %_WINCEROOT%\public\servers\sdk\samples\natadmin.
>>
>> We completely re-did it, with a much nicer and more extensible UI, for CE
>> 5.0. NatAdmin was retired completely, and now the code lives in
>> %_WINCEROOT%\public\servers\oak\samples\RemoteAdmin.
>>
>> If you have more specific questions let me know.
>>
>>
>> --
>> John Spaith
>> Software Design Engineer, Windows CE
>> Microsoft Corporation
>>
>> Check out the new CE Networking Team Blog at
>>
http://blogs.msdn.com/cenet/.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use. © 2003 Microsoft Corporation. All
>> rights
>> reserved.
>>
>> "Brian Price" <brianprice@appliedcs.com.au> wrote in message
>> news:cf046cbf.0411172159.687755ca@posting.google.com...
>> > Hi All,
>> >
>> > I have had trouble resolving this issue by studying the documentation
>> > and experimenting.
>> >
>> > Ideally, with regards to a windows CE.NET (V4.2) based device we would
>> > like to provide password based security for Web access, telnet access,
>> > etc. This password and user information should only reside on the
>> > device.
>> >
>> > I know that there are registry settings related UserList for the web
>> > server.
>> >
>> > The device is stand-alone, and may or may not be part of a domain.
>> >
>> > So, how do I secure the http site on one of these boxes so that a user
>> > is authenicated before using the web interface.
>> > This is the sort of functionality provided on cable and ADSL
>> > routers/modems.
>> >
>> > Thanks in advance
>> > Brian Price