September 2005 - Wine-Devel

Re: include/guiddef.h: C++ compatibility patch (with MSVC++ support)

by Dmitry Timoshkov

"Troy Rollo" <wine(a)troy.rollo.name> wrote: > --- include/guiddef.h (revision 26053) > +++ include/guiddef.h (local) > @@ -35,12 +35,18 @@ > #undef DEFINE_GUID > > #ifdef INITGUID > +#ifdef __cplusplus > #define DEFINE_GUID(name, l, w1, w2, b1, b2, b3, b4, b5, b6, b7, b8) \ > + EXTERN_C const GUID name = \ > + { l, w1, w2, { b1, b2, b3, b4, b5, b6, b7, b8 } } > +#else > +#define DEFINE_GUID(name, l, w1, w2, b1, b2, b3, b4, b5, b6, b7, b8) \ > const GUID name = \ > { l, w1, w2, { b1, b2, b3, b4, b5, b6, b7, b8 } } > +#endif > #else > #define DEFINE_GUID(name, l, w1, w2, b1, b2, b3, b4, b5, b6, b7, b8) \ > - extern const GUID name > + EXTERN_C const GUID name > #endif > > #define DEFINE_OLEGUID(name, l, w1, w2) \ There are 2 problems with this patch: you forgot to provide a definition for EXTERN_C, and it needlessly duplicates code for the __cplusplus case. -- Dmitry.

Sept. 2, 2005

Re: proper nt-style authentication (reactos, wine, samba tng)

by Robert Shearman

Luke Kenneth Casson Leighton wrote: >that you - the wine team - continue to reinvent an non-interoperable >version of MSRPC, for binary-level "DCOM" interoperabiltiy ONLY, >demonstrates quite how just as bloody stupid you are being. that _can_ >be taken as a compliment, as i genuinely i mean it with the greatest of >respect. > > Ok, I want to condense your huge message into a numbered list of things you say we need: 1. Type marshaling. 2. IDL compiler. 3. RPC Server. 4. Authentication. 5. Services (lsa, netlogon, samr, etc). Ok, so we are we at with Wine and ReactOS? 1: We need to implement this anyway because, like you crudely put it, we are in the crazy business of getting real code like InstallShield and Office 2003 to work. 2. We can either use MIDL and accept the problems that go with it (like not generating code that will compile with gcc 4.0) or we can finish implementing proxy support in widl. 3. We have support for named pipes in the RPC server, but Wine doesn't support remote named pipes and AFAIK ReactOS doesn't either. This is not a problem that should be solved by the RPC runtime. 4. Kai and Juan are working on delegating NTLM authentication to Samba. We still need to tie this in to the RPC server though. That should be a trivial task in comparison. Not sure how this will fit in on ReactOS. 5. Wine isn't really interested in having those types of servers, but it would be nice for the client code for those to work. I'm not sure that porting them from Samba would be fruitful as they would fundamentally need to tie into the registry. So, what you are suggesting is that we instead port FreeDCE and use it for 1-3 (and 4?). This while still having to implement (1) anyway because of the applications I mentioned that need it. Then we get to test two different MSRPC infrastructures and get to fix bugs in one without it fixing any bugs in the other. Just porting FreeDCE seems like a lot of work; perhaps more work than implementing the remaining features in our own MSRPC infrastructure, even when including the task of finishing the IDL compiler. Maybe I am being blind, but it seems to make sense just to carry on in the direction we are going with having our own MSRPC implementation and being able to "dogfood" our implementation (i.e. use it for our own proxies/stubs at the same time as letting applications use it). -- Rob Shearman

Sept. 2, 2005

Re: Web Server Back Online

by Saulius Krasuckas

* On Thu, 1 Sep 2005, Jeremy Newman wrote: > * On Thu, 2005-09-01 at 23:43 +0100, Richard Cohen wrote: > > > > Dont't you mean text/x-patch? > > Right, I added both. Since some pass it as text/x-patch, and some pass > text/x-diff. \m/ Works fine for me. Big thanks.

Sept. 2, 2005

Re: Web Server Back Online

by Ron Jensen

Sorry it took longer to retry the test. Had to work some. Let's see what mailman does this time... Ron

Sept. 2, 2005

Re: proper nt-style authentication (reactos, wine, samba tng)

by David Johnson

