Dimdim does not currently retain any content that is uploaded or shared during a meeting. This means that all chat messages, audio or video streams, shared presentations which are used are purged at the end of the hosted meeting. Further, no one can join your meeting or view your shared content without your knowledge since they require your unique meeting key. Finally, all meeting attendees are indicated in the participants list. It is possible to restrict entry to your meeting room by enabling the Waiting Room.
If you plan to deploy your own onsite Dimdim server you can secure it behind https and firewalls.
With Dimdim 4.0 we've implemented a new meeting key feature that requires the attendee to enter both the meeting room name and the meeting key (aka password)
How secure is a meeting with Dimdim?
Would you like to...
User Opinions (17 votes)
76%
23%
Visitor Comments
-
Comment #1 (Posted by john b gleason
)
I see a big security problem the way it is set up now. Anyone who knows the host's "Meeting Room Name" which is the same as his dimdim ID, can easily join the room at any time there is a meeting underway. This is not a good thing. Sure there is a lobby feature, but who wants to be bothered stopping and starting a conference to screen people through a check point. A better suggestion would be to have a secret PASSWORD for every meeting. Or with a prefernce to leave the password as is until changed. For example, as the host my invitaion would go out to the attenndees with instructions how to Join meeting, telling them under "meeting name" they must enter "footprint" or it could be an extension of my ID (which is jb99) such as jb99-footprint. Please advise if there is an existing feature which would accomplish the same results, if not please advise. Thank you JB