kenlefeb/aonawaresyslog

Automatically exported from code.google.com/p/aonawaresyslog

Hi there 👋

aonawaresyslog's Issues

Password stored for uninstall should be encrypted

The database password that used to install the database is stored 
unencrypted for uninstallation

Original issue reported on code.google.com by [email protected] on 4 Jun 2007 at 8:57

Setup should autocreate user if required

Syslog user in database should be automatically created, depending on db 
authentication mode

Original issue reported on code.google.com by [email protected] on 4 Jun 2007 at 8:58

[deleted issue]

[deleted issue]

Can't Install in Win2008R2

What steps will reproduce the problem?
1. run Setup.exe or SetupSyslogDaemon.msi 
2. after input 2 pages sql server information
3. will pop-up a dialog: "The installer has encountered an unexpected error 
installing the package. This may indicate a problem with this package. The 
error code is 2869"

This is a good software for syslog. It's work fine in win2003. Please help fix 
Win2008 install problem. Thanks a lot. :)

Original issue reported on code.google.com by [email protected] on 21 Jul 2011 at 2:27

Installation options - use existing database

Is it possible to set the program to use an existing database rather than 
create a new database for each install?

I would like to add the tables and permissions to an existing database, and I 
can also see this being useful if you install it on a new server but want to 
keep existing data from a previous install.

Thanks in advance for any help.

Original issue reported on code.google.com by [email protected] on 1 Jul 2013 at 4:22

Documentation out of date

Screenshots, install order does not match new design

Original issue reported on code.google.com by [email protected] on 4 Jun 2007 at 8:55

Create setup for sample application

The sample syslog sender / receiver should be installable

Original issue reported on code.google.com by [email protected] on 4 Jun 2007 at 8:59

Configuration database passwords should be encrypted

Passwords stored in the config files should be encrypted

Original issue reported on code.google.com by [email protected] on 4 Jun 2007 at 8:57

white list allows callers

this will protect against DOS attacks.

a simple XML file on db table to hold this data.

this of course can be done in any decent firewall hardware software too.
But somepeople will not have this so simply doing it in software would be 
at least a decent option.

Original issue reported on code.google.com by [email protected] on 18 Feb 2009 at 5:50

Allow decoding of hostname

Request to decode hostname and store this in database.  Not all hardware 
supports sending host name though.

Original issue reported on code.google.com by [email protected] on 4 Jun 2007 at 9:01

Addressing the unencrypted password problem

A simple modification of your code will remove the dependancy on unencrypted 
passwords.  I downloaded the source code to see if I can implement the change 
required.  

My test platform will be windows7 to SQL2005 std.

Original issue reported on code.google.com by [email protected] on 8 Oct 2010 at 2:40