I love for this great idea and I put it to the ROS DEV..... Please consider doing every bit of it. XXXOOO Dave On 9/1/05, Luke Kenneth Casson Leighton <lkcl(a)lkcl.net> wrote: > [please note: due to its cross-discipline and cross-project nature, > this message is going out to SEVERAL related project mailing lists. > when replying, please take EXTRA caution not least because some of > these lists are subscriber-only. also, please note: i _would_ > post this also to the samba mailing lists but due to the fascist > censorship in place since the 15th dec 2004, i am unable to do so. > this is their decision and it is their loss. i am not asking you > to respect that decision i am simply making you aware of it.] > > hi, > > out the woodwork i pop - not necessarily ready to chew anything because > i know just how much work's involved, but what i did want to do was > say "hi, i'm still here" and do a brain-dump of how authentication > ideally needs to be implemented in reactos. > > at 2,600 words and 16k, this message is quite long and so i have > placed a copy at http://lkcl.net/software/reports/reactos-auth.txt, > just in case it doesn't make it past various mailing-list limits > (i'll find out in a couple of minutes... :) > > it breaks down into a number of sections: > > 1) i describe the timescales and ways to cut them, > along with some warnings and stuff. > > 2) amonst other stuff i outline some background as to > why i am posting this to so many lists. > > 3) i outline a project plan and the dependencies > and "optional" steps, > > 4) i describe a recommended implementation > roadmap starting with the "minimum" requirements, > and expand on some technical info and references > i found, which would help with some of the > "nice-to-have" steps. > > so. first. > > please do not be scared by how much work is involved, and how much code > there is. it all hinges one ONE function and that one function... you > are _not_ going to believe how much code that one function drags in, > kicking and screaming, behind it. > > please also please i beg you DO NOT consider going "bleedin 'ellfire, > that's so much frakkin work we can't POSSIBLY do it the way you > describe, we MUST do it our own way, starting with what we know, love > and have already started tackling, and can't possibly back out of what > we've already done". > > should you choose to exercise the "NIH" option, i frakkin > guarantee you that you will waste about five to eight years > of your (collective) lives reinventing the wheel. > > "The Plan" outlined here will shave that down to about 12 to 18 months, > utilising some SIX HUNDRED THOUSAND lines of pre-existing code, and > later in this message i also outline a prioritisation of the necessary > work to "cut down" the time to maybe about ... mmm... three or so > months, by leaving out some of the "nice-to-have" stuff. actually... > _all_ of the nice-to-have stuff :) > > that will at least "GetItWorking(tm)" and the rest of the bits > can be considered at leisure once people go "god that's awful, > we can't possibly leave it like that" and hopefully hopefully > things will actually progress from there. > > remember - please: this stuff is sufficiently complicated such that > you really can't afford the niceties such as "It Must Be Perfect (tm)" > before it can be accepted. i've seen that shit before, and it's > a baad mxxxxxxxer path to go down, especially with such complex > and heavily interdependant reverse-engineering projects as reactos, > wine, samba and freedce. > > anyway. > > fyi - before i begin, i should mention a couple of things: > > 1) this message also goes out the the apache devel mailing > list (specifically the APR one) because the NT style > authentication thing is the sort of thing that really _should_ > be in a (special?) APR util library, along with "NT Named Pipes" - > see http://en.wikipedia.org/wiki/NamedPipes > > one of the reasons why NT-style NamedPipes is _not_ in an APR util is > because it is believed that NT-style NamedPipes do not fit the > "least common denominator". by having the infrastructure outlined > below, it is possible to move things "up one level" to the point > where unix _has_ that denominononmination. > > also, if APR still has support for that god-awful program-running > program called Win95, it would, with not much extra effort, be > possible to port some reactos components to Win95 (!) such that > ThePlan outlined here would make Win95 have proper NT-style > authentication (!) now there's a horrible thought that will give > MS and free software people nightmares both: upgrading Win95 by > installing free software components at it. muhahahahah ahem. > > 2) i have filled in a number of pages on wikipedia.org. see > http://en.wikipedia.org/wiki/User:lkcl. please take the time to > review these pages, PLEASE help me with my totally biased "POV" > (point-of-view) comments, by either editing the pages direct or by adding > comments on the "talk" pages as appropriate. or alternatively dumping > me in the nearest pond if ever you meet me. > > wikipedia is supposed to be encyclopedia-ic and some of my > comments are anything but that. > > help!!! > > 3) please due to the quite broad distribution of this message across > multiple mailing lists, please do NOT ask stupid questions like > "what the hell do we need to use samba tng for, why can't we use samba > in reactos"? and "why is this guy bothering us with this insane stuff?" > and "how do i use killfiles?" or terry pratchett's - more specifically > the librarian's favourite - "where has all the pie and custard gone?" > > please do your research: see if nothing else > http://en.wikipedia.org/wiki/Samba_TNG_software and then start googling. > > > anyway. > > onward. > > roughly in order of dependence, with "nice-to-have" status added as > well: > > 1) port FreeDCE to Win32 - more specifically add in autoconf support for an > alternative threading model - the one in reactos. no, this is not a joke: > MSRPC is a critical part of NT infrastructure it's just that very few > people > are actually aware of this (including the US DoJ and the EU commission...) > > see http://www.google.co.uk/search?q=lkcl+wine+freedce for discussion > links as to why - it's a long story and it took me several dozen > messages spanning over many days to outline it in sufficient detail > for it to be understood (mostly me getting things straight in my > head...) > > status: "nice to have" but you will soon wish that you _did_ have it!!! > > there is also an opportunity to support Wine, here: essentially > it's the same job, for DCOM, for proper "authentication" > purposes in Wine just like in ReactOS... it's a long story. > > 2) remove dependence on "unix" security model from Samba TNG's services > starting with samrd (perhaps by finishing off samrtdbd?) > > status: "essential". > > sub-projects: > > a) in Samba TNG, rework winbindd such that it is a REQUIRED service, > and it has "modes" that, instead of "inventing" links between > unix uids and nt sids, it reads smbpasswd and correlates unix uids > with nt sids _just_ like is done now - but hard-coded through > the awful code that has had to dieee since... about two weeks after > i wrote it, back in 1999. > > this one's a long story but it's not actually required for > reactos but _might_ be required for wine... > > status: "pretty much essential" but not for reactos but for making life > easy to share tng development between reactos and unix. > > b) in Samba TNG, make the authentication code (smb-side and rpc server > back-end-wise) contact winbindd BUT ONLY for resolving unix uids and > unix gids - which is actually a VERY small task involving a few > hundred lines of code. > > this goes back to the "SURS" stuff i wrote up in 1999 - but instead > of a library it hands off the responsibility for sid<->uid+gid > lookups to winbindd. > > it _may_ also be essential for Wine to operate correctly > with authentication (which is a "stub" at the moment just > like it is in reactos), to interoperate with other programs, > to cache login credentials in order to do smb client-side > operations, that sort of thing, under which circumstances, > it will be necessary for Wine to have the same sort of thing. > > it's no big deal :) > > status: same as for 2a). > > c) in Samba TNG, abandon all use of hard-coded MSRPC stuff and utilise > FreeDCE instead, and do a rewrite of all services, one by one > (and because samba tng is modular, this _can_ be done one-by-one, > checking MSRPC interoperability along the way between the "old" > services, the "new" services, and also with NT itself). > > in and of itself, this critically depends on making > DCEThreads reliable, though, or adding support (finally!) for > POSIX threads. > > status: "non-essential" but you would soon end up wishing that you had :) > > 3) complete LsaLogonUser, add LsaLogonUserEx, in NTOSKRNL.DLL, and > friends. > > my favourites. the LSASS stuff. > > these functions are quite simple: they are "redirectors" - a vector > table of functions is required to be passed in, which includes things > like "authenticate with my lovely service" and "free some memory". > > there are many LSASS sub-services: one of them is Netware, one of > them is MSV1_0.DLL, one of them is Kerberos. > > there are others. > > LSASS is based on _exactly_ the same technique that dlopen does e.g > in libdvdcss, and in freedce's ntlmsspauth.so, and in... mmm... > the freedce transport module infrastructure and _many_ other > projects ... except of course it's NT-based table of > higher-order-functions not unix "dlopen()" ones. > > i'll stop trying to teach people to suck eggs, now *embarrassed* :) > > status: "essential". > > sub-projects: > > a) write an MSV1_0.DLL which registers with the LSASS service. > this will utilise MSRPC functions that call into the Samba TNG > "NETLOGON" service. > > there already exists "basic" functions inside Samba TNG that... > well... it's a bit messy, but they work. > > the key function to be calling is cli_nt_login_interactive, > and you will notice _very_ quickly from the arguments hey, some > of those look... kinda... familiar!! > > see > http://viewcvs.samba-tng.org/cgi-bin/viewcvs.cgi/tng/source/rpc_client/cli_… > > status: "essential." > > the "porting" bit of this code to FreeDCE i would classify as > "non-essential" but again, you will soon wish that you _were_ using > FreeDCE. > > > > that's basically it: there are other sub-projects such as > turning the "Registry" code in ReactOS (or Wine) into an MSRPC > service (yes, i did say pretty much everything that's anything > critical in NT is an MSRPC service, didn't i? :) but they aren't > "essential". > > i say basically it, but that ONE stupid function, cli_nt_login_interactive, > drags in quite literally HALF A MILLION lines of code - 250,000 lines of > it in FreeDCE, alone (which, like i said, could possibly be avoided but > the hard-coded MSRPC stuff in samba tng is sufficiently awkward to make > a rewrite utilising FreeDCE very attractive). > > > > what i would suggest is the following: > > 1) write an MSV1_0.DLL "test stub" in combination with completing the > LSASS functions, which supports a username "test", domain of "test" and > password of "test". > > code up a hard-coded "blob" - a NET_USER_INFO_3 structure - that contains > the response / essential information of groups, gids, sids, user session > key etc. > > see > http://viewcvs.samba-tng.org/cgi-bin/viewcvs.cgi/tng/source/include/rpc_net… > > (note: i _did_ say it would be nice to utilise FreeDCE didn't i? well, > the NET_USER_INFO_3 structure in that header file is a "messy" version that > i recreated from off-the-wire back in about ... mmmm... 1997. there > _do_ exist IDL-generated versions of this data structure, thanks to > matthew chapman - NETLOGON.idl for example). > > once that works... > > 2) write a lovely insecure method of "outsourcing" the username, > domain and password to an external server - Samba TNG - which performs > the authentication on your behalf and gets back "real" data. > > this could be done simply with a TCP connection, throw the data > in-the-clear over to a simple temporary shim service blah blah, > bob's your uncle. > > 3) port samba tng's netlogond, samrd and lsarpcd to ReactOS. > > this is quite straightforward: about the only really essential > "missing" bit is to tie the services in to "NT Named Pipes" rather > than unix domain sockets. > > _but_ - they only need to be plugged in to a back-end transport > which all services - any of samba tng's MSRPC services - would > use. so there's a key bit of work needed - probably under > 400 lines of code - and the rest should fall into place. > > this is where it would be SO much easier to be utilising FreeDCE. > > all that's needed would be to write a FreeDCE "transport" > plugin for ReactOS - ncacn_np - and then you'd be DONE. > > it's a long story... > > hey, has someone implemented TransactNamedPipe() and CreateNamedPipe() > in ReactOS? > > if not, it's quite straightforward to do, and it involves dropping > opaque data blobs onto smbd (again, smbd ported to reactos...) > > i _did_ say it's a long story, didn't i? :) > > 4) finally: track down how "LsaLogonUserEx" works. LsaLogonUser > utilises cleartext passwords. LsaLogonUserEx i BELIEVE utilises NT and > LM password hashes, or some brain-dead encrypted variant thereof. > > once 1) is completed, then TA-DAAAAA!!! lib/secur/lsa.c's "LsaLogonUser" > function actually gets REAL DATA! > > > okay. > > notes: > > 1) regarding FreeDCE. see http://en.wikipedia.org/wiki/FreeDCE > > freedce is an interoperable version of MSRPC that is derived from > EXACTLY the same source code (DCE 1.0 reference implementation) that > is present in Windows NT. > > DCE/RPC was co-opted / adopted / borg-ified by microsoft to form > the basis of NT domains because paul leach, a co-founder of > apollo computers and originator of NCS which became DCE/RPC, > ended up working for microsoft back at the time when dave > cutler was doing the original NT 3.1. > > using FreeDCE is non-essential for small projects of less than about > 8,000 lines of code. Samba TNG's MSRPC code comprises OVER ONE HUNDRED > THOUSAND lines of code. > > that i carried on hand-crafting MSRPC packets for three years simply > demonstrates quite how bloody stupid i am. > > that you - the wine team - continue to reinvent an non-interoperable > version of MSRPC, for binary-level "DCOM" interoperabiltiy ONLY, > demonstrates quite how just as bloody stupid you are being. that _can_ > be taken as a compliment, as i genuinely i mean it with the greatest of > respect. > > 2) regarding a strategy to "minimise" the amount of time needed to > "Get Things Working". > > a) utilise samba tng as-it-is, porting it as-is to ReactOS (mingw32) > b) utilise cli_nt_login_interactive() as-it-is. > c) complete MSV1_0.DLL. > > this will be SUFFICIENT and would only take a few months. enhancements > come later, roughly in this order: > > a) complete a port of FreeDCE to ReactOS, by beating DCEthreads to > death and replacing it with Win32 (NT) threads - #ifdef style, > autoconf style. > > b) locate NETLOGON.idl, samr.idl and lsarpc.idl from matthew chapman's > stuff, or from "todd sabin's" http://razor.bindview.com, or from > the samba web site. > > actually... see: http://www.bindview.com/services/razor/utilities/ > > compile up CLIENT-SIDE ONLY, using dceidl, and create a > library for use inside MSV1_0.DLL. > > i know todd developed interoperable versions of these idl files, > because he was using them, compiled with MIDL.EXE, to do security > tests against NT 4.0. remember: these IDL files are what microsoft > DOESN'T want anyone to have, and there are very good _legitimate_ > reasons for it: they are "behind-the-scenes" APIs which, if some > idiot inside microsoft went and wrote a tool which became publicly > used and relied on, they would be stuffed: they have ENOUGH apis > which date back 15 years and they don't need any more. that > having been said, i hate the fact that they are forcing people > to pay $50k up-front and then $100 per-client for frakkin > _information_. bastards. > > c) replace cli_nt_login_interactive() with a function that utilises > the above library that utilises netlogon, samr and lsarpc client-side > stuff from b) above. > > basically, what it boils down to is that the functions inside > cli_nt_login_interactive i wrote BY HAND after examining MSRPC > traffic. those functions neeeed too dieeee and they can easily > be replaced one-by-one with the "proper" versions from doing > "dceidl -client lsarpc.idl". it takes a couple of seconds and > you get a header file lsarpc.h and a lsarpc.o and you're DONE. > > question. why did i spend so long doing hand-marshalling of the > nt domains code. perhaps because i would not be able to give > microsoft absolute hell for three frakkin years? > > d) consider porting, one-by-one, the Samba TNG services lsarpcd, > netlogond and samrd (or better samrtdbd) to FreeDCE runtime > infrastructure. > > this is NOT essential but it is very worthwhile. every project > needs to do at least two throw-aways and with the samba tng > code, there has been approximately one and a half throwaways > so far... time for a major one, ESPECIALLY in light of the reactos > project. > > FINALLY: > > e) consider writing that winregd service but actually picking up REAL > registry hive files. someone did write a "reader" of registry files, > i do not recall who it was. > > [note: YESSSS!!! yeeeeeehawww, todd i could KISS you!!] > > http://www.bindview.com/Services/RAZOR/Utilities/Unix_Linux/ntreg_readme.cfm > > todd wrote a registry-hive-reader as a linux filesystem driver!!!!! > > todd, you are bloody mad. *smooch*. > > > f) consider writing a samr service with the FreeDCE runtime > that utilises "registry" functions RegXXXX - _properly_. > > > anyway, if you got this far: congratulations and welcome to a brief > nightmare history of the development behind NT Domains Authentication. > > all of the infrastructure above _already_ exists - in Samba TNG. > it's just... it works. it's a bit creaky at the edges, but it works. > > how about it? > > l. > > p.s. it almost goes without saying, but i will hint at it once again: > you will not find the samba team's goals and strategic direction to be > compatible with reactos. as a team, they lack the insight, vision and > project management skills to be able to cope with such inter-dependant > insane gibberish. this i say with much sadness because they are highly > respected individuals in the free software community, and yet they are > taking the samba project in very different - and ultimately > time-consuming - directions from what is really really needed. due > to pride they cannot admit this in public but they have been known > to admit it in private. much much disappointment and sadness and there's > absolutely nothing i can do about it. > > -- > -- > <a href="http://lkcl.net">http://lkcl.net</a> > -- > _______________________________________________ > Ros-dev mailing list > Ros-dev(a)reactos.com > http://reactos.com:8080/mailman/listinfo/ros-dev > -- David Johnson http://www.davefilms.us

