184
edits
IFD:Nutzerstudien WiSe1314/Sicherheit (security) (view source)
Revision as of 12:23, 21 December 2013
, 21 December 2013→Data Analysis
No edit summary |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 78: | Line 78: | ||
<div style="color:brown">I'd like to see more discussion of your approach here. How did you choose your people? What criteria did you use to develop your questions?</div>--[[User:Hans|Hans]] 21:43, 18 December 2013 (CET) | <div style="color:brown">I'd like to see more discussion of your approach here. How did you choose your people? What criteria did you use to develop your questions?</div>--[[User:Hans|Hans]] 21:43, 18 December 2013 (CET) | ||
We chose them, because they are part of our social environment. We thought about what would be important for ourselves to develop the questions. Since we`re in the security-group we tried to focus especially on that topic. | |||
==Main Results Data Analysis== | ==Main Results Data Analysis== | ||
| Line 84: | Line 85: | ||
'''Results:''' | '''Results:''' | ||
* Most people use chat programs that are unsafe. The amount of friends that use a specific chat is more important <div style="color:brown">did the users know that the apps they use were unsafe?</div>--[[User:Hans|Hans]] 21:44, 18 December 2013 (CET) | * Most people use chat programs that are unsafe. The amount of friends that use a specific chat is more important <div style="color:brown">did the users know that the apps they use were unsafe?</div>--[[User:Hans|Hans]] 21:44, 18 December 2013 (CET) | ||
Yes, they do, but it doesn`t bother them. | |||
* Standard functions like Smileys and data/picture transfer should be offered | * Standard functions like Smileys and data/picture transfer should be offered | ||
* There should be a function to create a group discussion | * There should be a function to create a group discussion | ||
| Line 99: | Line 101: | ||
However, they did not try to find an alternative. Related to this we also found out that people using chat software for business had much more concerns about their personal information and especially the topic and content of the talk then the private users. | However, they did not try to find an alternative. Related to this we also found out that people using chat software for business had much more concerns about their personal information and especially the topic and content of the talk then the private users. | ||
<div style="color:brown">You bring up a lot of valuable points here, and the bullet points provide a quick summary, but I'd love to hear more about all of the topics. In particular, I think the core issue is why people don't find more secure/private alternatives to the apps that they use. Is it social (everyone I know uses Xapp)? Is it usability (private apps are hard to use)?</div>--[[User:Hans|Hans]] 21:50, 18 December 2013 (CET) | <div style="color:brown">You bring up a lot of valuable points here, and the bullet points provide a quick summary, but I'd love to hear more about all of the topics. In particular, I think the core issue is why people don't find more secure/private alternatives to the apps that they use. Is it social (everyone I know uses Xapp)? Is it usability (private apps are hard to use)? Or something else entirely?</div>--[[User:Hans|Hans]] 21:50, 18 December 2013 (CET) | ||
Since insecurity in their currently chats doesn`t bother them much, they just haven`t thought about a secure alternative yet. Most important thing has always been, that all friends use the app/chat. They would change to a secure chat, where all friends are logged in, though. | |||
==What specific problem we want to solve== | ==What specific problem we want to solve== | ||
The interface should communicate security to the user. | The interface should communicate security to the user. Therefore we want to improve the interface of ChatSecure in a way, that everyone is able to understand what is meant with the symbols. | ||
To create such a design, we drew some of our own design-ideas on a paper. It showed the message window and some applications and icons we added to it, e.g. the lock symbol next to the Accountname and in the speech bubbles itself. These things intensify the security-feeling. Then we discussed those ideas, made a prototype and tested it on a comrade who wasn`t in our working group. | To create such a design, we drew some of our own design-ideas on a paper. It showed the message window and some applications and icons we added to it, e.g. the lock symbol next to the Accountname and in the speech bubbles itself. These things intensify the security-feeling. Then we discussed those ideas, made a prototype and tested it on a comrade who wasn`t in our working group. | ||
[[image:IFD-NuSt security-mockup.jpg|1000px]] | [[image:IFD-NuSt security-mockup.jpg|1000px]] | ||
<div style="color:brown">Its good to see the mockups, this gets the process rolling. About the prompt for sending messages insecurely, this would work well for people in very sensitive situations, but I think most users would get annoyed once they've seen a pop-up like this more than 5 or 10 times. I think that it is possible to achieve the same results security-wise with less annoyance on the user by integrating this warning more. For example, the Send button should change color like you have already but maybe instead of the yes/no/later prompt, the user would have to press the send button twice, and it would change color on each press. For more security, there could be an enforced delay on the second press, so they would have to wait a second or two before clicking it the second time. Or mybe it would be enough if the whole interface was shouting out that the message would be sent insecurely, something like every aspect of the UI turning red, and getting a different font.</div>--[[User:Hans|Hans]] 21:56, 18 December 2013 (CET) | |||
<!-- | <!-- | ||