Return-Path: X-Original-To: apmail-logging-log4j-user-archive@www.apache.org Delivered-To: apmail-logging-log4j-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9511596D5 for ; Fri, 19 Dec 2014 11:44:00 +0000 (UTC) Received: (qmail 81400 invoked by uid 500); 19 Dec 2014 11:43:55 -0000 Delivered-To: apmail-logging-log4j-user-archive@logging.apache.org Received: (qmail 81348 invoked by uid 500); 19 Dec 2014 11:43:55 -0000 Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Users List" Reply-To: "Log4J Users List" Delivered-To: mailing list log4j-user@logging.apache.org Received: (qmail 81337 invoked by uid 99); 19 Dec 2014 11:43:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 11:43:55 +0000 X-ASF-Spam-Status: No, hits=-0.4 required=5.0 tests=PLING_QUERY,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of remko.popma@gmail.com designates 209.85.220.43 as permitted sender) Received: from [209.85.220.43] (HELO mail-pa0-f43.google.com) (209.85.220.43) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Dec 2014 11:43:27 +0000 Received: by mail-pa0-f43.google.com with SMTP id kx10so1059761pab.30 for ; Fri, 19 Dec 2014 03:43:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:in-reply-to:message-id:date:to :content-transfer-encoding:mime-version; bh=Ur4/NCdNIdYAzt90UmFeKu2lYpsqYXwYetfbIhiFDJE=; b=zyoCbN/n1Ypn7WdQj0C/AOozIcnQ9lOSbUttg/4nQff2+BqySsGWnAx1c4S9UXZlYv st9O0nlL5x4hRkCjqs0Y3IhQs75da0PkWbk7OzplY1SAdl80AfVyV5R0bXSv3WJh3KHg YZx26FPeJJvucUm+vs5WYmr3ywNSSgTt+Jn8+wsqS7MRYGu36VZKXze5EpoexkRrw5IS p9quXP+SI7q5davN49l5oiCRCBh2G5k9k3Y6D8uvP+helulfxdTbqL9m/aKp3i0VYDzm fztSK/JJlsfOt7FTKEvdI+O5/IpEcnni+g0AAeDgfrT/uh2yCWIBC7a6pd/d6jWc9+uM G0PA== X-Received: by 10.70.129.106 with SMTP id nv10mr11575546pdb.7.1418989406243; Fri, 19 Dec 2014 03:43:26 -0800 (PST) Received: from [10.66.128.89] (pw126254138001.8.panda-world.ne.jp. [126.254.138.1]) by mx.google.com with ESMTPSA id di3sm9389424pbc.46.2014.12.19.03.43.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 19 Dec 2014 03:43:25 -0800 (PST) Subject: Re: How to write encrypted (!) lines to logfile ? References: <424813.33939.bm@smtp129.mail.ir2.yahoo.com> From: Remko Popma Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (11D257) In-Reply-To: <424813.33939.bm@smtp129.mail.ir2.yahoo.com> Message-Id: <1EB5C94A-2418-4241-B1C8-FBF803E0ED9E@gmail.com> Date: Fri, 19 Dec 2014 20:43:18 +0900 To: Log4J Users List Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-Virus-Checked: Checked by ClamAV on apache.org Interesting! Currently there's no such feature, but would you mind raising a= feature request in the log4j2 Jira issue tracker?=20 Thanks! Remko Sent from my iPhone > On 2014/12/19, at 19:43, "Ben Stover" wrote: >=20 > As far as I know the standard way of writing log output to logfiles is as p= lain human readable text. >=20 > Is there a way to configure log4j to enrypt lines before writing? > Or (re-)encrypt whole logfile after writing? >=20 > The encryption should NOT take place IN the writing application but be con= figured inside log4j configuration. >=20 > Ben >=20 >=20 >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org > For additional commands, e-mail: log4j-user-help@logging.apache.org >=20 --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-user-help@logging.apache.org