Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0C71F200B38 for ; Fri, 8 Jul 2016 19:28:11 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 0B137160A5A; Fri, 8 Jul 2016 17:28:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id ADDCB160A36 for ; Fri, 8 Jul 2016 19:28:09 +0200 (CEST) Received: (qmail 32584 invoked by uid 500); 8 Jul 2016 17:28:08 -0000 Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@nifi.apache.org Delivered-To: mailing list dev@nifi.apache.org Received: (qmail 32573 invoked by uid 99); 8 Jul 2016 17:28:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 Jul 2016 17:28:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2565F180584 for ; Fri, 8 Jul 2016 17:28:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.549 X-Spam-Level: * X-Spam-Status: No, score=1.549 tagged_above=-999 required=6.31 tests=[HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=2, KAM_LOTSOFHASH=0.25, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id naH5yn-pCfND for ; Fri, 8 Jul 2016 17:28:04 +0000 (UTC) Received: from mail-pa0-f48.google.com (mail-pa0-f48.google.com [209.85.220.48]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id ACA0F5FBC7 for ; Fri, 8 Jul 2016 17:28:03 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id hu1so1757493pad.3 for ; Fri, 08 Jul 2016 10:28:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :message-id:references:to; bh=r5osCli5TuKZBFy02NxQcVCWLdOoojWlB84ol1KKUUk=; b=cI6iBSu+gn5la4mMljAfeTTR/Z/4D2oy8xUfcSYgn2oZSYTf2ZcDRAffBbfKqheUOB kZQqxN1Q7fSKeTn7L3IUz8GDePCmmUviLmAprW3Rajuf8WZ4vzImIRkG2NZ/lYHukV8l QTbMPQ0Fe0GY5D7Cl0V2XXS+tfgD/uwW7dfzz9mZus3K6J3e4RoX/DZOlvOO5WmYSbPb f1PWATD16zJbL5Fv2u5+jt0LZ8vk0CdV5T9zMLj1C3Upd+7algJTanoyBc9jzSm3Gbfi rk/awgqiZhslbzT1JPN40hiFmACxjUrhMkqQQ0UpozWpxY5vjKAN1u9p8loTZUj+XXZK yzbw== X-Gm-Message-State: ALyK8tLjiledc7108iRIpPhbYDF/utqv0xuOBo9x0Xie0P9+jKxv9bByAWeVEiTNZl+Qsg== X-Received: by 10.67.3.7 with SMTP id bs7mr11941036pad.86.1467998882233; Fri, 08 Jul 2016 10:28:02 -0700 (PDT) Received: from [192.168.1.3] (cpe-172-91-141-241.socal.res.rr.com. [172.91.141.241]) by smtp.gmail.com with ESMTPSA id d65sm5907068pfa.45.2016.07.08.10.28.00 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 08 Jul 2016 10:28:01 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_0DE37AB1-6245-4B0A-8F61-B8306AC3D496"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) Subject: Re: [VOTE] Release Apache NiFi MiNiFi 0.0.1 (RC1) X-Pgp-Agent: GPGMail 2.6b2 From: Andy LoPresto In-Reply-To: Date: Fri, 8 Jul 2016 10:27:59 -0700 Message-Id: <6A4E3975-F1AE-4038-9B28-3FF947423E4E@apache.org> References: <643781941.436603.1467915206822.JavaMail.yahoo@mail.yahoo.com> <1450593271.844069.1467987362540.JavaMail.yahoo@mail.yahoo.com> To: dev@nifi.apache.org X-Mailer: Apple Mail (2.3124) archived-at: Fri, 08 Jul 2016 17:28:11 -0000 --Apple-Mail=_0DE37AB1-6245-4B0A-8F61-B8306AC3D496 Content-Type: multipart/alternative; boundary="Apple-Mail=_790B399D-6168-435B-A592-8AA253027144" --Apple-Mail=_790B399D-6168-435B-A592-8AA253027144 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 My +1 vote from the other day is now binding. Andy LoPresto alopresto@apache.org alopresto.apache@gmail.com PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jul 8, 2016, at 9:12 AM, Joe Witt wrote: >=20 > +1 binding. >=20 > Ran through full build verification. Check licensing/notice items and > hoping we can make that leaner and meaner over time as well. >=20 > Was able to use the toolkit to convert a nifi template to a minifi > config and fire that up and immediately see desired results. >=20 > Some feedback items. >=20 > 1) minifi-toolkit awareness > The build helper email references this which makes knowledge of it > available. But I didn't initially notice any references to it in the > system admin guide doc or README entries. Might need to call it out > more or provide a more prescriptive pointer to how to build it, find > it, use it. >=20 > 2) minifi-toolkit execution >=20 > When running config.sh it says > " > Transform Usage: >=20 > java org.apache.nifi.minifi.toolkit.configuration.ConfigMain transform > INPUT_FILE OUTPUT_FILE > " >=20 > But I ended up just running 'bin/config.sh IN.xml OUT.yml' and it > worked great so the java classname bits there are probably superfluous > or only apply to those running without the script. >=20 > 3) WARN in logs. Probably can be pulled in differently to avoid this. > 2016-07-08 09:04:30,300 WARN [main] org.apache.nifi.nar.NarClassLoader > ./work/nar/framework/minifi-framework-nar-0.0.1.nar-unpacked does not > contain META-INF/bundled-dependencies! >=20 > 4) Some of these things about how minifi starts up, is configured, API > items, are probably still subject to change. We should document that > well. A version of 0.0.1 might not be sufficient to communicate that. >=20 > On Fri, Jul 8, 2016 at 7:56 AM, Bryan Rosander = wrote: >> +1 (non-binding) >>=20 >> Downloaded RC, verified checksums, gpg. >>=20 >> Built with contrib-check turned on. >>=20 >> Ran through all templates at >> = https://github.com/brosander/minifi-testkit/tree/8a8b9791a6b3d6404d6eaa6be= 48951851d3fa898/templates >> (ran config.sh transform on each template to generate yaml, ran = MiNiFi with >> resulting yaml) >>=20 >> Thanks, >> Bryan >>=20 >> On Fri, Jul 8, 2016 at 10:16 AM, Joe Percivall < >> joepercivall@yahoo.com.invalid> wrote: >>=20 >>> +1 (binding) >>>=20 >>> Ran through the helper and verified functionality. >>>=20 >>> - - - - - - >>> Joseph Percivall >>> linkedin.com/in/Percivall >>> e: joepercivall@yahoo.com >>>=20 >>>=20 >>>=20 >>>=20 >>> On Thursday, July 7, 2016 2:13 PM, Joe Percivall >>> wrote: >>> Vote forth-coming but regarding Andy's notes/questions: >>> I agree with using HTTPS links when possible in both files and the = couple >>> README.md changes. >>>=20 >>> I don't think there are any plans currently for separate mailing = lists/IRC >>> nodes. I am in favor of keeping NiFi and MiNiFi together for now to = build >>> visibility, especially since MiNiFi is a sub-project of NiFi. Once = there is >>> a steady stream of questions we can revisit it. >>> If this vote passes, it would be the first release. In order to = avoid the >>> issues with the sensitive property you suggest would it need to be = done for >>> this release? >>> Technically Connections are referring to the IDs of both the = Processor and >>> Port. The difference is that the Processor's IDs are set as the same = as the >>> configured name and for the Ports, the IDs and names are those that = are set >>> in the target NiFi instance (you're point to a component in another >>> system). As you bring up this adds the the limitation that all names = must >>> be unique (which in small deployments that MiNiFi targets shouldn't = be a >>> problem) but makes it more user friendly. Enforcing uniqueness was = added as >>> part of a contribution from Bryan Rosander as a validation check = when >>> transforming the config.yml and applies to processors, connections, = and >>> remote processing groups. >>> Joe >>> - - - - - - Joseph Percivalllinkedin.com/in/Percivalle: >>> joepercivall@yahoo.com >>>=20 >>>=20 >>>=20 >>> On Thursday, July 7, 2016 12:05 AM, Andy LoPresto < >>> alopresto@apache.org> wrote: >>>=20 >>>=20 >>> Hi, >>> I verified the GPG signature and all hash signatures. Contrib check = ran >>> fine. >>> I used one of the example config.yml files in the System Admin Guide = and >>> deployed it to the compiled binary. The tool ran successfully and = wrote to >>> a log file on my system. I have a couple notes about the release but >>> nothing blocking. >>> +1 (non-binding) >>> Notes/questions: >>> README.md:* Could we use HTTPS links when possible?* The note about = the >>> time to run a parallel Maven build says on a moderate dev laptop it = should >>> complete in less than 10 minutes. While true, a more accurate = statement >>> would be < 2 minutes. * The mkdir example references = =E2=80=9Cexample-nifi-deploy=E2=80=9D >>> and =E2=80=9Cexample-minifi-deploy=E2=80=9D interchangeably. * Are = there separate MiNiFi >>> mailing lists and IRC nodes coming? >>> System Admin Guide:* Could we use HTTPS links when possible? >>> config.yml:* Could we please change the default algorithm for = protecting >>> sensitive property values to something stronger than the current = selection? >>> I would open a Jira if necessary, but this is one of those things = that is >>> really better to do before the first release so users have a >>> backward-compatible config.yml file moving forward. If we change it = in a >>> subsequent release, we will need to do significant migration = hand-holding. >>> My suggestion would be "PBEWITHSHA256AND256BITAES-CBC-BC=E2=80=9D = which is >>> significantly stronger, but after trying a few BC options, I = continue to >>> get EncryptionExceptions even though I have the JCE unlimited = cryptographic >>> strength jurisdiction policy files installed, so this may be a 0.0.2 = fix. >>> Is BouncyCastle not enabled by default?* Question about how = processors and >>> connectors reference each other =E2=80=94 it appears connectors = reference source >>> processors by name but destination processors or ports by ID? Is = this >>> consistent or just demonstrating the flexibility of the system? = Also, what >>> enforces processor name uniqueness, as this is not an existing = feature of >>> NiFi. >>> All in all looks like a lot of great work and will expand the user = base >>> and opportunities for NiFi significantly. Thanks. >>> Andy LoPrestoalopresto@apache.orgalopresto.apache@gmail.comPGP >>> Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 >>>=20 >>> On Jul 6, 2016, at 7:27 PM, Aldrin Piri = wrote: >>> Hello Apache NiFi Community, >>>=20 >>> I am pleased to be calling this vote for the source release of = Apache NiFi >>> - MiNiFi, >>> minifi-0.0.1. >>>=20 >>> The source zip, including signatures, digests, etc. can be found at: >>> = https://repository.apache.org/content/repositories/orgapachenifi-1087 >>>=20 >>> The Git tag is minifi-0.0.1-RC1 >>>=20 >>> The Git commit hash is d6ebeda6bce8259f0531e8455965625333315bdb >>> * >>>=20 >>> = https://git-wip-us.apache.org/repos/asf?p=3Dnifi-minifi.git;a=3Dcommit;h=3D= d6ebeda6bce8259f0531e8455965625333315bdb >>>=20 >>> * >>>=20 >>> = https://github.com/apache/nifi-minifi/commit/d6ebeda6bce8259f0531e84559656= 25333315bdb >>>=20 >>> Checksums of minifi-0.0.1-source-release.zip: >>> MD5: b63355fb419ca09b26fe12485b3bf4a5 >>> SHA1: 4c9352b7d4d53d139a707dbdcd03df73dbfb847d >>> SHA256: = d52e7f614afe6aee05e6796e429f2813b51f36d2b6d83a4c08a1fb1fdb50b2ff >>>=20 >>> Release artifacts are signed with the following key: >>> https://people.apache.org/keys/committer/aldrin >>>=20 >>> KEYS file available here: >>> https://dist.apache.org/repos/dist/release/nifi/KEYS >>>=20 >>> 30 issues were closed/resolved for this release: >>>=20 >>> = https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=3D1231602= 0&version=3D12335481 >>>=20 >>> Release note highlights can be found here: >>>=20 >>> = https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNo= tes-Version0.0.1 >>>=20 >>> The vote will be open for 72 hours. >>> Please download the release candidate and evaluate the necessary = items >>> including checking hashes, signatures, build from source, and test. = Then >>> please vote: >>>=20 >>> [ ] +1 Release this package as minifi-0.0.1 >>> [ ] +0 no opinion >>> [ ] -1 Do not release this package because... >>>=20 >>> Thanks! >>>=20 --Apple-Mail=_790B399D-6168-435B-A592-8AA253027144 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 My +1 vote from the other day is now binding. 

Andy = LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC = B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

On Jul 8, 2016, at 9:12 AM, Joe Witt <joe.witt@gmail.com> = wrote:

+1 binding.

Ran through full = build verification.  Check licensing/notice items and
hoping we can make that leaner and meaner over time as = well.

Was able to use the toolkit to = convert a nifi template to a minifi
config and fire that = up and immediately see desired results.

Some = feedback items.

1) minifi-toolkit = awareness
The build helper email references this which = makes knowledge of it
available.  But I didn't = initially notice any references to it in the
system admin = guide doc or README entries.  Might need to call it out
more or provide a more prescriptive pointer to how to build = it, find
it, use it.

2) = minifi-toolkit execution

