Login or Register to Ask a Question and Join Our Community


OS X Support RSS

MobileMe: Setting up and troubleshooting secure iChat

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS MobileMe: Setting up and troubleshooting secure iChat
# 1  
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 ...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

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
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

mulog

MULOG(1)							Museek Daemon Plus							  MULOG(1)

NAME

       Mulog - Chat Logging Script for Museekd

DESCRIPTION

       Mulog is command-line Python script that connects to museekd(1) and saves chat messages into log files. Under the Log Directory, it creates
       room & private subdirectories and a syslog file. If it loses connection with museekd, it will automatically exit.

       Setting the interface and password on the command-line is a security risk. Since interface and password settings are saved  to  the  config
       file when set, you should set them, exit mulog, and restart mulog without the options on the commandline..LP

       Before  running,  you  will  need a working museekd(1) and need to know your museekd interface and interface password. Configure those with
       musetup(1).

SYNOPSIS

       mulog [-c <config-filename> ] [--config <config-filename>] [-i <host:port | /socket.path>]  [--interface  <host:port  |	/socket.path>  [-p
       <interface-password>] [--password <inteface-password>] [-l <directory>] [--log <directory>] [-v] [--version] [-h] [--help]

OPTIONS

       Mulog accepts the following options:

       -c <filename>, --config <filename>
	      Use a different config file.

       -l <directory>, --log <directory>
	      Use a different chat log directory.

       -i, --interface <host:port | /socket.path>
	      Choose a different interface (saved to config file)

       -p, --password <interface-password>
	      Choose a different password (saved to config file)

       -v, --version
	      Display Version and exit.

       -h, --help
	      Display Help and exit.

EXAMPLE

       To run this program the standard way type:

       mulog

       Alternativly you use a different config file with:

       mulog --config mulog.config

       To set the interface password:

       mulog --password 1234567890

FILES

	~/.museekd/mulog.config
	      The default location for the mulog config file.

	~/.museekd/logs/
	      The default log directory.

	~/.museekd/logs/syslog
	      The museekd error/connection log file.

	~/.museekd/logs/room/
	      The directory where chat room logs are stored.

	~/.museekd/logs/private/
	      The directory where private chat logs are stored.

AUTHORS

       Hyriand <hyriand@thegraveyard.org>

       daelstorm <daelstorm@gmail.com>

SEE ALSO

       mucous(1) murmur(1) muscan(1) muscand(1)museekcontrol(1) museekd(1) musetup(1) musetup-gtk(1) museeq(1)

daelstorm							   Release 0.2.0							  MULOG(1)