2013-02-10 13:59:09 +00:00
|
|
|
/*
|
|
|
|
* COPYRIGHT: See COPYING in the top level directory
|
|
|
|
* PROJECT: ReactOS System Libraries
|
|
|
|
* FILE: dll/win32/kernel32/include/console.h
|
|
|
|
* PURPOSE: Console API Client Definitions
|
2013-04-15 19:32:00 +00:00
|
|
|
* PROGRAMMERS: Hermes Belusca-Maito (hermes.belusca@sfr.fr)
|
2013-02-10 13:59:09 +00:00
|
|
|
*/
|
|
|
|
|
|
|
|
#pragma once
|
|
|
|
|
|
|
|
/* CONSTANTS ******************************************************************/
|
|
|
|
|
2014-09-07 22:53:49 +00:00
|
|
|
#define HANDLE_DETACHED_PROCESS (HANDLE)-1
|
|
|
|
#define HANDLE_CREATE_NEW_CONSOLE (HANDLE)-2
|
|
|
|
#define HANDLE_CREATE_NO_WINDOW (HANDLE)-3
|
|
|
|
|
2013-02-10 13:59:09 +00:00
|
|
|
|
|
|
|
/* FUNCTION PROTOTYPES ********************************************************/
|
|
|
|
|
2014-09-07 22:53:49 +00:00
|
|
|
BOOLEAN
|
|
|
|
WINAPI
|
|
|
|
ConDllInitialize(IN ULONG Reason,
|
|
|
|
IN PWSTR SessionDir);
|
2013-02-10 13:59:09 +00:00
|
|
|
|
2014-09-07 22:53:49 +00:00
|
|
|
VOID
|
|
|
|
InitializeCtrlHandling(VOID);
|
2013-02-10 13:59:09 +00:00
|
|
|
|
2014-09-07 22:53:49 +00:00
|
|
|
DWORD
|
|
|
|
WINAPI
|
[CONSOLE.DLL-KERNEL32-CONSRV]
Fix the console properties dialog, when launching and transmitting console properties. Before, the properties dialog was directly launched by the console server (consrv), running with CSRSS (System) privileges, what constituted a security hole. Now, I create a remote thread in the running process owning the console for launching the properties dialog (thus it has only user privileges, and not System ones anymore). For that purpose, I basically took the technique described in the following paper (Cesar Cerrudo, "Story of a dumb patch", http://www.argeniss.com/research/MSBugPaper.pdf or http://www.scn.rain.com/~neighorn/PDF/MSBugPaper.pdf), where basically the console server shares the console properties via a shared memory section with the console properties dialog dll. The address of the thread which launches the dialog in the context of the console app is given to the console server the same way as we do for the control handler (called e.g. when you press Ctrl-C, etc...)
Of course this is quite hackish, because you have the GUI interface split between the console server and the console properties dialog dll. Something far more elegant would be to put all the GUI thingie into a dedicated dll or exe, running with the same privileges as the console program itself (a kind of console -- or terminal -- emulator).
[CONSOLE.DLL]
Fix retriving / setting colors.c and other things.
[CONSRV.DLL]
- Fix retrieving / setting console properties from the registry (via the HKCU\Console\* keys), via the shell shortcuts (not totally done at the moment, because somebody has to implement properly that thing : http://msdn.microsoft.com/en-us/library/windows/desktop/bb773359(v=vs.85).aspx (NT_CONSOLE_PROPS structure stored as a shortcut data block) (at application launching time), and via the console properties dialog.
- Few DPRINTs removed.
svn path=/branches/ros-csrss/; revision=58415
2013-03-03 15:35:12 +00:00
|
|
|
ConsoleControlDispatcher(IN LPVOID lpThreadParameter);
|
|
|
|
|
2014-09-07 22:53:49 +00:00
|
|
|
DWORD
|
|
|
|
WINAPI
|
[CONSOLE.DLL-KERNEL32-CONSRV]
Fix the console properties dialog, when launching and transmitting console properties. Before, the properties dialog was directly launched by the console server (consrv), running with CSRSS (System) privileges, what constituted a security hole. Now, I create a remote thread in the running process owning the console for launching the properties dialog (thus it has only user privileges, and not System ones anymore). For that purpose, I basically took the technique described in the following paper (Cesar Cerrudo, "Story of a dumb patch", http://www.argeniss.com/research/MSBugPaper.pdf or http://www.scn.rain.com/~neighorn/PDF/MSBugPaper.pdf), where basically the console server shares the console properties via a shared memory section with the console properties dialog dll. The address of the thread which launches the dialog in the context of the console app is given to the console server the same way as we do for the control handler (called e.g. when you press Ctrl-C, etc...)
Of course this is quite hackish, because you have the GUI interface split between the console server and the console properties dialog dll. Something far more elegant would be to put all the GUI thingie into a dedicated dll or exe, running with the same privileges as the console program itself (a kind of console -- or terminal -- emulator).
[CONSOLE.DLL]
Fix retriving / setting colors.c and other things.
[CONSRV.DLL]
- Fix retrieving / setting console properties from the registry (via the HKCU\Console\* keys), via the shell shortcuts (not totally done at the moment, because somebody has to implement properly that thing : http://msdn.microsoft.com/en-us/library/windows/desktop/bb773359(v=vs.85).aspx (NT_CONSOLE_PROPS structure stored as a shortcut data block) (at application launching time), and via the console properties dialog.
- Few DPRINTs removed.
svn path=/branches/ros-csrss/; revision=58415
2013-03-03 15:35:12 +00:00
|
|
|
PropDialogHandler(IN LPVOID lpThreadParameter);
|
|
|
|
|
2013-02-10 13:59:09 +00:00
|
|
|
HANDLE WINAPI
|
|
|
|
DuplicateConsoleHandle(HANDLE hConsole,
|
|
|
|
DWORD dwDesiredAccess,
|
|
|
|
BOOL bInheritHandle,
|
|
|
|
DWORD dwOptions);
|
|
|
|
|
2014-04-20 14:39:38 +00:00
|
|
|
BOOL WINAPI
|
|
|
|
GetConsoleHandleInformation(IN HANDLE hHandle,
|
|
|
|
OUT LPDWORD lpdwFlags);
|
|
|
|
|
|
|
|
BOOL WINAPI
|
|
|
|
SetConsoleHandleInformation(IN HANDLE hHandle,
|
|
|
|
IN DWORD dwMask,
|
|
|
|
IN DWORD dwFlags);
|
|
|
|
|
2013-02-10 13:59:09 +00:00
|
|
|
BOOL WINAPI
|
|
|
|
VerifyConsoleIoHandle(HANDLE Handle);
|
|
|
|
|
|
|
|
BOOL WINAPI
|
|
|
|
CloseConsoleHandle(HANDLE Handle);
|
|
|
|
|
|
|
|
HANDLE WINAPI
|
|
|
|
GetConsoleInputWaitHandle(VOID);
|
|
|
|
|
2014-08-04 20:25:34 +00:00
|
|
|
HANDLE
|
2013-02-10 13:59:09 +00:00
|
|
|
TranslateStdHandle(HANDLE hHandle);
|
|
|
|
|
2014-09-07 22:53:49 +00:00
|
|
|
#define SetTEBLangID(p) (p)
|
|
|
|
|
|
|
|
VOID
|
|
|
|
SetUpConsoleInfo(IN BOOLEAN CaptureTitle,
|
|
|
|
IN OUT LPDWORD pTitleLength,
|
|
|
|
IN OUT LPWSTR* lpTitle OPTIONAL,
|
|
|
|
IN OUT LPDWORD pDesktopLength,
|
|
|
|
IN OUT LPWSTR* lpDesktop OPTIONAL,
|
|
|
|
IN OUT PCONSOLE_START_INFO ConsoleStartInfo);
|
|
|
|
|
2013-02-10 13:59:09 +00:00
|
|
|
VOID
|
2014-09-07 22:53:49 +00:00
|
|
|
SetUpHandles(IN PCONSOLE_START_INFO ConsoleStartInfo);
|
|
|
|
|
|
|
|
VOID
|
|
|
|
InitExeName(VOID);
|
|
|
|
|
|
|
|
VOID
|
|
|
|
SetUpAppName(IN BOOLEAN CaptureStrings,
|
|
|
|
IN OUT LPDWORD CurDirLength,
|
|
|
|
IN OUT LPWSTR* CurDir,
|
|
|
|
IN OUT LPDWORD AppNameLength,
|
|
|
|
IN OUT LPWSTR* AppName);
|
|
|
|
|
|
|
|
USHORT
|
|
|
|
GetCurrentExeName(OUT PWCHAR ExeName,
|
|
|
|
IN USHORT BufferSize);
|
2013-02-10 13:59:09 +00:00
|
|
|
|
|
|
|
LPCWSTR
|
|
|
|
IntCheckForConsoleFileName(IN LPCWSTR pszName,
|
|
|
|
IN DWORD dwDesiredAccess);
|
|
|
|
|
|
|
|
HANDLE WINAPI
|
|
|
|
OpenConsoleW(LPCWSTR wsName,
|
|
|
|
DWORD dwDesiredAccess,
|
|
|
|
BOOL bInheritHandle,
|
|
|
|
DWORD dwShareMode);
|
|
|
|
|
|
|
|
/* EOF */
|