Damian Garbacz | 10 Sep 08:23 2010

Signed assemblies

Hi,

I'm using log4net library in one of my projects (commercial application).

I'm trying to get the 'The Windows 7 Software' and 'Works with Windows Server 2008 R2' Logo. One of the requirements is, that all assemblies should be digital signed. Third party software should be signed by author. Is there a possibility to get that kind of log4net library?

 

Please notice that signing tool used in Visual Studio is not sufficient.

There is a requirement, to use 'signtool.exe' application (described in http://msdn.microsoft.com/en-us/library/8s9b9yaz(VS.80).aspx), along with proper certificate (should be purchased in one of Microsoft trusted providers e.g. http://www.verisign.com/index.html )

 

Best Regards

 

--

Damian Garbacz

Software Engineer & Team Leader

 

-----------------------------------------------

 Future Processing Sp. z o.o.

 Tel: +48 32 4612270

 Fax: +48 32 3762318

 Mob: +48 691 643356

 dgarbacz <at> future-processing.com

 www.future-processing.com

-----------------------------------------------

 

Dominik Psenner | 10 Sep 10:56 2010
Picon

RE: Signed assemblies

Howdie,

 

This nails down to the question: who’s gonna pay the certificate? It would probably require some kind of sponsorship to ASF that in turn will make sure the log4net project gets the certificate. J

 

http://www.apache.org/foundation/sponsorship.html

 

Greetings,

D.

 

From: Damian Garbacz [mailto:dgarbacz <at> future-processing.com]
Sent: Friday, September 10, 2010 8:24 AM
To: log4net-dev <at> logging.apache.org
Subject: Signed assemblies

 

Hi,

I'm using log4net library in one of my projects (commercial application).

I'm trying to get the 'The Windows 7 Software' and 'Works with Windows Server 2008 R2' Logo. One of the requirements is, that all assemblies should be digital signed. Third party software should be signed by author. Is there a possibility to get that kind of log4net library?

 

Please notice that signing tool used in Visual Studio is not sufficient.

There is a requirement, to use 'signtool.exe' application (described in http://msdn.microsoft.com/en-us/library/8s9b9yaz(VS.80).aspx), along with proper certificate (should be purchased in one of Microsoft trusted providers e.g. http://www.verisign.com/index.html )

 

Best Regards

 

--

Damian Garbacz

Software Engineer & Team Leader

 

-----------------------------------------------

 Future Processing Sp. z o.o.

 Tel: +48 32 4612270

 Fax: +48 32 3762318

 Mob: +48 691 643356

 dgarbacz <at> future-processing.com

 www.future-processing.com

-----------------------------------------------

 

Damian Garbacz | 14 Sep 10:09 2010

RE: Signed assemblies

Hello,

Because of order code of practice, before any sponsorship, a need an official confirmation, that you already don’t have that kind of certificate and library.

Don’t take this to negative, I just need that information, so I can go and talk to my official supervisor.

 

Best regards.

 

--

Damian Garbacz

Software Engineer & Team Leader

 

-----------------------------------------------

 Future Processing Sp. z o.o.

 Tel: +48 32 4612270

 Fax: +48 32 3762318

 Mob: +48 691 643356

 dgarbacz <at> future-processing.com

 www.future-processing.com

-----------------------------------------------

 

From: Dominik Psenner [mailto:dpsenner <at> gmail.com]
Sent: Friday, September 10, 2010 10:56 AM
To: 'Log4NET Dev'
Subject: RE: Signed assemblies

 

Howdie,

 

This nails down to the question: who’s gonna pay the certificate? It would probably require some kind of sponsorship to ASF that in turn will make sure the log4net project gets the certificate. J

 

http://www.apache.org/foundation/sponsorship.html

 

Greetings,

D.

 

From: Damian Garbacz [mailto:dgarbacz <at> future-processing.com]
Sent: Friday, September 10, 2010 8:24 AM
To: log4net-dev <at> logging.apache.org
Subject: Signed assemblies

 

Hi,

I'm using log4net library in one of my projects (commercial application).

I'm trying to get the 'The Windows 7 Software' and 'Works with Windows Server 2008 R2' Logo. One of the requirements is, that all assemblies should be digital signed. Third party software should be signed by author. Is there a possibility to get that kind of log4net library?

 

Please notice that signing tool used in Visual Studio is not sufficient.

There is a requirement, to use 'signtool.exe' application (described in http://msdn.microsoft.com/en-us/library/8s9b9yaz(VS.80).aspx), along with proper certificate (should be purchased in one of Microsoft trusted providers e.g. http://www.verisign.com/index.html )

 

Best Regards

 

--

Damian Garbacz

Software Engineer & Team Leader

 

-----------------------------------------------

 Future Processing Sp. z o.o.

 Tel: +48 32 4612270

 Fax: +48 32 3762318

 Mob: +48 691 643356

 dgarbacz <at> future-processing.com

 www.future-processing.com

-----------------------------------------------

 

Dominik Psenner | 14 Sep 10:36 2010
Picon

RE: Signed assemblies

Hi,

 

I am quite confident that if there were signed assemblies, they would be available for download.

 

Greetings,

D.

 

From: Damian Garbacz [mailto:dgarbacz <at> future-processing.com]
Sent: Tuesday, September 14, 2010 10:09 AM
To: 'Log4NET Dev'
Su
bject: RE: Signed assemblies

 

Hello,

Because of order code of practice, before any sponsorship, a need an official confirmation, that you already don’t have that kind of certificate and library.

Don’t take this to negative, I just need that information, so I can go and talk to my official supervisor.

 

Best regards.

 

--

Damian Garbacz

Software Engineer & Team Leader

 

-----------------------------------------------

 Future Processing Sp. z o.o.

 Tel: +48 32 4612270

 Fax: +48 32 3762318

 Mob: +48 691 643356

 dgarbacz <at> future-processing.com

 www.future-processing.com

-----------------------------------------------

 

From: Dominik Psenner [mailto:dpsenner <at> gmail.com]
Sent: Friday, September 10, 2010 10:56 AM
To: 'Log4NET Dev'
Subject: RE: Signed assemblies

 

Howdie,

 

This nails down to the question: who’s gonna pay the certificate? It would probably require some kind of sponsorship to ASF that in turn will make sure the log4net project gets the certificate. J

 

http://www.apache.org/foundation/sponsorship.html

 

Greetings,

D.

 

From: Damian Garbacz [mailto:dgarbacz <at> future-processing.com]
Sent: Friday, September 10, 2010 8:24 AM
To: log4net-dev <at> logging.apache.org
Subject: Signed assemblies

 

Hi,

I'm using log4net library in one of my projects (commercial application).

I'm trying to get the 'The Windows 7 Software' and 'Works with Windows Server 2008 R2' Logo. One of the requirements is, that all assemblies should be digital signed. Third party software should be signed by author. Is there a possibility to get that kind of log4net library?

 

Please notice that signing tool used in Visual Studio is not sufficient.

There is a requirement, to use 'signtool.exe' application (described in http://msdn.microsoft.com/en-us/library/8s9b9yaz(VS.80).aspx), along with proper certificate (should be purchased in one of Microsoft trusted providers e.g. http://www.verisign.com/index.html )

 

Best Regards

 

--

Damian Garbacz

Software Engineer & Team Leader

 

-----------------------------------------------

 Future Processing Sp. z o.o.

 Tel: +48 32 4612270

 Fax: +48 32 3762318

 Mob: +48 691 643356

 dgarbacz <at> future-processing.com

 www.future-processing.com

-----------------------------------------------

 

Julie Sheffield (JIRA | 14 Sep 22:14 2010
Picon

[jira] Commented: (LOG4NET-1) Support Fallback Appenders


    [
https://issues.apache.org/jira/browse/LOG4NET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909421#action_12909421
] 

Julie Sheffield commented on LOG4NET-1:
---------------------------------------

I implemented this behavior for the RemotingAppender by having it implement IAppenderAttachable
(exactly the way ForwardingAppender implements it).  Then I could add the backup appender just by
specifying appender-ref in log4net.config.  Then all I needed to do was in the catch block , before calling
ErrorHandler.Error(message, ex), I look to see if any appenders have been attached and forward the
LoggingEvent to them.

Of course, this approach is specific only to the RemotingAppender.  Since that's what I need for the project
I'm working on, that's what I've tested extensively, but it seems like it wouldn't be hard to take a similar
approach with other potentially error-prone appenders like ADONetAppender if it's too disruptive to
change the entire IErrorHandler interface.

In the meantime, should I check in my changes to RemotingAppender?  Seems like that one is particularly
susceptible to potential intermittent interruptions and other HA applications might need similar
behavior to what I've implemented and tested.  Where should I upload my code so people could take a look and
see if it's worth including?

Thanks!

> Support Fallback Appenders
> --------------------------
>
>                 Key: LOG4NET-1
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-1
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders, Core
>    Affects Versions: 1.2.9
>         Environment: From sourceforge
>            Reporter: Nicko Cadell
>             Fix For: v.Next
>
>
> Basically, I'm looking for the ability to set up a hierarchy of appenders so that if a log to an
ADONETAppender fails, log4net could then log to one of more "back-up" appenders, for example, a
RollingLogFile or SMTP.
> Thanks,
> Leo
> Leo J. Hart IV

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Nicko Cadell (JIRA | 14 Sep 22:37 2010
Picon

[jira] Commented: (LOG4NET-1) Support Fallback Appenders


    [
https://issues.apache.org/jira/browse/LOG4NET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909433#action_12909433
] 

Nicko Cadell commented on LOG4NET-1:
------------------------------------

I am currently out of the office with no access to emails until September 15th. If your email is urgent please
contact Rick Hobbs or Nigel Atkinson on 020 7025 0950, otherwise I will respond on my return.

Thanks,
Nicko

> Support Fallback Appenders
> --------------------------
>
>                 Key: LOG4NET-1
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-1
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders, Core
>    Affects Versions: 1.2.9
>         Environment: From sourceforge
>            Reporter: Nicko Cadell
>             Fix For: v.Next
>
>
> Basically, I'm looking for the ability to set up a hierarchy of appenders so that if a log to an
ADONETAppender fails, log4net could then log to one of more "back-up" appenders, for example, a
RollingLogFile or SMTP.
> Thanks,
> Leo
> Leo J. Hart IV

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Julie Sheffield (JIRA | 15 Sep 15:18 2010
Picon

[jira] Updated: (LOG4NET-1) Support Fallback Appenders


     [
https://issues.apache.org/jira/browse/LOG4NET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julie Sheffield updated LOG4NET-1:
----------------------------------

    Attachment: RemotingAppender.cs

> Support Fallback Appenders
> --------------------------
>
>                 Key: LOG4NET-1
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-1
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders, Core
>    Affects Versions: 1.2.9
>         Environment: From sourceforge
>            Reporter: Nicko Cadell
>             Fix For: v.Next
>
>         Attachments: RemotingAppender.cs
>
>
> Basically, I'm looking for the ability to set up a hierarchy of appenders so that if a log to an
ADONETAppender fails, log4net could then log to one of more "back-up" appenders, for example, a
RollingLogFile or SMTP.
> Thanks,
> Leo
> Leo J. Hart IV

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Julie Sheffield (JIRA | 18 Sep 02:08 2010
Picon

[jira] Created: (LOG4NET-267) Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if the number of errors goes over a specified threshold

Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if the
number of errors goes over a specified threshold
-----------------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: LOG4NET-267
                 URL: https://issues.apache.org/jira/browse/LOG4NET-267
             Project: Log4net
          Issue Type: Improvement
          Components: Other
    Affects Versions: 1.2.10
         Environment: N/A (compiled against .NET 2.0)
            Reporter: Julie Sheffield
            Priority: Minor
             Fix For: v.Next

I had a requirement for my project that the ops team be notified every time the number of error-level or
higher alerts logged system-wide was more than a certain threshold in any given day.  (i.e. notify ops
after every 25 errors, but reset the count every day, so there might be multiple notifications on a single
day if the error log were getting flooded, but a few errors per day will not raise the alarm.)  I think this
might be of use for other people's projects as well, so I thought I would contribute the code.  To use it, the
service calling the remote sink would pass in a named logger and a threshold to an overloaded constructor. 
If no logger is passed in to the constructor, the plugin will use its original behavior with no performance
implication beyond one check for null.

Please see attached code.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Julie Sheffield (JIRA | 18 Sep 02:10 2010
Picon

[jira] Updated: (LOG4NET-267) Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if the number of errors goes over a specified threshold


     [
https://issues.apache.org/jira/browse/LOG4NET-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julie Sheffield updated LOG4NET-267:
------------------------------------

    Attachment: RemoteLoggingServerPlugin.cs

Code allowing callers of the plugin to specify an additional logger to log errors to after every specified
number of messages per day

> Added overload to RemoteLoggingServerPlugin to allow callers to pass in an additional logger to use if
the number of errors goes over a specified threshold
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-267
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-267
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Other
>    Affects Versions: 1.2.10
>         Environment: N/A (compiled against .NET 2.0)
>            Reporter: Julie Sheffield
>            Priority: Minor
>             Fix For: v.Next
>
>         Attachments: RemoteLoggingServerPlugin.cs
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> I had a requirement for my project that the ops team be notified every time the number of error-level or
higher alerts logged system-wide was more than a certain threshold in any given day.  (i.e. notify ops
after every 25 errors, but reset the count every day, so there might be multiple notifications on a single
day if the error log were getting flooded, but a few errors per day will not raise the alarm.)  I think this
might be of use for other people's projects as well, so I thought I would contribute the code.  To use it, the
service calling the remote sink would pass in a named logger and a threshold to an overloaded constructor. 
If no logger is passed in to the constructor, the plugin will use its original behavior with no performance
implication beyond one check for null.
> Please see attached code.

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Julie Sheffield (JIRA | 18 Sep 02:14 2010
Picon

[jira] Issue Comment Edited: (LOG4NET-1) Support Fallback Appenders


    [
https://issues.apache.org/jira/browse/LOG4NET-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909421#action_12909421
] 

Julie Sheffield edited comment on LOG4NET-1 at 9/17/10 8:13 PM:
----------------------------------------------------------------

I implemented this behavior for the RemotingAppender by having it implement IAppenderAttachable
(exactly the way ForwardingAppender implements it).  Then I could add the backup appender just by
specifying appender-ref in log4net.config.  Then in the catch block, before calling
ErrorHandler.Error(message, ex), I look to see if any appenders have been attached and forward the
LoggingEvent to them.

Of course, this approach is specific only to the RemotingAppender.  Since that's what I need for the project
I'm working on, that's what I've tested extensively, but it seems like it wouldn't be hard to take a similar
approach with other potentially error-prone appenders like ADONetAppender if it's too disruptive to
change the entire IErrorHandler interface.

In the meantime, should I check in my changes to RemotingAppender?  Seems like that one is particularly
susceptible to potential intermittent interruptions and other HA applications might need similar
behavior to what I've implemented and tested.  Where should I upload my code so people could take a look and
see if it's worth including?

Thanks!

      was (Author: codegrll):
    I implemented this behavior for the RemotingAppender by having it implement IAppenderAttachable
(exactly the way ForwardingAppender implements it).  Then I could add the backup appender just by
specifying appender-ref in log4net.config.  Then all I needed to do was in the catch block , before calling
ErrorHandler.Error(message, ex), I look to see if any appenders have been attached and forward the
LoggingEvent to them.

Of course, this approach is specific only to the RemotingAppender.  Since that's what I need for the project
I'm working on, that's what I've tested extensively, but it seems like it wouldn't be hard to take a similar
approach with other potentially error-prone appenders like ADONetAppender if it's too disruptive to
change the entire IErrorHandler interface.

In the meantime, should I check in my changes to RemotingAppender?  Seems like that one is particularly
susceptible to potential intermittent interruptions and other HA applications might need similar
behavior to what I've implemented and tested.  Where should I upload my code so people could take a look and
see if it's worth including?

Thanks!

> Support Fallback Appenders
> --------------------------
>
>                 Key: LOG4NET-1
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-1
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders, Core
>    Affects Versions: 1.2.9
>         Environment: From sourceforge
>            Reporter: Nicko Cadell
>             Fix For: v.Next
>
>         Attachments: RemotingAppender.cs
>
>
> Basically, I'm looking for the ability to set up a hierarchy of appenders so that if a log to an
ADONETAppender fails, log4net could then log to one of more "back-up" appenders, for example, a
RollingLogFile or SMTP.
> Thanks,
> Leo
> Leo J. Hart IV

--

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Gmane