wine-devel

wine-devel@winehq.org

4 participants
84472 discussions

RFC: Wine and PAM integration
by Andriy Palamarchuk 26 Sep '02

26 Sep '02

I played a couple of days with PAM (Pluggable Authentication Modules). I do not have big experience in this area and want to know your opinion about my ideas. *** PAM short explanation *** PAM <From PAM for Linux documentation> Linux-PAM (Pluggable Authentication Modules for Linux) is a suite of shared libraries that enable the local system administrator to choose how applications authenticate users. It is possible to switch between the authentication mechanism(s) without (rewriting and) recompiling a PAM-aware application. Indeed, one may entirely upgrade the local authentication system without touching the applications themselves. </From PAM for Linux documentation> PAM-aware application requests authorization using predefined id - PAM service name. System administrator configures the application authorization bas PAM service name identifies set of authorization parameters. For more information see http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/ Note, that application does not see parameters of the authorization process, e.g password, Windows NT domain name, authorization server. The application only knows user name and service name. *** PAM and Wine *** Integration with PAM allows Wine to provide authentication services for Windows applications through Windows API. PAM has modules for native Unix authentication, Samba, flat files, relational databases. Example: Windows ftp server application, running under Wine can be configured to use any method of authorization, provided by PAM - Windows domain, flat file, relational database. This authorization can be made different from the authorization, required to run wine itself and different from default authorization for Wine applications. Following PAM services can be configured for Wine from more general to more detailed: * PAM service for Wine itself * Default Wine Applications service - default service which provides authentication for Windows applications. Exact name of the service will be specified in the Wine configuration is used if not specified. * Application-Specific Service Name specified in the AppDefaults section of the .wine/config file for given application. Default Application service is used if not specified Questions, problems: Do we have requirement for wineserver to work across user boundaries? If no, then we probably don't need PAM service for Wine itself. As you see Wine won't know anything about NT domains. I was thinking about passing service name through domain name parameter. Example: Call LogonUser accepts lpszDomain parameter. Instead of the domain name DOMAIN1 user provides to the application PAM service name SERVICE1. PAM service SERVICE1 is configured to use Samba module for authentication in NT domain DOMAIN1. PAM provides authorization and nothing else. To get more information from the authorization provider you should access it directly. E.g. with PAM only it is impossible to get list of users, groups from Windows NT domain, which user belongs to which group. Even more, it is impossible to know that some PAM service underneath uses NT domain and name of this domain. I can't imagine how to implement with PAM scenario like this - Windows application gets list of users belonging to some group, presents it to the user, then does authentication for one of user names. On other hand it is possible to do that with Samba. It seems it is better to ingegrate Wine with each protocol individually - implement PAM-like architecture inside Wine, but this architecture will provide much more information to Wine. The downside - this is much more complex approach than PAM. Andriy __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com

3 9

Modal VB-Dialog hangs
by Fabian Cenedese 26 Sep '02

26 Sep '02

Hi I have a problem with a VB6 app. It opens a second dialog with modal flag. After this everything hangs (WaitForMultipleObject), all windows in wine are frozen. I tried to debug it, I also read the tips and hints in the FAQ for frozen programs but I still don't get it. Would be great if anybody more wise :) could have a short look at it. I made a simple testproggy, available here (project and exe): http://www.indel.ch/ftp/vbmodtest.zip I was testing with wine-20020904 with SuSE 8.0 (2.4.18) Thanks Fabi

3 4

RE: [Controversial] Developper only CVS sandbox
by Patrik Stridvall 26 Sep '02

26 Sep '02

> As Dimi is not the only one that can start flames on > wine-devel, let's start > a new one :-) Unfortunately your topic is not controversial enough. :-) > When I see the work that is starting to go on on D3D8 or even > on my old D3D > code, I think that it would be nice if there was some CVS > 'sandbox' where > Wine developper could interact on shared code without going > the Alexandre > round-trip. This would be much less painful than sending > patches back and > forth between developpers. Makes sense. > This sandbox would be closed (ie it would be a developper > only Wine tree) to > NOT start another Wine fork and all development on this > sandbox would be > merged back in Wine when they are ready (and then would still go the > Alexandre way of course). > > Now, what does the Wine community think about this ? If > people agree, what > would be the best way to handle this ? Obviously anybody that have the resources can setup a CVS server and give accounts to others. So why discuss it at all. Do it yourself or if you lack the resources try to convice somebody that do to host it for you. If people think it is a good idea they will use it and if they want write access they will ask you for an CVS account. If not, well, I think you will notice the lack of intrest... :-) In short: Action speaks louder than words. BTW, Wine already have a SourceForge account http://sourceforge.net/projects/wine/ (registered by Dimitrie it seems). Why not use it? SourceForge provides CVS access IIRC.