When running = config.sh it says
"
Transform Usage:

java = org.apache.nifi.minifi.toolkit.configuration.ConfigMain transform
INPUT_FILE OUTPUT_FILE
"

But I ended up just running 'bin/config.sh IN.xml OUT.yml' = and it
worked great so the java classname bits there are = probably superfluous
or only apply to those running = without the script.

3) WARN in logs. =  Probably can be pulled in differently to avoid this.
2016-07-08 09:04:30,300 WARN [main] = org.apache.nifi.nar.NarClassLoader
./work/nar/framework/minifi-framework-nar-0.0.1.nar-unpacked = does not
contain META-INF/bundled-dependencies!

4) Some of these things about how minifi = starts up, is configured, API
items, are probably still = subject to change.  We should document that
well. =  A version of 0.0.1 might not be sufficient to communicate that.

On Fri, Jul 8, 2016 at 7:56 AM, Bryan Rosander = <bryanrosander@gmail.com> wrote:
+1 (non-binding)

Downloaded RC, verified checksums, gpg.

Built with contrib-check turned on.

Ran through all templates at
https://github.com/brosander/minifi-testkit/tree/8a8b9791a6b3d6= 404d6eaa6be48951851d3fa898/templates
(ran config.sh = transform on each template to generate yaml, ran MiNiFi with
resulting yaml)