Sept. 2, 2005

Re: Web Server Back Online

by Jeremy Newman

Right, I added both. Since some pass it as text/x-patch, and some pass text/x-diff. I haven't seen any complaints about the patches appearing inline, so I assume that it is OK. On Thu, 2005-09-01 at 23:43 +0100, Richard Cohen wrote: > Jeremy Newman wrote: > > Interesting, when it does get the mime type, it inlines it for text > > types. I'll add the mime type text/x-diff to /etc/mime.types and see > > what happens. > > > Dont't you mean text/x-patch? > > Richard > > >

Sept. 2, 2005

proper nt-style authentication (reactos, wine, samba tng)

by Luke Kenneth Casson Leighton

[please note: due to its cross-discipline and cross-project nature, this message is going out to SEVERAL related project mailing lists. when replying, please take EXTRA caution not least because some of these lists are subscriber-only. also, please note: i _would_ post this also to the samba mailing lists but due to the fascist censorship in place since the 15th dec 2004, i am unable to do so. this is their decision and it is their loss. i am not asking you to respect that decision i am simply making you aware of it.] hi, out the woodwork i pop - not necessarily ready to chew anything because i know just how much work's involved, but what i did want to do was say "hi, i'm still here" and do a brain-dump of how authentication ideally needs to be implemented in reactos. at 2,600 words and 16k, this message is quite long and so i have placed a copy at http://lkcl.net/software/reports/reactos-auth.txt, just in case it doesn't make it past various mailing-list limits (i'll find out in a couple of minutes... :) it breaks down into a number of sections: 1) i describe the timescales and ways to cut them, along with some warnings and stuff. 2) amonst other stuff i outline some background as to why i am posting this to so many lists. 3) i outline a project plan and the dependencies and "optional" steps, 4) i describe a recommended implementation roadmap starting with the "minimum" requirements, and expand on some technical info and references i found, which would help with some of the "nice-to-have" steps. so. first. please do not be scared by how much work is involved, and how much code there is. it all hinges one ONE function and that one function... you are _not_ going to believe how much code that one function drags in, kicking and screaming, behind it. please also please i beg you DO NOT consider going "bleedin 'ellfire, that's so much frakkin work we can't POSSIBLY do it the way you describe, we MUST do it our own way, starting with what we know, love and have already started tackling, and can't possibly back out of what we've already done". should you choose to exercise the "NIH" option, i frakkin guarantee you that you will waste about five to eight years of your (collective) lives reinventing the wheel. "The Plan" outlined here will shave that down to about 12 to 18 months, utilising some SIX HUNDRED THOUSAND lines of pre-existing code, and later in this message i also outline a prioritisation of the necessary work to "cut down" the time to maybe about ... mmm... three or so months, by leaving out some of the "nice-to-have" stuff. actually... _all_ of the nice-to-have stuff :) that will at least "GetItWorking(tm)" and the rest of the bits can be considered at leisure once people go "god that's awful, we can't possibly leave it like that" and hopefully hopefully things will actually progress from there. remember - please: this stuff is sufficiently complicated such that you really can't afford the niceties such as "It Must Be Perfect (tm)" before it can be accepted. i've seen that shit before, and it's a baad mxxxxxxxer path to go down, especially with such complex and heavily interdependant reverse-engineering projects as reactos, wine, samba and freedce. anyway. fyi - before i begin, i should mention a couple of things: 1) this message also goes out the the apache devel mailing list (specifically the APR one) because the NT style authentication thing is the sort of thing that really _should_ be in a (special?) APR util library, along with "NT Named Pipes" - see http://en.wikipedia.org/wiki/NamedPipes one of the reasons why NT-style NamedPipes is _not_ in an APR util is because it is believed that NT-style NamedPipes do not fit the "least common denominator". by having the infrastructure outlined below, it is possible to move things "up one level" to the point where unix _has_ that denominononmination. also, if APR still has support for that god-awful program-running program called Win95, it would, with not much extra effort, be possible to port some reactos components to Win95 (!) such that ThePlan outlined here would make Win95 have proper NT-style authentication (!) now there's a horrible thought that will give MS and free software people nightmares both: upgrading Win95 by installing free software components at it. muhahahahah ahem. 2) i have filled in a number of pages on wikipedia.org. see http://en.wikipedia.org/wiki/User:lkcl. please take the time to review these pages, PLEASE help me with my totally biased "POV" (point-of-view) comments, by either editing the pages direct or by adding comments on the "talk" pages as appropriate. or alternatively dumping me in the nearest pond if ever you meet me. wikipedia is supposed to be encyclopedia-ic and some of my comments are anything but that. help!!! 3) please due to the quite broad distribution of this message across multiple mailing lists, please do NOT ask stupid questions like "what the hell do we need to use samba tng for, why can't we use samba in reactos"? and "why is this guy bothering us with this insane stuff?" and "how do i use killfiles?" or terry pratchett's - more specifically the librarian's favourite - "where has all the pie and custard gone?" please do your research: see if nothing else http://en.wikipedia.org/wiki/Samba_TNG_software and then start googling. anyway. onward. roughly in order of dependence, with "nice-to-have" status added as well: 1) port FreeDCE to Win32 - more specifically add in autoconf support for an alternative threading model - the one in reactos. no, this is not a joke: MSRPC is a critical part of NT infrastructure it's just that very few people are actually aware of this (including the US DoJ and the EU commission...) see http://www.google.co.uk/search?q=lkcl+wine+freedce for discussion links as to why - it's a long story and it took me several dozen messages spanning over many days to outline it in sufficient detail for it to be understood (mostly me getting things straight in my head...) status: "nice to have" but you will soon wish that you _did_ have it!!! there is also an opportunity to support Wine, here: essentially it's the same job, for DCOM, for proper "authentication" purposes in Wine just like in ReactOS... it's a long story. 2) remove dependence on "unix" security model from Samba TNG's services starting with samrd (perhaps by finishing off samrtdbd?) status: "essential". sub-projects: a) in Samba TNG, rework winbindd such that it is a REQUIRED service, and it has "modes" that, instead of "inventing" links between unix uids and nt sids, it reads smbpasswd and correlates unix uids with nt sids _just_ like is done now - but hard-coded through the awful code that has had to dieee since... about two weeks after i wrote it, back in 1999. this one's a long story but it's not actually required for reactos but _might_ be required for wine... status: "pretty much essential" but not for reactos but for making life easy to share tng development between reactos and unix. b) in Samba TNG, make the authentication code (smb-side and rpc server back-end-wise) contact winbindd BUT ONLY for resolving unix uids and unix gids - which is actually a VERY small task involving a few hundred lines of code. this goes back to the "SURS" stuff i wrote up in 1999 - but instead of a library it hands off the responsibility for sid<->uid+gid lookups to winbindd. it _may_ also be essential for Wine to operate correctly with authentication (which is a "stub" at the moment just like it is in reactos), to interoperate with other programs, to cache login credentials in order to do smb client-side operations, that sort of thing, under which circumstances, it will be necessary for Wine to have the same sort of thing. it's no big deal :) status: same as for 2a). c) in Samba TNG, abandon all use of hard-coded MSRPC stuff and utilise FreeDCE instead, and do a rewrite of all services, one by one (and because samba tng is modular, this _can_ be done one-by-one, checking MSRPC interoperability along the way between the "old" services, the "new" services, and also with NT itself). in and of itself, this critically depends on making DCEThreads reliable, though, or adding support (finally!) for POSIX threads. status: "non-essential" but you would soon end up wishing that you had :) 3) complete LsaLogonUser, add LsaLogonUserEx, in NTOSKRNL.DLL, and friends. my favourites. the LSASS stuff. these functions are quite simple: they are "redirectors" - a vector table of functions is required to be passed in, which includes things like "authenticate with my lovely service" and "free some memory". there are many LSASS sub-services: one of them is Netware, one of them is MSV1_0.DLL, one of them is Kerberos. there are others. LSASS is based on _exactly_ the same technique that dlopen does e.g in libdvdcss, and in freedce's ntlmsspauth.so, and in... mmm... the freedce transport module infrastructure and _many_ other projects ... except of course it's NT-based table of higher-order-functions not unix "dlopen()" ones. i'll stop trying to teach people to suck eggs, now *embarrassed* :) status: "essential". sub-projects: a) write an MSV1_0.DLL which registers with the LSASS service. this will utilise MSRPC functions that call into the Samba TNG "NETLOGON" service. there already exists "basic" functions inside Samba TNG that... well... it's a bit messy, but they work. the key function to be calling is cli_nt_login_interactive, and you will notice _very_ quickly from the arguments hey, some of those look... kinda... familiar!! see http://viewcvs.samba-tng.org/cgi-bin/viewcvs.cgi/tng/source/rpc_client/cli_… status: "essential." the "porting" bit of this code to FreeDCE i would classify as "non-essential" but again, you will soon wish that you _were_ using FreeDCE. that's basically it: there are other sub-projects such as turning the "Registry" code in ReactOS (or Wine) into an MSRPC service (yes, i did say pretty much everything that's anything critical in NT is an MSRPC service, didn't i? :) but they aren't "essential". i say basically it, but that ONE stupid function, cli_nt_login_interactive, drags in quite literally HALF A MILLION lines of code - 250,000 lines of it in FreeDCE, alone (which, like i said, could possibly be avoided but the hard-coded MSRPC stuff in samba tng is sufficiently awkward to make a rewrite utilising FreeDCE very attractive). what i would suggest is the following: 1) write an MSV1_0.DLL "test stub" in combination with completing the LSASS functions, which supports a username "test", domain of "test" and password of "test". code up a hard-coded "blob" - a NET_USER_INFO_3 structure - that contains the response / essential information of groups, gids, sids, user session key etc. see http://viewcvs.samba-tng.org/cgi-bin/viewcvs.cgi/tng/source/include/rpc_net… (note: i _did_ say it would be nice to utilise FreeDCE didn't i? well, the NET_USER_INFO_3 structure in that header file is a "messy" version that i recreated from off-the-wire back in about ... mmmm... 1997. there _do_ exist IDL-generated versions of this data structure, thanks to matthew chapman - NETLOGON.idl for example). once that works... 2) write a lovely insecure method of "outsourcing" the username, domain and password to an external server - Samba TNG - which performs the authentication on your behalf and gets back "real" data. this could be done simply with a TCP connection, throw the data in-the-clear over to a simple temporary shim service blah blah, bob's your uncle. 3) port samba tng's netlogond, samrd and lsarpcd to ReactOS. this is quite straightforward: about the only really essential "missing" bit is to tie the services in to "NT Named Pipes" rather than unix domain sockets. _but_ - they only need to be plugged in to a back-end transport which all services - any of samba tng's MSRPC services - would use. so there's a key bit of work needed - probably under 400 lines of code - and the rest should fall into place. this is where it would be SO much easier to be utilising FreeDCE. all that's needed would be to write a FreeDCE "transport" plugin for ReactOS - ncacn_np - and then you'd be DONE. it's a long story... hey, has someone implemented TransactNamedPipe() and CreateNamedPipe() in ReactOS? if not, it's quite straightforward to do, and it involves dropping opaque data blobs onto smbd (again, smbd ported to reactos...) i _did_ say it's a long story, didn't i? :) 4) finally: track down how "LsaLogonUserEx" works. LsaLogonUser utilises cleartext passwords. LsaLogonUserEx i BELIEVE utilises NT and LM password hashes, or some brain-dead encrypted variant thereof. once 1) is completed, then TA-DAAAAA!!! lib/secur/lsa.c's "LsaLogonUser" function actually gets REAL DATA! okay. notes: 1) regarding FreeDCE. see http://en.wikipedia.org/wiki/FreeDCE freedce is an interoperable version of MSRPC that is derived from EXACTLY the same source code (DCE 1.0 reference implementation) that is present in Windows NT. DCE/RPC was co-opted / adopted / borg-ified by microsoft to form the basis of NT domains because paul leach, a co-founder of apollo computers and originator of NCS which became DCE/RPC, ended up working for microsoft back at the time when dave cutler was doing the original NT 3.1. using FreeDCE is non-essential for small projects of less than about 8,000 lines of code. Samba TNG's MSRPC code comprises OVER ONE HUNDRED THOUSAND lines of code. that i carried on hand-crafting MSRPC packets for three years simply demonstrates quite how bloody stupid i am. that you - the wine team - continue to reinvent an non-interoperable version of MSRPC, for binary-level "DCOM" interoperabiltiy ONLY, demonstrates quite how just as bloody stupid you are being. that _can_ be taken as a compliment, as i genuinely i mean it with the greatest of respect. 2) regarding a strategy to "minimise" the amount of time needed to "Get Things Working". a) utilise samba tng as-it-is, porting it as-is to ReactOS (mingw32) b) utilise cli_nt_login_interactive() as-it-is. c) complete MSV1_0.DLL. this will be SUFFICIENT and would only take a few months. enhancements come later, roughly in this order: a) complete a port of FreeDCE to ReactOS, by beating DCEthreads to death and replacing it with Win32 (NT) threads - #ifdef style, autoconf style. b) locate NETLOGON.idl, samr.idl and lsarpc.idl from matthew chapman's stuff, or from "todd sabin's" http://razor.bindview.com, or from the samba web site. actually... see: http://www.bindview.com/services/razor/utilities/ compile up CLIENT-SIDE ONLY, using dceidl, and create a library for use inside MSV1_0.DLL. i know todd developed interoperable versions of these idl files, because he was using them, compiled with MIDL.EXE, to do security tests against NT 4.0. remember: these IDL files are what microsoft DOESN'T want anyone to have, and there are very good _legitimate_ reasons for it: they are "behind-the-scenes" APIs which, if some idiot inside microsoft went and wrote a tool which became publicly used and relied on, they would be stuffed: they have ENOUGH apis which date back 15 years and they don't need any more. that having been said, i hate the fact that they are forcing people to pay $50k up-front and then $100 per-client for frakkin _information_. bastards. c) replace cli_nt_login_interactive() with a function that utilises the above library that utilises netlogon, samr and lsarpc client-side stuff from b) above. basically, what it boils down to is that the functions inside cli_nt_login_interactive i wrote BY HAND after examining MSRPC traffic. those functions neeeed too dieeee and they can easily be replaced one-by-one with the "proper" versions from doing "dceidl -client lsarpc.idl". it takes a couple of seconds and you get a header file lsarpc.h and a lsarpc.o and you're DONE. question. why did i spend so long doing hand-marshalling of the nt domains code. perhaps because i would not be able to give microsoft absolute hell for three frakkin years? d) consider porting, one-by-one, the Samba TNG services lsarpcd, netlogond and samrd (or better samrtdbd) to FreeDCE runtime infrastructure. this is NOT essential but it is very worthwhile. every project needs to do at least two throw-aways and with the samba tng code, there has been approximately one and a half throwaways so far... time for a major one, ESPECIALLY in light of the reactos project. FINALLY: e) consider writing that winregd service but actually picking up REAL registry hive files. someone did write a "reader" of registry files, i do not recall who it was. [note: YESSSS!!! yeeeeeehawww, todd i could KISS you!!] http://www.bindview.com/Services/RAZOR/Utilities/Unix_Linux/ntreg_readme.cfm todd wrote a registry-hive-reader as a linux filesystem driver!!!!! todd, you are bloody mad. *smooch*. f) consider writing a samr service with the FreeDCE runtime that utilises "registry" functions RegXXXX - _properly_. anyway, if you got this far: congratulations and welcome to a brief nightmare history of the development behind NT Domains Authentication. all of the infrastructure above _already_ exists - in Samba TNG. it's just... it works. it's a bit creaky at the edges, but it works. how about it? l. p.s. it almost goes without saying, but i will hint at it once again: you will not find the samba team's goals and strategic direction to be compatible with reactos. as a team, they lack the insight, vision and project management skills to be able to cope with such inter-dependant insane gibberish. this i say with much sadness because they are highly respected individuals in the free software community, and yet they are taking the samba project in very different - and ultimately time-consuming - directions from what is really really needed. due to pride they cannot admit this in public but they have been known to admit it in private. much much disappointment and sadness and there's absolutely nothing i can do about it. -- -- <a href="http://lkcl.net">http://lkcl.net</a> --

