sounds good so far... ;-)
Am 24.03.2016 um 16:10 schrieb Maxim Solodovnik:
I will add NOTE to the news section regarding new release
something like
please NOTE this release contains screen-sharing application signed be
self-signed certificate due to
https://issues.apache.org/jira/browse/INFRA-11384.
to use screen-sharing application with modern Java, please add OM site to
the list of java security exceptions by running $JAVA_HOME/bin/ControlPanel.
I believe this should be enough :)
On Thu, Mar 24, 2016 at 8:25 PM, Peter Dähn <[email protected]> wrote:
ok.. than it need to be communicated somehow and I'm fine with it...
Greetings Peter
Am 24.03.2016 um 12:04 schrieb Maxim Solodovnik:
I'm subscribed to JIRA issue (any registered user can *watch* JIRA)
I'm pinging INFRA once a week
and unfortunately no-one have ETA :(
this is why I raised this topic
On Thu, Mar 24, 2016 at 4:57 PM, Peter Dähn <[email protected]> wrote:
If so, how it will be communicated and how log does it take till these
issue will be fixed (still no answer yet, I think...)?
Sorry for bothering... ;-) Peter
Am 24.03.2016 um 10:59 schrieb Maxim Solodovnik:
Actually install from branch and install release differs:
1) release gets additional testing
1. by developers before cutting release
2. by community while voting
2) release is sort of "complete" if you will look at issues fixed, and
features implemented
3) web-start app is signed
I would vote for release "as is" due to currently both development and
"security release" are stalled :(
On Thu, Mar 24, 2016 at 2:14 PM, Peter Dähn <[email protected]> wrote:
Sorry for the late response,
I already started 3 times... to write this e-mail... ;-)
What is the difference to install 3.1.1 from branch or a release with
self
signed certificates? If I need some features or bugfixes I could
install
an
actual branch (maybe recommended rxxxx)-version and I would have an
java-application with all security-dialogs because of the self signed
certificate.
If I am not aware of the mailing-lists I will install a release with
that
restrictions. It need to be communicate very clear somehow, what is the
difference to former releases and what does it mean.
If there is a need to release a new version, than it need to be clear
how
to communicate the restrictions outside the mailing-lists. If there is
no
need for a release I would wait. Anyway in both cases we need an
estimation
how long it takes to fix this issue.
Greetings Peter
Am 24.03.2016 um 04:28 schrieb Maxim Solodovnik:
Hmm, we have 23 PMC, and 3 were active on this topic :)
We got quorum :)
I'm going to process with releases tonight, please stop me if you have
good
reason :)
On Thu, Mar 24, 2016 at 3:37 AM, [email protected] <
[email protected]> wrote:
Ok
2016-03-23 22:45 GMT+13:00 Alvaro <[email protected]>:
Right now i made a fresh installation of OM 3.1.1 (DropBox)
on Windows 10 with Oracle java 1.8_74, and doeing it Maxim
say about ControlPanel-java, it can start the screen sharing
application
works fine.
...................
El mié, 23-03-2016 a las 19:58 +1300, [email protected]
escribió:
Yeah but have you tested with a Windows PC if you can start the
screen
sharing application ?
On OSx it won't work without going through a number of hacks in
case
it's a
self signed certificate.
cheers
2016-03-23 19:50 GMT+13:00 Maxim Solodovnik <[email protected]
:
I believe this comment [1] describes the current situation
[1]
https://issues.apache.org/jira/browse/INFRA-11384?focusedCommentId=15182057&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15182057
On Wed, Mar 23, 2016 at 12:05 PM, Maxim Solodovnik <
[email protected]>
wrote:
As I understand (I don't have HipChat log)
INFRA waiting for Symantec answer (I guess for a long time)
Actually we are using self-signed version in demo
The only thing need to done is to run
/opt/jdk/jre/bin/ControlPanel,
and
add Om site to the exceptions list (tested with Oracle JDK up to
1.8.0_73)
On Wed, Mar 23, 2016 at 9:00 AM, [email protected] <
[email protected]> wrote:
Did they at least say what's the blocking issue?
Anyway, I would agree, in that case we go ahead and release it
with
a
caveat. The issue will be that a lot of the new jvm's don not
accept
Java
WebStart applications with self signed certificates anymore. I can
remember
some issues on Mac with it.
Has anyone checked if the self signed certificate for Java
Webstart
still
works at least on Windows with latest JVM ?
Thanks,
Sebastian
2016-03-23 15:53 GMT+13:00 Maxim Solodovnik <
[email protected]
:
I have contacted them using hipchat (official INFRA channel)
The answer was: no ETA :(
This is why I have raised this discussion
WBR, Maxim
(from mobile, sorry for the typos)
On Mar 23, 2016 01:03, <[email protected]> wrote:
Have you tried to use IRC channel to get a response on the ETA
from
infra ?
Sent from my iPhone
On 23/03/2016, at 3:02 AM, Alvaro <[email protected]>
wrote:
Do it!
....................
El mar, 22-03-2016 a las 17:27 +0600, Maxim Solodovnik
escribió:
Hello All,
As you may know our current releases are blocked by
https://issues.apache.org/jira/browse/INFRA-11384 (no
signing
events
available)
Maybe we can publish our release with screen-sharing
application
signed
by
self-signed certificate until INFRA-11384 will be resolved?
This issue is 1 week old and INFRA team can't provide any
estimates on
when
in might be resolved
WDYT?
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
[email protected]
--
WBR
Maxim aka solomax
--
WBR
Maxim aka solomax
--
Sebastian Wagner
https://twitter.com/#!/dead_lock
[email protected]
