Sponsored Content
Operating Systems OS X (Apple) OS X Support RSS MobileMe: Setting up and troubleshooting secure iChat Post 302258522 by Linux Bot on Friday 14th of November 2008 06:00:03 PM
Old 11-14-2008
MobileMe: Setting up and troubleshooting secure iChat

MobileMe enhances iChat in Mac OS X 10.5 Leopard by providing a means for creating secure chat interactions between MobileMe subscribers. In a secure chat text, audio, or video chat, all data transferred in the chat is encrypted. To use this safeguard, you and your chat buddy must both have MobileMe memberships and enable Secure Chat.When both you and your chat buddy have MobileMe Secure iChat enabled and you start a chat, a lock icon appears in the upper-right corner of the iChat window. Text, audio and video are encrypted on your computer, sent across the Internet encrypted, and are not decrypted until they reach your buddy’s computer.

More from Apple OS X Support ...
 

We Also Found This Discussion For You

1. AIX

Setting up a secure channel with AIX

hi i have two aix servers and I was asked to setup a secure shell between the two servers using the sybase user. Can any one let me know how to do this (2 Replies)
Discussion started by: newtoaixos
2 Replies
NAGZILLAC(1)						      General Commands Manual						      NAGZILLAC(1)

NAME
nagzillac - jabber relay bot client SYNOPSIS
nagzillac type^JID^message DESCRIPTION
This manual page documents briefly the nagzillac command. nagzillac is the client for nagzilla that takes the data you hand it as argument and sends it over to the nagzilla daemon that will send the message along. OPTIONS
nagzillac only takes one options that consists of three arguments. They are seperated by the carret character(`^'), although the last argu- ment may contain carrets without any troubles. Here is an explenation of the different parts: type This is the type of the message. It can be either room (which will send the message to a jabber conference room) or chat (target should be a jabber ID). JID This is the target for the message. If you choose room type it has to be a conference room name or complete ID. A single room with- out any @ in it will get sent to the configured conference server. If you choose the chat type the JID has to be the jabber ID of the user to receive the message, either just the user part which will get added the jabber server as domain part, or a full jabber ID. message The final part is the message that will get sent. At the moment it will be put into the body as plain text. Please notice that you will have to quote or escape special characters in the message like white space. FILES
/etc/nagzillac/nagzillac.cfg The configuration file for the nagzilla client. Please see the comments in the file for informations on what to tweak. EXAMPLE
The following sends a chat message to the rhonda user on the default server: nagzillac "chat^rhonda^hi there" This will send a message to a conference room on a different server: nagzillac "room^monitor@jabber.doma.in^alert - do something" SEE ALSO
nagzillad(1). AUTHOR
nagzillac was written by Bill Mathews. This manual page was written by Gerfried Fuchs <rhonda@debian.at> for the Debian project (and may be used by others). 2009-06-03 NAGZILLAC(1)
All times are GMT -4. The time now is 01:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy