during the updates for ZRTP callback and the ZRTP specific part
of the GUI I took the chance to show the overall GUI to a friend
who is not a software developer or even a "nerd" , just a
normal Windows user.
I showed him the features how to set up a SIP call, and showed him
the security (encryption) option. His feedback was IMHO valuable:
Currently the GUI (CallParticipantPanel) shows a closed padlock to
display the state if encryption support is enabled or not
That was confusing: even if the padlock was "gray" he assumed the
call is secure. His association was: a browser shows a padlock if
the pages are secure - or nothing is shown. A closed padlock always
signals "security" regardless of the colour. The ZRTP specific
status pages were regarded as "additional information to know what
is going on" .
My proposal is:
- either remove this button - its functions to dynamically
switch on/off security during the call is not supported anymore because
of interoperability problems with other ZRTP clients. It's a mere
status indicator
or
- find a better symbol (icon) to show the encryption support on/off
status - but definitely not a padlock .
In the ZRTP specific GUI part I have removed the "gray" padlock.
If encryption is not active the button is empty and show a padlock
only if encryption is active.
How about having an open padlock for unsecured and a closed padlock for
secure? And then make it a simple status icon somewhere on the GUI instead
of a dynamic button? This is what I would suggest, as someone who does a lot
of GUI work, to make it clear to the user what is going on. One of many
reasons for showing an open padlock, instead of no padlock (for unsecured),
is so that the user knows that the feature is working properly but is not
enabled.
You could also put a red slash through the padlock to indicate unsecured.
Sent: Sunday, December 14, 2008 5:44 AM
To: dev@sip-communicator.dev.java.net
Subject: [sip-comm-dev] GUI modifications for Secure Call
All,
during the updates for ZRTP callback and the ZRTP specific part of the GUI I
took the chance to show the overall GUI to a friend who is not a software
developer or even a "nerd" , just a normal Windows user.
I showed him the features how to set up a SIP call, and showed him the
security (encryption) option. His feedback was IMHO valuable:
Currently the GUI (CallParticipantPanel) shows a closed padlock to display
the state if encryption support is enabled or not
That was confusing: even if the padlock was "gray" he assumed the call is
secure. His association was: a browser shows a padlock if the pages are
secure - or nothing is shown. A closed padlock always signals "security"
regardless of the colour. The ZRTP specific status pages were regarded as
"additional information to know what is going on" .
My proposal is:
- either remove this button - its functions to dynamically
switch on/off security during the call is not supported anymore because
of interoperability problems with other ZRTP clients. It's a mere
status indicator
or
- find a better symbol (icon) to show the encryption support on/off
status - but definitely not a padlock .
In the ZRTP specific GUI part I have removed the "gray" padlock.
If encryption is not active the button is empty and show a padlock only if
encryption is active.
On Sun, Dec 14, 2008 at 02:37:40PM -0500, Alan Kelly wrote:
How about having an open padlock for unsecured and a closed padlock for
secure? And then make it a simple status icon somewhere on the GUI instead
of a dynamic button? This is what I would suggest, as someone who does a lot
of GUI work, to make it clear to the user what is going on. One of many
reasons for showing an open padlock, instead of no padlock (for unsecured),
is so that the user knows that the feature is working properly but is not
enabled.
You could also put a red slash through the padlock to indicate unsecured.
The red slashed padlock would be more recognizable than the open
padlock. But it shouldn't be made too big no to scare the users as ZRTP
is not that common (yet).
here are some padlock icons. Bigger? Changes? Comments ?
People should be scared if the call is not secure.
Regards, Earl
Sébastien Mazy wrote:
···
Hi,
On Sun, Dec 14, 2008 at 02:37:40PM -0500, Alan Kelly wrote:
How about having an open padlock for unsecured and a closed padlock for
secure? And then make it a simple status icon somewhere on the GUI instead
of a dynamic button? This is what I would suggest, as someone who does a lot
of GUI work, to make it clear to the user what is going on. One of many
reasons for showing an open padlock, instead of no padlock (for unsecured),
is so that the user knows that the feature is working properly but is not
enabled.
You could also put a red slash through the padlock to indicate unsecured.
The red slashed padlock would be more recognizable than the open
padlock. But it shouldn't be made too big no to scare the users as ZRTP
is not that common (yet).
open/closed padlock is a good idea IMHO. The KDE theme Crystal Clear
also has nice open/closed padlock (attached).
Regards,
Werner
Earl schrieb:
Hi,
here are some padlock icons. Bigger? Changes? Comments ?
People should be scared if the call is not secure.
Regards, Earl
S�bastien Mazy wrote:
Hi,
How about having an open padlock for unsecured and a closed padlock for
secure? And then make it a simple status icon somewhere on the GUI instead
of a dynamic button?
Attached also a proposal for a status icon that shows if security option
is enabled or not (SecureOn and SecureOff, SVG is available). Basically
it's s shield that contains the SC logo.
Please bear in mind: I'm not a graphic designer - that's just a sketch.
Any idea where we can place the image for example at the call participant
panel? For a button this image is too big.
···
On Sun, Dec 14, 2008 at 02:37:40PM -0500, Alan Kelly wrote:
open/closed padlock is a good idea IMHO. The KDE theme Crystal Clear
also has nice open/closed padlock (attached).
Yes, very nice and looks alike the padlock used in Firefox. If you're
going for a padlck for both icons, could you please make it big enough
so that the states are easily recognizable?.
Attached also a proposal for a status icon that shows if security option
is enabled or not (SecureOn and SecureOff, SVG is available). Basically
it's s shield that contains the SC logo.
I think the padlock convey the idea of encryption better. A shield makes
me think more of something that prevents certain connexions (typically a
firewall).
Please bear in mind: I'm not a graphic designer - that's just a sketch.
You never saw me try to draw something
Any idea where we can place the image for example at the call participant
panel? For a button this image is too big.
A label left to the "hangup" button?
By the way, do you know of a ZRTP "echo test"?
Cheers,
···
On Mon, Dec 15, 2008 at 02:48:17PM +0100, Werner Dittmann wrote:
I took the crystal theme padlocks and changed the colors a little
to give more visual impact and clarity.
In my opinion, the yellow + black bars means "under construction"
there is still negotiations and hand-shaking proceeding, but once
the encrypted connection is successful, I would prefer to see only
green and no more yellow + black bars.
What do you think?
Regards, Earl
Werner Dittmann wrote:
···
Hi,
open/closed padlock is a good idea IMHO. The KDE theme Crystal Clear
also has nice open/closed padlock (attached).
Regards,
Werner
Earl schrieb:
Hi,
here are some padlock icons. Bigger? Changes? Comments ?
People should be scared if the call is not secure.
Regards, Earl
S�bastien Mazy wrote:
Hi,
On Sun, Dec 14, 2008 at 02:37:40PM -0500, Alan Kelly wrote:
How about having an open padlock for unsecured and a closed padlock for
secure? And then make it a simple status icon somewhere on the GUI instead
of a dynamic button?
Attached also a proposal for a status icon that shows if security option
is enabled or not (SecureOn and SecureOff, SVG is available). Basically
it's s shield that contains the SC logo.
Please bear in mind: I'm not a graphic designer - that's just a sketch.
Any idea where we can place the image for example at the call participant
panel? For a button this image is too big.
attached a screen shot of a new secure call GUI proposal:
- took the padlocks as modified by Earl and use them to
show encrypted/unencrypted state
- Used S�bastien's idea a placed the "secure mode supported"
icon left to the hangup button - note the new status button
design . Would this classify as an idea? (I took a background
from a SC button and overlayed it with a key)
- The SAS verification is now done with a check box. IMHO shows better
the intend. Using the security symbol as a button was not too clear
to my "test user".
Some notes: the background of the padlocks is black and doesn't fit the
overall colour scheme of SC. Also it seems they are too big. I don't know
how to adjust the size of the surrounding panel with grid layout to fit
the size.
The SAS check boy has the wrong background even if I use SIPCommCheckbox
here - maybe Lubo can check if the relevant stuff if exported to the
main GUI ? Or are there other ways to define a similar way to "check"
a specific datum?
Ideas? Thoughts?
Regards,
Werner
Earl schrieb:
···
Werner,
I took the crystal theme padlocks and changed the colors a little
to give more visual impact and clarity.
In my opinion, the yellow + black bars means "under construction"
there is still negotiations and hand-shaking proceeding, but once
the encrypted connection is successful, I would prefer to see only
green and no more yellow + black bars.
Sorry for not chiming in earlier. I'm actually working on the Call UI right now (inspired by zfone's) and hope to be able to commit soon (relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll like it. Therefore, could you please hold on before you commit anything in order to avoid any conflicts?
Sorry again for the late notice.
Cheers
Yana
Werner Dittmann wrote:
···
Earl, all,
attached a screen shot of a new secure call GUI proposal:
- took the padlocks as modified by Earl and use them to
show encrypted/unencrypted state
- Used S�bastien's idea a placed the "secure mode supported"
icon left to the hangup button - note the new status button
design . Would this classify as an idea? (I took a background
from a SC button and overlayed it with a key)
- The SAS verification is now done with a check box. IMHO shows better
the intend. Using the security symbol as a button was not too clear
to my "test user".
Some notes: the background of the padlocks is black and doesn't fit the
overall colour scheme of SC. Also it seems they are too big. I don't know
how to adjust the size of the surrounding panel with grid layout to fit
the size.
The SAS check boy has the wrong background even if I use SIPCommCheckbox
here - maybe Lubo can check if the relevant stuff if exported to the
main GUI ? Or are there other ways to define a similar way to "check"
a specific datum?
Ideas? Thoughts?
Regards,
Werner
Earl schrieb:
Werner,
I took the crystal theme padlocks and changed the colors a little
to give more visual impact and clarity.
In my opinion, the yellow + black bars means "under construction"
there is still negotiations and hand-shaking proceeding, but once
the encrypted connection is successful, I would prefer to see only
green and no more yellow + black bars.
thanks for the info, no problem at all. The GUI is just here in my
Sandbox to play around with possible solutions. Other modifications
are related to messages and texts and not to the GUI, thus I can
easily check conflicts.
Regards,
Werner
Yana Stamcheva schrieb:
···
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI right now (inspired by zfone's) and hope to be able to commit soon (relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll like it. Therefore, could you please hold on before you commit anything in order to avoid any conflicts?
Sorry again for the late notice.
Cheers
Yana
Werner Dittmann wrote:
Earl, all,
attached a screen shot of a new secure call GUI proposal:
- took the padlocks as modified by Earl and use them to
show encrypted/unencrypted state
- Used S�bastien's idea a placed the "secure mode supported"
icon left to the hangup button - note the new status button
design . Would this classify as an idea? (I took a background
from a SC button and overlayed it with a key)
- The SAS verification is now done with a check box. IMHO shows better
the intend. Using the security symbol as a button was not too clear
to my "test user".
Some notes: the background of the padlocks is black and doesn't fit the
overall colour scheme of SC. Also it seems they are too big. I don't know
how to adjust the size of the surrounding panel with grid layout to fit
the size.
The SAS check boy has the wrong background even if I use SIPCommCheckbox
here - maybe Lubo can check if the relevant stuff if exported to the
main GUI ? Or are there other ways to define a similar way to "check"
a specific datum?
Ideas? Thoughts?
Regards,
Werner
Earl schrieb:
Werner,
I took the crystal theme padlocks and changed the colors a little
to give more visual impact and clarity.
In my opinion, the yellow + black bars means "under construction"
there is still negotiations and hand-shaking proceeding, but once
the encrypted connection is successful, I would prefer to see only
green and no more yellow + black bars.
Here are padlocks with white background.
I also cleaned up the yellow and black bars.
Regards, Earl
Werner Dittmann wrote:
···
Yana,
thanks for the info, no problem at all. The GUI is just here in my
Sandbox to play around with possible solutions. Other modifications
are related to messages and texts and not to the GUI, thus I can
easily check conflicts.
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI right now (inspired by zfone's) and hope to be able to commit soon (relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll like it. Therefore, could you please hold on before you commit anything in order to avoid any conflicts?
Sorry again for the late notice.
Cheers
Yana
Werner Dittmann wrote:
Earl, all,
attached a screen shot of a new secure call GUI proposal:
- took the padlocks as modified by Earl and use them to
show encrypted/unencrypted state
- Used S�bastien's idea a placed the "secure mode supported"
icon left to the hangup button - note the new status button
design . Would this classify as an idea? (I took a background
from a SC button and overlayed it with a key)
- The SAS verification is now done with a check box. IMHO shows better
the intend. Using the security symbol as a button was not too clear
to my "test user".
Some notes: the background of the padlocks is black and doesn't fit the
overall colour scheme of SC. Also it seems they are too big. I don't know
how to adjust the size of the surrounding panel with grid layout to fit
the size.
The SAS check boy has the wrong background even if I use SIPCommCheckbox
here - maybe Lubo can check if the relevant stuff if exported to the
main GUI ? Or are there other ways to define a similar way to "check"
a specific datum?
Ideas? Thoughts?
Regards,
Werner
Earl schrieb:
Werner,
I took the crystal theme padlocks and changed the colors a little
to give more visual impact and clarity.
In my opinion, the yellow + black bars means "under construction"
there is still negotiations and hand-shaking proceeding, but once
the encrypted connection is successful, I would prefer to see only
green and no more yellow + black bars.
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll
like it. Therefore, could you please hold on before you commit anything
in order to avoid any conflicts?
I think I'll be able to commit next week. Do you have something in mind?
Cheers,
Yana
Werner Dittmann wrote:
···
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll
like it. Therefore, could you please hold on before you commit anything
in order to avoid any conflicts?
nothing in particular, mainly testing and translating messages in case
of errors or ZRTP failures etc. Some messages may pop up during ZRTP
operations and I just will make sure that the right messages show up.
Regards,
Werner
Yana Stamcheva schrieb:
···
Hi Werner,
I think I'll be able to commit next week. Do you have something in mind?
Cheers,
Yana
Werner Dittmann wrote:
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll
like it. Therefore, could you please hold on before you commit anything
in order to avoid any conflicts?
No problem, will ping you as soon as it's in the trunk!
Cheers,
Yana
Werner Dittmann wrote:
···
Hi Yana,
nothing in particular, mainly testing and translating messages in case
of errors or ZRTP failures etc. Some messages may pop up during ZRTP
operations and I just will make sure that the right messages show up.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner,
I think I'll be able to commit next week. Do you have something in mind?
Cheers,
Yana
Werner Dittmann wrote:
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll
like it. Therefore, could you please hold on before you commit anything
in order to avoid any conflicts?
I've committed some general modifications in the call dialog, but nothing particular yet for the secure call. Just wanted to ensure you that this is work in progress and the interface is not finished yet.
I've made a lot of tests with ZRTP these days and will give you some feedback as soon as I finish with all the other stuff (which should be during the weekend).
Cheers,
Yana
Werner Dittmann wrote:
···
Hi Yana,
nothing in particular, mainly testing and translating messages in case
of errors or ZRTP failures etc. Some messages may pop up during ZRTP
operations and I just will make sure that the right messages show up.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner,
I think I'll be able to commit next week. Do you have something in mind?
Cheers,
Yana
Werner Dittmann wrote:
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope you'll
like it. Therefore, could you please hold on before you commit anything
in order to avoid any conflicts?
I was busy with some new ZRTP versions and interop testing .
Thus it's perfect timing.
Regards,
Werner
Yana Stamcheva schrieb:
···
Hi Werner, all,
I've committed some general modifications in the call dialog, but
nothing particular yet for the secure call. Just wanted to ensure you
that this is work in progress and the interface is not finished yet.
I've made a lot of tests with ZRTP these days and will give you some
feedback as soon as I finish with all the other stuff (which should be
during the weekend).
Cheers,
Yana
Werner Dittmann wrote:
Hi Yana,
nothing in particular, mainly testing and translating messages in case
of errors or ZRTP failures etc. Some messages may pop up during ZRTP
operations and I just will make sure that the right messages show up.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner,
I think I'll be able to commit next week. Do you have something in mind?
Cheers,
Yana
Werner Dittmann wrote:
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope
you'll
like it. Therefore, could you please hold on before you commit
anything
in order to avoid any conflicts?
just a quick question. I saw the following comment in the SecureButton class:
// TODO GoClear
// We deactivate the tooltip at the moment, because the
// secure mode cannot be toggled off.
Do you have any idea if this is still the case ?
Is this for the same reason that we have SECURITY_ENABLED event and don't have SECURITY_DISABLED?
Cheers,
Yana
Werner Dittmann wrote:
···
Thanks Yana.
I was busy with some new ZRTP versions and interop testing .
Thus it's perfect timing.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner, all,
I've committed some general modifications in the call dialog, but
nothing particular yet for the secure call. Just wanted to ensure you
that this is work in progress and the interface is not finished yet.
I've made a lot of tests with ZRTP these days and will give you some
feedback as soon as I finish with all the other stuff (which should be
during the weekend).
Cheers,
Yana
Werner Dittmann wrote:
Hi Yana,
nothing in particular, mainly testing and translating messages in case
of errors or ZRTP failures etc. Some messages may pop up during ZRTP
operations and I just will make sure that the right messages show up.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner,
I think I'll be able to commit next week. Do you have something in mind?
Cheers,
Yana
Werner Dittmann wrote:
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope
you'll
like it. Therefore, could you please hold on before you commit
anything
in order to avoid any conflicts?
I'm experiencing some problems with ZRTP, hope that you could help me.
Actually no one of secureOn, secureOff or showSAS methods is ever called, while I see with zfone that the call is secured. I'm probably misunderstanding something, but I hoped to receive a SecurityGUIEventZrtp in the gui in order to be able to show to the user the secure strings. Did I missed something?
Cheers,
Yana
Yana Stamcheva wrote:
···
Hi Werner,
just a quick question. I saw the following comment in the SecureButton class:
// TODO GoClear
// We deactivate the tooltip at the moment, because the
// secure mode cannot be toggled off.
Do you have any idea if this is still the case ?
Is this for the same reason that we have SECURITY_ENABLED event and don't have SECURITY_DISABLED?
Cheers,
Yana
Werner Dittmann wrote:
Thanks Yana.
I was busy with some new ZRTP versions and interop testing .
Thus it's perfect timing.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner, all,
I've committed some general modifications in the call dialog, but
nothing particular yet for the secure call. Just wanted to ensure you
that this is work in progress and the interface is not finished yet.
I've made a lot of tests with ZRTP these days and will give you some
feedback as soon as I finish with all the other stuff (which should be
during the weekend).
Cheers,
Yana
Werner Dittmann wrote:
Hi Yana,
nothing in particular, mainly testing and translating messages in case
of errors or ZRTP failures etc. Some messages may pop up during ZRTP
operations and I just will make sure that the right messages show up.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner,
I think I'll be able to commit next week. Do you have something in mind?
Cheers,
Yana
Werner Dittmann wrote:
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope
you'll
like it. Therefore, could you please hold on before you commit
anything
in order to avoid any conflicts?
At first the SecureButton was implemented to enable a user to switch on
encryption during the call or switch it off during the call. However,
some interop tests showed that other ZRTP implementations do not support
this feature to switch on security _during_ the call. Thus we introduced
to switch on security in the SIP account configuration (the extended part).
Thus the SecureButton is now an inidicator only to show if ZRTP security
is _avaliable_.
It works as follows:
During setup of the media streams (the RTP managers) we initialize the
ZRTP engine. If initialization was successful the SCCallback class is
initialized and sends the SECURITY_ENABLED event. Because we disabled the
feature to switch off security during the call there is no SECURITY_DISABLED
event and also the action of the SecureButton is disabled. In addtion,
because the SecureButton is a mere indicator only, I made the proposal to
change the icon from a padlock to a key symbol (see attached png/svg file)
that signals: security is _available_. The padlock symbols should be reserved
to indicate if encryption is really switched on (or not)
Please feel free to brush up the key symbol :-).
regards,
Werner
Yana Stamcheva schrieb:
···
Hi Werner,
just a quick question. I saw the following comment in the SecureButton
class:
// TODO GoClear
// We deactivate the tooltip at the moment, because the
// secure mode cannot be toggled off.
Do you have any idea if this is still the case ?
Is this for the same reason that we have SECURITY_ENABLED event and
don't have SECURITY_DISABLED?
Cheers,
Yana
Werner Dittmann wrote:
Thanks Yana.
I was busy with some new ZRTP versions and interop testing .
Thus it's perfect timing.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner, all,
I've committed some general modifications in the call dialog, but
nothing particular yet for the secure call. Just wanted to ensure you
that this is work in progress and the interface is not finished yet.
I've made a lot of tests with ZRTP these days and will give you some
feedback as soon as I finish with all the other stuff (which should be
during the weekend).
Cheers,
Yana
Werner Dittmann wrote:
Hi Yana,
nothing in particular, mainly testing and translating messages in case
of errors or ZRTP failures etc. Some messages may pop up during ZRTP
operations and I just will make sure that the right messages show up.
Regards,
Werner
Yana Stamcheva schrieb:
Hi Werner,
I think I'll be able to commit next week. Do you have something in
mind?
Cheers,
Yana
Werner Dittmann wrote:
Yana,
are there any news about the new Call UI?
Regards,
Werner
Yana Stamcheva schrieb:
Hey all,
Sorry for not chiming in earlier. I'm actually working on the
Call UI
right now (inspired by zfone's) and hope to be able to commit soon
(relatively ).
I believe I'm taking all your suggestions into account, so I hope
you'll
like it. Therefore, could you please hold on before you commit
anything
in order to avoid any conflicts?
, just a
.
- that's just a sketch.
).
