Return-Path: X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7B2F17E34 for ; Tue, 4 Oct 2011 17:52:02 +0000 (UTC) Received: (qmail 35649 invoked by uid 500); 4 Oct 2011 17:52:02 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 35617 invoked by uid 500); 4 Oct 2011 17:52:02 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 35609 invoked by uid 99); 4 Oct 2011 17:52:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2011 17:52:02 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of grobmeier@gmail.com designates 209.85.216.47 as permitted sender) Received: from [209.85.216.47] (HELO mail-qw0-f47.google.com) (209.85.216.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2011 17:51:56 +0000 Received: by qadc1 with SMTP id c1so767266qad.34 for ; Tue, 04 Oct 2011 10:51:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=Z1k6sInieZSJ0iEYBjT4nmXmf/YPRE3Qjax98nTnMgI=; b=SEwjqAdyLiNHgcXNGFhvnY75x9FSoDcbNX8tkgf+FwgGB5hMPJiiZhHCXChBY/FUuZ 1T8vIhOCND+f33BHnWELiWxWPXrlYOviu2Yb5X7JSo1OQBgcmO1rMjpaVHc0txrnY4JN jJ3GlQUdTy87NJlF9ugpV8ejyM4SAe4D8DlFA= Received: by 10.229.23.212 with SMTP id s20mr1217162qcb.153.1317750695143; Tue, 04 Oct 2011 10:51:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.223.134 with HTTP; Tue, 4 Oct 2011 10:51:15 -0700 (PDT) In-Reply-To: References: <26491AC0-0C0B-4F94-BB74-EC0ABD97FF71@apache.org> From: Christian Grobmeier Date: Tue, 4 Oct 2011 19:51:15 +0200 Message-ID: Subject: Re: Companions -> Chainsaw? To: Log4J Developers List Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org OK understood. Not sure were do ask, but maybe infra has an idea if such a thing exists. If not, we might ask the board if we can buy something like that On Tue, Oct 4, 2011 at 7:44 PM, Scott Deboy wrote: > We need a code signing certificate that is trusted by a root cert auth, and > use that cert to sign the jars - I would prefer the ASF handle this. > > See > http://download.oracle.com/javase/6/docs/technotes/guides/javaws/developersguide/faq.html > > Scott > > > On Tue, Oct 4, 2011 at 10:32 AM, Christian Grobmeier > wrote: >> >> > http://logging.apache.org/chainsaw/download.html - by clicking on the >> > 'Java >> > Web Start' link, Chainsaw will download, install and run.. >> > >> > To update the version of Chainsaw we provide via Web Start, we need to >> > sign >> > the jars, since Chainsaw writes to the local file system, can initiate >> > socket connections, etc, and Web Start only allows that if the jars are >> > signed and the person oks the access..It seems Apache should have a cert >> > for >> > signing jars, instead of having to do this ourselves.. >> >> Is any pgp key fine to sign or should it be one with a trusted >> identiy, like "this software was developed by the ASF" and so on? >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org >> For additional commands, e-mail: log4j-dev-help@logging.apache.org >> > > -- http://www.grobmeier.de --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org