Sept. 2, 2005

Re: WINEALSA: comment on unexpected shrinking of mmap-buffer (resend)

by Robert Reif

Alex Villacís Lasso wrote: > Robert Reif wrote: > >> Alex Villacís Lasso wrote: >> >>> Robert Reif wrote: >>> >>>> Fix the wine ALSA driver rather than the test unless you can prove >>>> that the test fails on Windows. >>>> >> Hers is a real quick hack that fixes the problem. This should give >> you someplace to start. > Direct sound expects the size of the buffer in bytes to remain constant regardless of the format and the intent of the patch was to show where the changes need to be made. That's the bug that need fixing. I don't have the time to fix this bug properly in the near future so all I could do was give a hint.

Sept. 1, 2005

Re: Web Server Back Online

by Richard Cohen

Jeremy Newman wrote: > Interesting, when it does get the mime type, it inlines it for text > types. I'll add the mime type text/x-diff to /etc/mime.types and see > what happens. > Dont't you mean text/x-patch? Richard

Sept. 1, 2005

Re: curses problems in wineconsole

by Robert Lunnon

On Tuesday 30 August 2005 19:28, Alexandre Julliard wrote: > Robert Lunnon <bobl(a)optushome.com.au> writes: > > curses.c in wineconsole seems to be under (re) development at the moment. > > Under Solaris I get the following. I presume this is because the changes > > are being developed with ncurses in mind. > > Nothing has changed in that code for months. There have been some > changes in the configure script though, so maybe something in the > curses detection has been broken. I have investigated this, it seems that configure has suddenly found the curses library recently under solaris so Solaris has not yet been tested against the curses code in wine. I will need to compose a patch. <sigh> Bob

