 Freedom(R) 2.1
 ================


                     Release Notes
 
Contents:
 
Hardware and software requirements........................1.0
Installation..............................................2.0
  A note about the kernel module..........................2.1
  Installing Freedom 2.1..................................2.2
  Configuring Freedom Mail................................2.3
  RPM dependencies........................................2.4
Freedom 2.0...............................................3.0
  What's in 2.0?..........................................3.1
  What's in 2.01?.........................................3.2
  What's in 2.01b?........................................3.3
  What's in 2.1?..........................................3.4
  Known issues............................................3.5
Getting help & giving feedback............................4.0 
 
 
----- 1.0  Hardware and Software Requirements -----
 
Freedom 2.1 officially supports the following distribution on a 
Pentium or higher x86 based system.

 - Redhat 6.2
 
  Freedom requires GNOME. You must install GNOME to run
  Freedom. (Note that GNOME does not need to be your
  current desktop.)

You must also have Linux's networking components correctly
configured and functional on your machine.
 
----- 2.0  Installation -----

Freedom 2.1 is distributed as a binary via RPM. Additionally,
the source and build instructions are available at:

 http://opensource.zeroknowledge.com


----- 2.1  A note about the kernel module -----

Freedom 2.1 installs a kernel module that is sensitive to
different kernel versions and configurations. If you are not
using the stock kernel for your distribution, you will need to
manually build the kernel module on your computer. There are
simple instructions for doing so in the INSTALL.DRIVER file in
the /usr/share/freedom/doc directory.


----- 2.2  Installing Freedom from RPM -----

Use your favorite graphical RPM app, or enter the following
command (as root):

  rpm -Uvh <name of Freedom RPM>

To launch Freedom after it has been installed, enter the
following command as a non-root user:

  /usr/share/bin/freedom
  
If you wish to install Freedom in another location, you can
do so by adding an environment variable named FREEDOM_HOME
set to the location of the root freedom folder.

Note that Freedom works by anonymizing all traffic that
originates from the user who has run Freedom. Any applications
running as another user will NOT be "anonymized". Freedom
cannot be run as root.


----- 2.3  Configuring Freedom Mail -----

To use Freedom mail, all you need is a mail application configured
to use POP and either sendmail or a remote SMTP server. When you have
a nym selected, mail sent using your regular mail application will
appear to come from your nym, and you will automatically receive mail
sent to your nyms.

If you do not have a POP or SMTP server, or if you wish to use a
separate mail application for your Freedom mail, you can configure
it with the following information:

username/account      freedom
password              freedom
POP server            mail.freedom.net
SMTP server           mail.freedom.net

(This is not an actual mail server. It indicates Freedom should
operate even in the absence of "real" mail servers.)


----- 2.4  RPM Dependencies -----

The following is a list of packages that must be installed in order
to successfully install Freedom from RPM:

XFree86
audiofile
esound
glib
glibc
gnome-libs
gtk+
imlib
libjpeg
libpng
libtiff
libxml
zlib

Please note that the required libraries may be provided by packages with 
slightly different package names for non-Red Hat distributions.

For example: on SuSE "XFree86-libs" is replaced by "xshared".


----- 3.0  Freedom 2.0 -----

Freedom 2.0 is designed to make online privacy easier and
more accessible. 

Freedom 2.0 includes:

 - Standard and Premium nyms
 - An intuitive User Interface
 - The Freedom mail system
 - The Ad Manager
 

----- 3.1  What's in 2.0? -----
 
This was released in December 2000.

Standard and Premium Nyms

 Freedom 2.0 includes a new type of nym. Standard nyms can
 be created without purchasing an activation code, and give
 you access to many of the privacy features of Freedom, for
 free. Standard nyms include access to the Ad Manager,
 Cookie Manager and Keyword Alert.
 
 Premium nyms include all the above features, as well as
 Freedom Mail and access to the Freedom Network for
 anonymous browsing, IRC, news and telnet.

----- 3.2  What's in 2.01? -----
 
This was released in January 2001.

New:

 - Additional event console logging has been added to POP 
   proxy transactions.

 - Updated network information files (Niqs.Cache and Keys.cache).

 - A diagnostic script has been provided for the Linux client. 
   This script provides some basic system configuration information.

Improved:

 - Standard nym users will no longer experience difficulties sending
   email and posting to newsgroups.

 - Fix of Error sending mail: 'Freedom failed to find the public 
   key for...' problem.

 - This release also contains a wide range of visual/textual bug fixes.
 
 Please consult the following Knowledge Base Center Article
 for more information on the Freedom v2.1 release:
 
 http://www.freedom.net/support/article.html?article=325

----- 3.3  What's in 2.01b? -----

This was released in March 2001.

Freedom version 2.01b is the first in a series of releases that will help with 
the migration to the new and improved Freedom Network released with 2.1.

 Please consult the following Knowledge Base Center Article
 for more information on the Freedom 2.01b release:
 
 http://www.freedom.net/support/article.html?article=343

----- 3.4  What's in 2.1? -----
 
This was released in April 2001.


The Freedom 2.1 release contains a wide range of fixes, changes and
improvements. Over 200 bugs have been fixed. Some of the major new
changes include:

 New AIP 2.0 Support
 This Freedom Client release includes support for a number of changes in the
 Freedom network and protocols that increase performance and reliability.

 NIQS update reliability
 Client updates from the NIQS server are now performed in the clear. This
 carries no security risk and improves reliability.

 Network reliability
 Route prolong failures causing errors downloading mail and other extended
 network activities (e.g.: IRC) have been fixed. Additional changes have been
 made to improve the reliability of connections to core servers
 (specifically Nym server and Token server).

 Freedom Mail
 Major changes have been made to the sending of Freedom mail. Freedom mail
 will be more reliable and faster.

 Please consult the following Knowledge Base Center Article
 for more detailed information on the Freedom 2.1 release:
 
 http://www.freedom.net/support/article.html?article=348


