Return-Path: X-Original-To: apmail-openmeetings-user-archive@www.apache.org Delivered-To: apmail-openmeetings-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 46793EFBD for ; Tue, 5 Feb 2013 04:28:35 +0000 (UTC) Received: (qmail 94091 invoked by uid 500); 5 Feb 2013 04:28:35 -0000 Delivered-To: apmail-openmeetings-user-archive@openmeetings.apache.org Received: (qmail 94069 invoked by uid 500); 5 Feb 2013 04:28:34 -0000 Mailing-List: contact user-help@openmeetings.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@openmeetings.apache.org Delivered-To: mailing list user@openmeetings.apache.org Received: (qmail 94041 invoked by uid 99); 5 Feb 2013 04:28:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 04:28:33 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of solomax666@gmail.com designates 209.85.220.53 as permitted sender) Received: from [209.85.220.53] (HELO mail-pa0-f53.google.com) (209.85.220.53) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Feb 2013 04:28:26 +0000 Received: by mail-pa0-f53.google.com with SMTP id bg4so3758967pad.26 for ; Mon, 04 Feb 2013 20:28:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=HsUwJmeDiFjAGXCmgDOs7+/DeXpClraZAW6Qrb2UoXw=; b=CPS3RjNuzD+BaQQPPJbKBDVnnhCPx8S4voPLPpIr/NGgDz4KB+SFrn3AF2DPm85Fxn xYlnXtXoeedWvoQlekhzEDMzXvW3+WK3oqBEHHS6cXRcZfvjDjak1Y2KnIz9NNu/OqOy FuJ5A/kQcr2ZlZVRPttZxpV84yONtnks5xqM9gGmqRA1pYKVpO89SKLHtDav3c2eIHDA 7CMC5d7MegAvKXvukNOvfqSVcxffftTD6nIhUs2GfoxcXYJ5BmFOiPLHNpqrTW9I3Ij7 vpRNwqO00Qmhs1g9FTyjYdGMZreg2UbBoRWKbr033RVixpTtyHslziHTO7K1q9N+dGIF 91iA== MIME-Version: 1.0 X-Received: by 10.66.89.199 with SMTP id bq7mr60165657pab.26.1360038484906; Mon, 04 Feb 2013 20:28:04 -0800 (PST) Received: by 10.66.16.72 with HTTP; Mon, 4 Feb 2013 20:28:04 -0800 (PST) In-Reply-To: References: <510C5238.306@telenet.be> <510CDF03.2070004@telenet.be> <510D278E.90404@telenet.be> Date: Tue, 5 Feb 2013 11:28:04 +0700 Message-ID: Subject: Re: problem while upgrading to OM 2.1 From: Maxim Solodovnik To: Bart Coninckx Cc: user Content-Type: multipart/alternative; boundary=f46d042ef591c6138d04d4f2a290 X-Virus-Checked: Checked by ClamAV on apache.org --f46d042ef591c6138d04d4f2a290 Content-Type: text/plain; charset=UTF-8 Fixed. Committed revision 1442468. On Sat, Feb 2, 2013 at 9:56 PM, Maxim Solodovnik wrote: > it is about storing user passwords. > to make it working you need to login to your DB and run the followin query: > update configuration set conf_value = > 'org.apache.openmeetings.utils.crypt.MD5Implementation' where conf_key = > 'crypt_ClassName'; > > > > > On Sat, Feb 2, 2013 at 9:49 PM, Bart Coninckx wrote: > >> OK, so this has nothing to do with RTMPS and HTTPS? It's while >> introducing these that I started habing trouble. It is actually then about >> storing things in de DB in an encrypted way? >> >> Is there an SQL somewhere to update the DB? >> >> cheers, >> >> BC >> >> >> On 02/02/13 13:20, Maxim Solodovnik wrote: >> >> You need to wait for my fix or manually update DB and set crypt class >> On Feb 2, 2013 4:40 PM, "Bart Coninckx" wrote: >> >>> Sebastian, >>> >>> meaning what? >>> >>> I took the version of >>> >>> https://builds.apache.org/job/openmeetings/lastSuccessfulBuild/artifact/singlewebapp/dist/apache-openmeetings-2.1.0.r1441250-31-01-2013_2314.tar.gz >>> >>> by the way... >>> >>> BC >>> >>> On 02/02/13 01:01, seba.wagner@gmail.com wrote: >>> >>> Yes it is now org.apache.openmeetings. ... if you are using latest 2.1 >>> revision from svn. >>> >>> Sebastian >>> Am 02.02.2013 12:40 schrieb "Bart Coninckx" : >>> >>>> Hi, >>>> >>>> after doing this I get: >>>> >>>> ERROR 02-02 00:36:32.388 ManageCryptStyle.java 66485 49 >>>> org.apache.openmeetings.utils.crypt.ManageCryptStyle [NioProcessor-18] - >>>> [getInstanceOfCrypt] >>>> java.lang.ClassNotFoundException: >>>> org.openmeetings.utils.crypt.MD5Implementation >>>> >>>> >>>> I recreated a keystore like I did successfully for OM 2.0 but somehow >>>> OM trips over this. >>>> >>>> Any idea fella's? >>>> >>>> cheers, >>>> >>>> >>>> BC >>>> >>> >>> >> > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax --f46d042ef591c6138d04d4f2a290 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Fixed.
Committed revision 1442468.


On Sat, Feb 2, 20= 13 at 9:56 PM, Maxim Solodovnik <solomax666@gmail.com> wr= ote:
it is about storing user pa= sswords.
to make it working you need to login to your DB and run the fo= llowin query:
update configuration set conf_value =3D 'org.apache.openmeetings.u= tils.crypt.MD5Implementation' where conf_key =3D 'crypt_ClassName&#= 39;;


<= div class=3D"h5">

On Sat, Feb 2, 2013 at = 9:49 PM, Bart Coninckx <bart.coninckx@telenet.be> wro= te:
=20 =20 =20
OK, so this has nothing to do with RTMPS and HTTPS? It's while introducing these that I started habing trouble.=C2=A0 It is actually then about storing things in de = DB in an encrypted way?

Is there an SQL somewhere to update the DB?

cheers,

BC


On 02/02/13 13:20, Maxim Solodovnik wrote:

You need to wait for my fix or manually update DB and set crypt class

On Feb 2, 2013 4:40 PM, "Bart Coninck= x" <b= art.coninckx@telenet.be> wrote:

Yes it is now org.apache.openmeetings. ... if you are using latest 2.1 revision from svn.

Sebastian

Am 02.02.2013 12:40 schrieb "= Bart Coninckx" <bart.coninckx@telenet.be>:
Hi,

after doing this I get:

ERROR 02-02 00:36:32.388 ManageCryptStyle.java 66485 49 org.apache.openmeetings.utils.crypt.ManageCryptStyle [NioProcessor-18] - [getInstanceOfCrypt]
java.lang.ClassNotFoundException: org.openmeetings.utils.crypt.MD5Implementation


I recreated a keystore like I did successfully for OM 2.0 but somehow OM trips over this.

Any idea fella's?

cheers,


BC





--
WBR
Maxim aka solomax



--
WBR
Maxim= aka solomax --f46d042ef591c6138d04d4f2a290--