Thanks,
Bryan

On Fri, Jul 8, 2016 at = 10:16 AM, Joe Percivall <
joepercivall@yahoo.com.invalid> wrote:

+1 (binding)

Ran through the helper and verified = functionality.

- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joepercivall@yahoo.com




On Thursday, July 7, 2016 2:13 = PM, Joe Percivall
<joepercivall@yahoo.com.INVALID> = wrote:
Vote forth-coming but regarding Andy's = notes/questions:
I agree with using HTTPS links when = possible in both files and the couple
README.md = changes.

I don't think there are any plans = currently for separate mailing lists/IRC
nodes. I am in = favor of keeping NiFi and MiNiFi together for now to build
visibility, especially since MiNiFi is a sub-project of NiFi. = Once there is
a steady stream of questions we can revisit = it.
If this vote passes, it would be the first release. In = order to avoid the
issues with the sensitive property you = suggest would it need to be done for
this release?
Technically Connections are referring to the IDs of both the = Processor and
Port. The difference is that the Processor's = IDs are set as the same as the
configured name and for the = Ports, the IDs and names are those that are set
in the = target NiFi instance (you're point to a component in another
system). As you bring up this adds the the limitation that = all names must
be unique (which in small deployments that = MiNiFi targets shouldn't be a
problem) but makes it more = user friendly. Enforcing uniqueness was added as
part of a = contribution from Bryan Rosander as a validation check when
transforming the config.yml and applies to processors, = connections, and
remote processing groups.
Joe
- - - - - - Joseph = Percivalllinkedin.com/in/Percivalle:
joepercivall@yahoo.com



   On Thursday, July 7, 2016 = 12:05 AM, Andy LoPresto <
alopresto@apache.org> = wrote:


Hi,
I = verified the GPG signature and all hash signatures. Contrib check ran
fine.
I used one of the example config.yml = files in the System Admin Guide and
deployed it to the = compiled binary. The tool ran successfully and wrote to
a = log file on my system. I have a couple notes about the release but
nothing blocking.
+1 (non-binding)
Notes/questions:
README.md:* Could we use HTTPS = links when possible?* The note about the
time to run a = parallel Maven build says on a moderate dev laptop it should
complete in less than 10 minutes. While true, a more accurate = statement
would be < 2 minutes. * The mkdir example = references =E2=80=9Cexample-nifi-deploy=E2=80=9D
and = =E2=80=9Cexample-minifi-deploy=E2=80=9D interchangeably.  * Are = there separate MiNiFi
mailing lists and IRC nodes = coming?
System Admin Guide:* Could we use HTTPS links when = possible?
config.yml:* Could we please change the default = algorithm for protecting
sensitive property values to = something stronger than the current selection?
I would = open a Jira if necessary, but this is one of those things that is
really better to do before the first release so users have = a
backward-compatible config.yml file moving forward. If = we change it in a
subsequent release, we will need to do = significant migration hand-holding.
My suggestion would be = "PBEWITHSHA256AND256BITAES-CBC-BC=E2=80=9D which is
significantly stronger, but after trying a few BC options, I = continue to
get EncryptionExceptions even though I have = the JCE unlimited cryptographic
strength jurisdiction = policy files installed, so this may be a 0.0.2 fix.
Is = BouncyCastle not enabled by default?* Question about how processors = and
connectors reference each other =E2=80=94 it appears = connectors reference source
processors by name but = destination processors or ports by ID? Is this
consistent = or just demonstrating the flexibility of the system? Also, what
enforces processor name uniqueness, as this is not an = existing feature of
NiFi.
All in all looks = like a lot of great work and will expand the user base
and = opportunities for NiFi significantly. Thanks.
Andy = LoPrestoalopresto@apache.orgalopresto.apache@gmail.comPGP
Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B = 2F7D EF69