----- 3.5  Known issues -----
 
Freedom and NFS

 Freedom only "anonymizes" traffic initiated by the user
 (real UID) that ran the Freedom program.
 
 Generally this is desirable behavior; for example the operation
 of a web server on your machine will not be affected. However 
 if the user indirectly transmits information through a system
 service already running, the traffic may be unexpectedly sent
 out in the clear.
 
 An example of this is NFS. If you mount a directory using NFS,
 traffic will be sent and received for it _without_ being
 "anonymized". You should be careful not to have your browser
 cache or other sensitive information in an NFS mounted
 directory.
 
Freedom cannot be run remotely

 When Freedom runs, it blocks all connections not routed
 through the Freedom Network for the user that ran Freedom.
 Because of this, if you are using X to send packets over a
 TCP connection (as is the case if you have set DISPLAY to
 hostname:x manually, or via SSH) the connection will be cut
 off until Freedom exits. Freedom must be run as a user on
 your local machine.

Poor performance with older glibc

 Systems that use versions of glibc older than 2.1.3 (such as
 Red Hat 6.1) may experience poor performance using Freedom.
 We strongly recommend that you upgrade to a recent version
 of glibc.

 If you are using Red Hat 6.1, enter the following as root
 on a single line:

 rpm -Uvh ftp://rpmfind.net/linux/redhat/redhat-6.2/i386/
  RedHat/RPMS/glibc-2.1.3-15.i386.rpm

 Or grab the appropriate package for your distribution at
 ftp.redhat.com or rpmfind.net.

Using a program other than sendmail to relay mail

 Sendmail is commonly configured as the default way mail is
 sent on a Linux installation. Freedom will correctly handle
 mail sent by sendmail, as well as mail sent via a remote
 SMTP server. However, if you have replaced sendmail with an
 alternate program (such as qmail), there are certain
 conditions in which outgoing mail can bypass Freedom.

 If you are unsure if you are using sendmail or another
 program to relay messages, we recommend configuring your
 mail program with a remote SMTP server. For more information,
 please see the Knowledge Center at www.freedom.net.

Freedom and Fetchmail

 To use fetchmail with Freedom, you must configure it to
 deliver into your local mail folder, and not use the POP
 "Top" command. You can do so by adding the following lines
 to your .fetchmailrc file:

 ## Retrieve Freedom Nym mail, and deliver it locally via procmail
 poll mail.freedom.net with proto pop3
 user [MyUserName] is freedom with password freedom
 fetchall
 mda "/usr/bin/procmail -d [MyUserName]"
 ###

 (Replace MyUserName with your own.)
 
Using Freedom with a corporate or 3rd party firewall

 The Freedom client communicates with the Freedom network over
 several non-standard ports. You must configure your firewall
 to allow communication on these ports to use Freedom.
 
 TCP and UDP ports that must be open:
  51100 (TCP and UDP)
  51101 (UDP)
  51102 (TCP)
  51107 (TCP)
  51109 (UDP)
  51140 (TCP)

"Can't connect to token server"
 
 This is symptomatic of a number of possible issues. One problem
 is the way some ISPs have configured their routers. If you
 receive "Can't Connect to Token Server", contact technical
 support.
 
Client-side cookies

 Some web sites use a type of cookie called a client-side cookie. 
 A client-side cookie is set using JavaScript to generate the cookie
 directly on your computer, effectively bypassing Freedom's Cookie
 Manager. This type of cookie can not be intercepted by Freedom, but
 the return of client-side cookies will be blocked when a nym is
 selected. Web applications that use client-side cookies will not
 work with a nym selected.
  
SSL
 
 Secure web connections (SSL) are already encrypted and cannot
 be read by Freedom. Freedom will not be able to intercept cookies
 sent during an SSL connection. When a nym is selected, this may cause
 problems with sites that use SSL and cookies for log-in authentication
 or for transactions.
  
Using Freedom with an ISP that uses a proxy server
 
 Some ISPs require their users connect through a proxy. When running
 Freedom with a nym selected, if your browser is configured to use a
 proxy, your connections will still pass through the proxy after having
 been routed through the anonymous Freedom Network. If you don't want
 your last hop to be your ISP's proxy, switch the proxy configuration
 in your browser to make a direct connection to the Internet.
 
 When you run Freedom without a nym selected, you will need to
 reconfigure your browser to use your ISP's proxy. 

Pinging with Freedom running

 Please note that pings are not sent through the Freedom Network.
 
  ----- 4.0 Getting help & giving feedback -----
  
 Further information can be found at:
 
  The Freedom web site: http://www.freedom.net/support/
  The Freedom Knowledge Center: http://www.freedom.net/support/knowledge.html
  
 Contact Technical Support at: support@freedom.net 
  
  Please include the following information when contacting
  Technical Support:
 
  - What operating system and what Internet connection type you are using 
  - The exact error message you encountered (if any) and any associated
    error message numbers. 
  - Exactly what you were doing at the time of the problem. 
  - What other software was running when you encountered your problem.
  - Include Freedom Diagnostic results as an attachement in your email
 
 -------------------------------------------------------------------------
 
Copyright (c) 2001
                    ^
                    ^ Zero-Knowledge Systems Inc.
                    ^ All Rights Reserved
 