Sept. 1, 2005

Re: Web Server Back Online

by Jeremy Newman

Interesting, when it does get the mime type, it inlines it for text types. I'll add the mime type text/x-diff to /etc/mime.types and see what happens. Please try this email test again in about 5 minutes. I'm not sure if people want the patches inline, maybe they do? Let me know. On Thu, 2005-09-01 at 11:40 -0600, Ron Jensen wrote: > In reading the FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.046.htp > I came to the impression that the mime-type and extension must match. If they don't > the extension is changed to .bin. > > I checked /etc/mime.types on my etch system and there is no text/x-patch. 'diff' is listed > as a file type under text/plain. > > As an experiment I am attaching an ASCII text file to this e-mail with a .txt and a .diff > extention, each file will get a mime type of text/plain and text/x-patch. > > Let's see what mailman does... > > Ron >

Sept. 1, 2005

Re: Web Server Back Online

by Jeremy Newman

Try that, let me know if it's better. Note: web browses cache mime type as well, so try a different .bin if needed. I'll try it for now. I played with mod_mime_magic as well, but was unable to get any joy out of it. It is supposed to do what the command 'file' does and get the mime type based on the contents of the file. Didn't seem to work though. On Thu, 2005-09-01 at 10:49 -0500, Robert Shearman wrote: > Could you configure .bin files to have a MIME type of text/x-diff or > something in Apache? Maybe just for the mailman directory if there are > other .bin files on the web site. >