On Jul 6, 2016, at 7:27 PM, = Aldrin Piri <aldrinpiri@gmail.com> wrote:
Hello = Apache NiFi Community,

I am pleased to be = calling this vote for the source release of Apache NiFi
- = MiNiFi,
minifi-0.0.1.

The = source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenif= i-1087

The Git tag is minifi-0.0.1-RC1

The Git commit hash is = d6ebeda6bce8259f0531e8455965625333315bdb
*
https://git-wip-us.apache.org/repos/asf?p=3Dnifi-minifi.git;a=3D= commit;h=3Dd6ebeda6bce8259f0531e8455965625333315bdb

*

https://github.com/apache/nifi-minifi/commit/d6ebeda6bce8259f05= 31e8455965625333315bdb

Checksums of = minifi-0.0.1-source-release.zip:
MD5: = b63355fb419ca09b26fe12485b3bf4a5
SHA1: = 4c9352b7d4d53d139a707dbdcd03df73dbfb847d
SHA256: = d52e7f614afe6aee05e6796e429f2813b51f36d2b6d83a4c08a1fb1fdb50b2ff

Release artifacts are signed with the = following key:
https://people.apache.org/keys/committer/aldrin

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

30 issues were closed/resolved for this = release:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectI= d=3D12316020&version=3D12335481

Release = note highlights can be found here:

https://cwiki.apache.org/confluence/display/MINIFI/Release+Note= s#ReleaseNotes-Version0.0.1

The vote will = be open for 72 hours.
Please download the release = candidate and evaluate the necessary items
including = checking hashes, signatures, build from source, and test. Then
please vote:

[ ] +1 Release this = package as minifi-0.0.1
[ ] +0 no opinion
[ = ] -1 Do not release this package because...

Thanks!


= --Apple-Mail=_790B399D-6168-435B-A592-8AA253027144-- --Apple-Mail=_0DE37AB1-6245-4B0A-8F61-B8306AC3D496 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJXf+KfAAoJEDxu9lsvfe9pkuYP/jfZZekTHk0wT1Ty+5nFHcF7 IRLxqJdQP8NhZtuz1pE49df0GWDnJ1zI4/O35eiTcGo0D3u7OHqd/NceOhtjsl2r pBLue0jykjanE4kqqOdjClzPY4MPKqzhdm4tWoR5E7yaO26o/mL3iwuR2fSQnfmM pqX17oMiY6n9efxJh1AfecS3jUhbH5lkz/37amrqgUUgdhTVvXnLT8U7qOW0vWx5 BfCHQc0bhvkJvMAyzlHKXzoJIR/BFf32kGhlmbgHVMtvrzE1MvgvbupBXh6aVwlC 5hQ7eDjmk56YcCrQ9P8YEHcSkQECNmVMfo8gYx1rKAMsWc235QqK+3H7lem+LuzL FSrX6gQfVu+W+FARKehNW4SHPB+bBnB7wAZde4OX44fjWK1LkI5unKlGAt3Z8AbB mw317sIEPgZUeFORXl2iyVjmQRpAJF5tlunexc4j10iGQIgcMqhRzf84MsTB9zQi H0O1A04yv1Iyr6n/ERQA0tOma93RxA3i4LPWiT/JFQeRiieNaudavqKfw8vwYSq5 nrhn3c4Hof2KApGl2n41mhosEYx6KFHRoxxKk1mSUyd97DDkLcAvm+hjvpGAvcAb Lo4oyghdpQmohDnkLf53G19BxrzBgugrqDH9B9hjE275nkaaH20CLmZUjDbMVRoQ H3eJY6ESTvWsHuY8jLhb =wyrv -----END PGP SIGNATURE----- --Apple-Mail=_0DE37AB1-6245-4B0A-8F61-B8306AC3D496--