ok.. this works just is you compile the release sources... to get "actual code" manually apply the patches usind git apply xxx.patch
so it should work... Am 09.07.19 um 09:37 schrieb Peter Dähn: > Hi, > > if you don't change something on the screensharing part of om simply put > the jar of the release in place. > > red5/webapps/openmeetings/screenshare/openmeetings-screenshare-4.0.8-full.jar > > Greetings Peter > > Am 09.07.19 um 08:03 schrieb Maxim Solodovnik: >> Yes, sure >> >> Only releases are being signed (this is not free) >> Nightly and local builds uses self-signed certificate >> >> On Tue, 9 Jul 2019 at 12:59, Equinoxe 4 <[email protected]> wrote: >>> Hi Maxim. It is a nightly build... Could be that the problem? >>> >>> Obtener Outlook para Android >>> >>> ________________________________ >>> From: Maxim Solodovnik <[email protected]> >>> Sent: Monday, July 8, 2019 10:00:10 PM >>> To: Openmeetings user-list >>> Subject: Re: Screen recording and Java security >>> >>> Hello, >>> >>> all released 4.0.x versions are signed with Symantec code signing >>> certificate and produces no warnings >>> Are you building from sources? >>> >>> On Tue, 9 Jul 2019 at 02:44, Equinoxe 4 <[email protected]> >>> wrote: >>>> Hi list, >>>> >>>> I want to give my users the chance to record the sessions using the >>>> desktop sharing recording option given by OM 4.x. However, I'm getting a >>>> security error from Java, which forces the uset to manually add the OM >>>> host to the security exceptions in the Java configuration console. My >>>> users are not tech savvy, so they will quit using the function. It seems >>>> that the problem comes from the fact that some java code is self-signed. I >>>> have a Comodo certificate for the OM host. Can I use the same certificate >>>> to sign the Java code? And, if yes, is there any guide to do this? >>>> >>>> Thanks in advanced. >>> >>> -- >>> WBR >>> Maxim aka solomax >> > >