Sept. 1, 2005

Re: uxtheme requiring shlwapi

by Aric Stewart

Great thanks, missed that patch. -aric Frank Richter wrote: >On 01.09.2005 15:59, Aric Stewart wrote: > > >>Any chance these changes could be made? >> >> > >Actually, some chaps in #winehackers asked for the same already ;) : >http://www.winehq.org/pipermail/wine-patches/2005-August/020373.html > >-f.r. > > > > >

Sept. 1, 2005

Re: Web Server Back Online

by Ron Jensen

In reading the FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.046.htp I came to the impression that the mime-type and extension must match. If they don't the extension is changed to .bin. I checked /etc/mime.types on my etch system and there is no text/x-patch. 'diff' is listed as a file type under text/plain. As an experiment I am attaching an ASCII text file to this e-mail with a .txt and a .diff extention, each file will get a mime type of text/plain and text/x-patch. Let's see what mailman does... Ron

Sept. 1, 2005

Re: KERNEL: check for NULL in LoadModule16

by Alex Villacís Lasso

Andreas Mohr wrote: >Hi, > >On Mon, Aug 29, 2005 at 01:43:04PM -0500, Alex Villacís Lasso wrote: > > >>I could not find any MSDN reference on any documented behavior for >>LoadLibrary16 or LoadModule16 when libname == NULL. >> >> > >I've checked it now (Watcom, Win98 SE): > >(forgot to zero LOADPARAMS, sorry! But it hopefully didn't matter...) > >a) NULL, &lp 0 "system out of mem/executable corrupt/relocs invalid" >b) "kernel", NULL kernel handle >c) NULL, NULL 0 >d) (char *)0x1, &lp 2 "file not found" >e) (char *)0x1256, NULL 2 >f) NULL, (void *)0x1257 0 > >NO CRASHES whatsoever, IOW it fully intercepts any invalid pointers. > >a), c), f) vs. d) indicates that it does an explicit check against a NULL name, >since probably otherwise LoadModule16 will continue due to the non-NULL >name (0x1) and notice somewhat later (in some file API) that file name 0x1 >is invalid. > > The attached patch should implement the observed behavior in Win98SE. Alex Villacís Lasso Changelog: - Add NULL and exception handler to LoadModule16 to check against NULL or invalid libname