6 8

re: d3d8header patch
by Ann and Jason Edmeades 26 Sep '02

26 Sep '02

Hi, Just fyi, according to the msdn: http://msdn.microsoft.com/library/en-us/dx8_c/directx_cpp/Graphics/Reference /CPP/D3DX/Interfaces/ID3DXFont/ID3DXFont.asp It would appear those should go in a new header d3dx8core.h. If you need to pick them up by people who include d3dx8.h, add a #include <d3dx8core.h> into d3dx8.h. This assumes we try to keep our definitions in the same location as windows... Jason

3 3

MZ_FillPSP() in dlls/winedos/module.c
by chrismorgan＠rcn.com 26 Sep '02

26 Sep '02

I have a script that passes a long argument string when calling a command handler(command.com or other comspec replacement). This code inside of MZ_FillPSP() if(length > 126) { ERR("Command line truncated! (length %d > maximum length 126)\n", length; length = 126; } is breaking my application by truncating the 200+ character argument at 126 characters. Do we still need to truncate at 126? Afaict having more than 126 characters may exceed some command.com default. Can someone shed more light on the historical reasons behind this code and whether more intelligent truncation can be performed? Thanks, Chris

4 5

Problem Saving Template with Word 2000
by Mason Kidd 25 Sep '02

25 Sep '02

Hi, I am using Word 2000 SR-1 on a fake windows install of wine 20020904. It runs fine except for one problem. When I exit the program, it tries to save the Normal.dot file to C:\windows\Application Data\Microsoft\Templates\Normal.dot and fails, with this error: The disk is full or too many files are open. (C:\windows\...\Templates\Normal.dot) If I click on Ok, and then try to save the template to a different location, even on a different partition, it gives the same error. I see this error in my xterm: err:shell:SHGetFileInfoA pidl is null! Is this related? I found bug number 956 that talks about this. Is this where I should start? It would seem to me that this would be a bug that Codeweavers had already dealt with, so do any of you guys know where to point me? Thanks. Mason Kidd

2 3

rfc: 16bit USER function
by Michael Stefaniuc 25 Sep '02

25 Sep '02

Hello, i would like to move USER functions of the type $type WINAPI $function16(@args) { return $function(@args); } from windows/*.c to dlls/user/user16.c but i don't know if that's the right place to put them because there are already some dlls/user/*16.c files. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

2 1

Re: RESEND: Handle shortened *optval arg. in WS_setsockopt / WS_SO_RCVTIMEO
by Greg Turner 25 Sep '02

25 Sep '02

hmm, somehow this failed to make it through to the list.... Trying again... ---- awesome, thanks for your input Rein! I am no unix sockets guru (nor, obviously, am I a winsock guru ;) so this is really helpful, I'll try and submit a revision to my revision (which is apparently already in wine). That explains the time value out I was seeing of 10,000! 3 hours sounded like an awfully long time to me so I probably should have guessed those were mili's :). Basically, from your advice, I see two options. One, the obvious one, which I'll implement for now, is to convert miliseconds-> <seconds,miliseconds> and be done with it. The other would be a "correct" solution that actually works -- judging by your post, just converting the arguments won't, and I'll need to learn a little bit more about wine-winsock to make it do the right thing. I'll do the easy thing, post it to patches, then look into do_block and get back to the list if I find that this is all beyond my abilities (a quite probable scenario ;) Thanks again for the hand-holding, keep it coming, please, as I may be somewhat "out of my league" here, and I don't want to screw up wine out of ignorance. -- Greg Turner <gmturner007(a)ameritech.net> "Waiting periods are only a step. Registration is only a step. The prohibition of private firearms is the goal." -U.S. Attorney General Janet Reno, December 1993 Rein Klazes wrote: >On Tue, 24 Sep 2002 16:10:43 -0500, you wrote: > > > > >>+ if (level == SOL_SOCKET && optname == SO_RCVTIMEO && optlen < sizeof(struct timeval)) { >>+ if (optlen == sizeof(time_t)) { >>+ /* Apparently WinSock will accept a shortened struct timeval. >> >> > >In Unix the arg optval points to a struct timeval, in windows to a >(32bit) int, no mystery here. The latter is the timeout in >milliseconds. Further a non-zero timeout less then 500 (msec) is taken >as 500 msec. > > > >>+ FIXME: should we do the same for SO_SNDTIMEO? */ >> >> > >Of course, its the same issue. > > > >>+ WARN("Short struct timeval in SO_RCVTIMEO: assuming time_t\n"); >>+ tval.tv_sec = *(time_t*)optval; >>+ tval.tv_usec = 0; >> >> > >You will need to convert from milliseconds here. > > >Unfortunately this does not work (a recv timing out). The socket in >wine is non-blocking internally, any blocking will be done in the >function do_block() using a select(). SO_RCVTMO has no effect there. > >Rein. > -- Greg Turner <gmturner007(a)ameritech.net> "Waiting periods are only a step. Registration is only a step. The prohibition of private firearms is the goal." -U.S. Attorney General Janet Reno, December 1993

1 0

ToDo's
by Thomas Wickline 25 Sep '02

25 Sep '02

Thanks to everyone who has gave feedback on this. Here is a draft of eveything up to today. As always in need of feedback ;) Tom Wine ToDo's as of 9/25/02 Contact : twickline2(a)triad.rr.com Wine ToDo OverView Window management: * Window management needs proper inter-process handling of activation, focus, repaint. National Language Support: * ASCII function work Winsock: * Winsock1 calls,in particular select(),use direct system calls instead of using related wine APIs * More unit tests need to be written * Make sure OOB data is handled properly. Check client-size blocking. * WS2: "provider" interface * WS2: Support other kind of services, like IrDA. * Fix stubs left in ws2_32.spec. DirectSound: * Make the latency configurable (tunable). * More intelligent prebuffering. * Complete support for hardware secondary buffers through the HAL (for a future ALSA multimedia wave audio driver). * 3D sound buffers. * Sound capture (recording). Sound drivers: * Alsa driver (on final 0.9 interface) Video: * Implement native codecs (RLE...) * DIB engine to do 32-bit graphics manipulation DDE: * Enhance memory management issues (interprocess sending) Wineconsole: * Add a (n)curse backend so that we can run CUI programs without using USER32 (and X11 behind) Native programs: * Winhelp: fix invocation thru WinHelp * Winedbg: make winedbg use dbghelp DLL File management: * Implement NT file namespace * UNC support * Allow flexibility in FS "mounting" (for example, SMB shares) TrueType fonts: * Libfontconfig support Tools: * Wine installation process should install and configure wine * Winemaker fixes * Run C regression tests on Windows with MSVC * Compile Wine with -DSTRICT * Work on WRC as it does not find system headers Instructions: * Write a proper Users Guide Introduction * Documentation updates Aspect or Component: * More DLL Separation * BiDi support * Review of Wine Server Protocol * Finalize Server Protocol * PAM (Pluggable Authentication Modules) * Visual C++'s native COM support * Add DWARF2 support * Speed up PDB support * Create replacement of browser component (Internet Explorer/I Porting issues for Mingw/Cygwin/MS_VC * Better seperation of win16/32 code. * Remove/rewite win16/9x api dependancy on newer code * Remove/rewrite wineisms from code * Documentation fixes low priority items: * VxD support with dynamic loading Add links to: Tasklets: http://bugs.winehq.com/buglist.cgi?keywords=tasklet tasklist: http://bugs.winehq.com/buglist.cgi?keywords=tasklist For a full list of .9/1.0 task's

3 3

Re: ToDo's
by Steven Edwards 25 Sep '02

25 Sep '02

Eric POUECH wrote: >>Here is the status of what I have so far on the ToDo's. >>I am not sure what section to put alot of this in so I just made >>Tools , Instructions & Aspect or Component for now. >>As much feedback as possiable is welcomed . >> >> > >here's some feedback: > >Sound drivers >- Alsa driver (on final 0.9 interface) > >Video: >- implement native codecs (RLE...) > >DDE: >- enhance memory management issues (interprocess sending) > >wineconsole: >- add a (n)curse backend so that we can run CUI programs without using USER32 (and X11 behind) > >file management: >- implement NT file namespace >- UNC support >- allow flexibility in FS "mounting" (for example, SMB shares) >(NB: I think we should make that clearer and not keep it shadowed in the Aspect/component list) > >(native) programs: >- winhelp: fix invocation thru WinHelp >- winedbg: make winedbg use dbghelp DLL (and implement it of course) > >--8<--------- >remove the Multimedia wave audio section >SEH support has been lately enhanced, is there still known issues ? >IMO, Dwarf2 support should not be added to winedbg. use of gdb proxy should be required instead. (even if it means adding PDB support to gdb, but that'd be a better investment) > >we should make clear what the low priority items are (VxD support with dynamic loading for example) > >A+ > > I dont know if any of these are in any of the TODOs but here goes. all of these would go under porting issues for Mingw/Cygwin/MS_VC - Better seperation of win16/32 code. - remove/rewite win16/9x api dependancy on newer code - remove/rewrite wineisms from code - documentation fixes I think all of this is high priortity but I am biased =) Thanks Steven

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel