Bug 752 - Lack of Message file and Eventlog Application Source registry entries result in event log errors
Summary: Lack of Message file and Eventlog Application Source registry entries result ...
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: -current
Hardware: ix86 Cygwin on NT/2k/Win7-11
: P2 minor
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-02 00:20 AEDT by Rodrigo Verissimo
Modified: 2016-05-21 01:17 AEST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rodrigo Verissimo 2003-11-02 00:20:00 AEDT
Due to a lack of a messaging dll for the cygrunsrv host and sshd service, all 
event log entries contain this error message before the actual sshd message :

> Source:    OpenSSHd
> Type:      Information
> Event ID:  0
> The description for Event ID ( 0 ) in Source (
> OpenSSHd ) cannot be found. The local computer may not
> have the necessary registry information or message DLL
> files to display messages from a remote computer. You
> may be able to use the /AUXSOURCE= flag to retrieve
> this description; see Help and Support for details.
> The following information is part of the event:
> OpenSSHd : PID 1512 : `OpenSSHd' service stopped.

to fix it ,create a resource file with message and categories entries and 
insertion string tags, compile it and link it to a dll. 
and add the proper registry keys in :
HKLM\SYSTEM\CurrentControlSet\Services\EventLog\Application\OpenSSHd
Comment 1 Damien Miller 2003-11-16 16:58:55 AEDT
Corrina, could you have a look at this please?
Comment 2 Corinna Vinschen 2003-11-17 02:37:17 AEDT
All Cygwin syslog entries are looking like this due to the missing
message entry in the DLL.  Nobody volunteered for a patch so far
since nobody cared enough.  The information is right there at the
end of the entry.  And it's definitely not the right way, to create
such a message entry for each and every application

Since it's not an OpenSSH bug, it doesn't belong here.  Therefore
I set the status to invalid.
Comment 3 Damien Miller 2004-04-14 12:24:19 AEST
Mass change of RESOLVED bugs to CLOSED
Comment 4 kevin.m.smyth+mindrot 2016-05-21 01:17:35 AEST
For posterity: the register_sshd_messages.cmd script at http://opensource.wellbury.com/projects/windows_sshd_block/ implements the described solution.

(Note the registry key is ...\Application\sshd not OpenSSHd)