Sept. 1, 2005

Re: WINEALSA: comment on unexpected shrinking of mmap-buffer (resend)

by Alex Villacís Lasso

Robert Reif wrote: > Alex Villacís Lasso wrote: > >> Robert Reif wrote: >> >>> Fix the wine ALSA driver rather than the test unless you can prove >>> that the test fails on Windows. >>> > Hers is a real quick hack that fixes the problem. This should give > you someplace to start. > >------------------------------------------------------------------------ > >? audio.c.test >? audio.diff >Index: audio.c >=================================================================== >RCS file: /home/wine/wine/dlls/winmm/winealsa/audio.c,v >retrieving revision 1.96 >diff -p -u -r1.96 audio.c >--- audio.c 12 Aug 2005 11:17:54 -0000 1.96 >+++ audio.c 31 Aug 2005 00:59:33 -0000 >@@ -2527,14 +2527,16 @@ static DWORD wodOpen(WORD wDevID, LPWAVE > getFormat(wwo->format.Format.wFormatTag)); > > dir=0; >- EXIT_ON_ERROR( snd_pcm_hw_params_set_buffer_time_near(pcm, hw_params, &buffer_time, &dir), MMSYSERR_INVALPARAM, "unable to set buffer time"); >+// EXIT_ON_ERROR( snd_pcm_hw_params_set_buffer_time_near(pcm, hw_params, &buffer_time, &dir), MMSYSERR_INVALPARAM, "unable to set buffer time"); >+ buffer_size = 0x10000; >+ EXIT_ON_ERROR( snd_pcm_hw_params_set_buffer_size_near(pcm, hw_params, &buffer_size), MMSYSERR_INVALPARAM, "unable to set buffer size"); > dir=0; > EXIT_ON_ERROR( snd_pcm_hw_params_set_period_time_near(pcm, hw_params, &period_time, &dir), MMSYSERR_INVALPARAM, "unable to set period time"); > > EXIT_ON_ERROR( snd_pcm_hw_params(pcm, hw_params), MMSYSERR_INVALPARAM, "unable to set hw params for playback"); > > err = snd_pcm_hw_params_get_period_size(hw_params, &period_size, &dir); >- err = snd_pcm_hw_params_get_buffer_size(hw_params, &buffer_size); >+// err = snd_pcm_hw_params_get_buffer_size(hw_params, &buffer_size); > > snd_pcm_sw_params_current(pcm, sw_params); > EXIT_ON_ERROR( snd_pcm_sw_params_set_start_threshold(pcm, sw_params, dwFlags & WAVE_DIRECTSOUND ? INT_MAX : 1 ), MMSYSERR_ERROR, "unable to set start threshold"); > > From what I could see from the patch, it tries to set a buffer size instead of a buffer time. However, the patch did not solve the problems as it is. First, the patch supplies a constant value for snd_pcm_hw_params_set_buffer_size_near(). However, the ALSA documentation states that the parameter for buffer_size for this function is given in *frames*, not bytes. Since a frame (nChannels * bitsPerSample / 8) can be from 1 to 4 bytes depending on the requested format, this patch only fixes the frame length, not the byte length. So the attached patch divides the required buffer size (in bytes) by the frame size to arrive to the buffer size in frames. Second, even after the division, the ALSA API is unable to honor the exact value required (at least in my hardware). For most formats the upper limit on the byte size is 30104 bytes, but for the reference tone it changes to 15052 bytes. So it triggers the buffer resize all over again. The attached patch hardcodes the value of 15052 bytes (0x3acc) as the required buffer size, and then the ALSA API doesn't resize the buffer. But obviously, this is a machine-dependent value that might be different in everybody else's machine. Any other value greater than 15052 triggers the buffer resize, and other values below it cause awful buzzings and silences on the games I have tested. Even the chosen value of 15052 bytes, though it works in the tested games, causes buzzings instead of the proper tone on some 8000Hz and 11050Hz tests (the tests where the playtime is around 100-300 ms instead of 1000 ms in the attached trace). Third (but this is no longer a winealsa issue), I still get the critical section timeouts on invalid threads in aprox. 1 in 5 runs of the interactive dsound test, even on an idle CPU. This proves that the timeout bug is not because of CPU load, and should be investigated further. All of this leads me to think that the winealsa driver should give up on trying to provide access to the direct mmap buffer, and revert to providing a fixed-size buffer that is then used to feed the actual ALSA buffer. This would a) hide the buffer resizes from the tests and the games, and b) remove the need of the undocumented hardware pointer function. In fact, I do not remember what was the rationale behind switching from the old model to the current one. In addition, I have tested a few games Any comments on this are welcome. Alex Villacís Lasso

Sept. 1, 2005

Re: Web Server Back Online

by Saulius Krasuckas

* On Thu, 1 Sep 2005, Jeremy Newman wrote: > * On Thu, 2005-09-01 at 12:18 +0300, Saulius Krasuckas wrote: > > If you are serious about taking on this issue. The best place to go is > to check out the mailman CVS at: > http://www.gnu.org/software/mailman/ Thanks. > as policy I only use binary packages in the Debian stable tree. So even > if your patch gets approved I won't see it until the next Debian goes > stable. That would be 'etch' BTW. This means all the world is restricted from reading about a half of sent patches through a web for some lengthy time, maybe a year. Right? :-( OTOH, maybe my FF can be configured to treat *.bin files from winehq.org as .diff files (X-PATCH). If someone know of such solution, alert me, please.

Sept. 1, 2005

Re: uxtheme requiring shlwapi

by Frank Richter

On 01.09.2005 15:59, Aric Stewart wrote: > Any chance these changes could be made? Actually, some chaps in #winehackers asked for the same already ;) : http://www.winehq.org/pipermail/wine-patches/2005-August/020373.html -f.r.

Sept. 1, 2005

Re: Web Server Back Online

by Jeremy Newman

On Thu, 2005-09-01 at 12:18 +0300, Saulius Krasuckas wrote: > * On Wed, 31 Aug 2005, Jeremy Newman wrote: > > * On Wed, 2005-08-31 at 19:24 +0300, Saulius Krasuckas wrote: > > The only way to work around that is for pipermail to use a cgi program > > which would send the correct mime type when you download a file. > > What programming language would be appropriate here? > And how much lines approximately would such program take? If you are serious about taking on this issue. The best place to go is to check out the mailman CVS at: http://www.gnu.org/software/mailman/ Mailman (and Pipermail) are written in Python. I have no idea how many lines this would take, but it shouldn't be all that hard. Please note, as policy I only use binary packages in the Debian stable tree. So even if your patch gets approved I won't see it until the next Debian goes stable. That would be 'etch' BTW.

Sept. 1, 2005

uxtheme requiring shlwapi

by Aric Stewart

Thanks for the great work on this! It is really cool, however I am having a dependency problem that would be great to resolve. uxtheme currently links in shlwapi.dll, shlwapi.dll in turn links in ole32.dll. Since WM_NCCREATE seems to load uxtheme it would be that ole32 is being loaded almost all the time now. This is an issue because when we here at CodeWeavers try to install dcom95.exe we need to set ole32=native (ie, disabled) so that dcom95 does not detect the builtin version. However because uxtheme is now being loaded with MessageBoxA, the install fails because it is unable to load ole32, thus shlwapi and thus uxtheme. Looking at uxtheme it seems like there are only 3 functions being used out of shlwapi. StrChrW: this is also located in comctl32.dll, while i hate to add comctl32.dll as a dependency to swap out shlwapi, it does solve the current problem, also a quick reimplementation of StrChrW as a helper function would remove this problem totally. SHRegGetPathW and PathAddBackslashW: These are really convenient functions but should not be hard to make little helper functions to replace the dependency. Any chance these changes could be made? Thanks alot, -aric

Sept. 1, 2005

Re: Wine device drivers proposal

by Damjan Jovanovic

--- Evgeny F <johnlen(a)yandex.ru> wrote: > Damjan Jovanovic <dj015(a)yahoo.com> wrote: > > > What "microdriver" are you talking about? Are you > > working on STI? For STI, there is a convention for > > Windows 2000 and onwards, something like > > \\.\USBSCAN\... (check the STI documentation on > MSDN). > > > > If it's STI, I have some code; do you want it? > > Yes, it is scanner microdriver. > > Yes, boundaries absolutely must be preserved, > because > > USB bulk reads and writes occur in packets, not as > > streams. How are you going to extract packets from > a > > stream at the other end? > > There are some new type of socket, present since > 2.6.4 kernel described > in unix(7) manual page - SOC_SEQPACKET, which is > both > connection-oriented and preserves message > bounderies. Will it work for > that purpose > No. Here's why: Your microdriver has a socket, and wine has a socket connected to that socket. When wine writes, your microdriver gets packets, and your microdriver can extract the boundaries and use the packets. But what happens when wine wants to read from the socket? How do you know to read from the scanner and send wine the packet, and what size that packet should be? You don't. Reading a USB pipe is a synchronous pull protocol and sockets use an asynchronous push protocol. That is why sockets can't be used. I've given this some thought, and wine needs to be changed. Drastically. Look at the hacks in ntdll/cdrom.c, kernel/volume.c and many others - the current handle system is coming apart at the seams. My advice is to add handle "types" eg. a file handle, cdrom handle, device handle, ..., with each handle being a pointer to something like: struct Handle { DWORD (*ReadFile)(VOID *buffer, DWORD size); DWORD (*WriteFile)(VOID *buffer, DWORD size); DWORD (*DeviceIoControl)(VOID *buffer, DWORD size); ... }; and have the ReadFile(), WriteFile() and DeviceIoControl() simply call the function pointers in the handle. That way it would be trivial to add a new device driver type of thing into wine: write new functions, and change CreateFile() to initialize handles for that device type with the right combination of function pointers. What do you think? ____________________________________________________ Start your day with Yahoo! - make it your home page http://www.yahoo.com/r/hs

Sept. 1, 2005

Re: Web Server Back Online

by Saulius Krasuckas

* On Wed, 31 Aug 2005, Jeremy Newman wrote: > * On Wed, 2005-08-31 at 19:24 +0300, Saulius Krasuckas wrote: > > > > Still winehq server/mail-manager converts the type to > > "application/octet-stream". > > Pipermail stores all attachments in as .bin files. > .. > When you click the link, apache sees .bin, which will always return a > mime type of application/octet-stream. Ok, I am still new to apache. :-] I wonder, can't Pipermail store all attachments here as .diff files? BTW, that would encourange users not to send .bz2 files. :-P > The only way to work around that is for pipermail to use a cgi program > which would send the correct mime type when you download a file. What programming language would be appropriate here? And how much lines approximately would such program take?

Sept. 1, 2005

Re: include/guiddef.h: C++ compatibility patch

by Troy Rollo

On Thu, 1 Sep 2005 14:30, Steven Edwards wrote: > Well yes some of us do. I work to keep the Wine SDK compatible with > the PSDK because we have developed a MSVC backend in the ReactOS build > system and one day (God willing) I will get the ReactOS Project to use > Wine headers rather than w32api headers. As such it needs to be able > to compile applications on MSVC and gcc. OK. I'll submit a version that can deal with this as well after I've tested it (should be some time tomorrow).

Sept. 1, 2005

Re: include/guiddef.h: C++ compatibility patch

by Steven Edwards

Hi, On 8/31/05, Troy Rollo <troy(a)rollo.com> wrote: > 'extern "C"' on a non-member non-function global is perfectly meaningless to > most C++ compilers. As far as I am aware, only MSVC++ mangles global > variables. The 'extern "C"' is thus there to deal with a broken feature of > the MSVC++ compiler, and is not applicable here unless somebody wants to > compile C++ for Winelib using MSVC++ without the PSDK - something which I > suspect would have many more obstacles in its path than just this. Well yes some of us do. I work to keep the Wine SDK compatible with the PSDK because we have developed a MSVC backend in the ReactOS build system and one day (God willing) I will get the ReactOS Project to use Wine headers rather than w32api headers. As such it needs to be able to compile applications on MSVC and gcc. Thanks Steven

Sept. 1, 2005