5. Bookmarks

Just like creating bookmarks for web pages in a browser, you can create bookmarks for ftp sites in Yafc. These can later be used for autologin to that site.

When connected to an ftp site, use the bookmark command (3.1.4 bookmark) to create a bookmark for that site. If you logged in with a username and password, Yafc will ask if you want to save the password in the bookmarks file. If you do, be sure it isn't world readable. By using the auto_bookmark keyword in the configuration file, Yafc can create bookmarks automatically for new sites.

The bookmarks are available to the open command, with tab completion.

The autologin information is stored in much the same way as in the `~/.netrc' file used by standard ftp(1), except that the macdef option is not supported.

An entry must begin with a machine, default or local keyword.

5.0.1 Bookmark keywords		keywords for bookmarks
5.0.2 Bookmark examples		examples

5.0.1 Bookmark keywords

`machine'

Specify the hostname to connect to or a domainname. The hostname can be a valid FTP URL, including username, password, etc. In that case there is no need to specify the corresponding keywords. Using the URL syntax is the only way to specify a non-standard port.

Domainnames should begin with a period, as in .kth.se. This will match any hostname on that domain, except for hostnames explicitly mentioned with another `machine' keyword. You can not specify an alias name for a domain entry.

`alias'

Specifies another (verbose) name for the bookmark, like `ruby' instead of `ftp.netlab.co.jp'. This is the name that will be shown in the tab completion list. Valid only after a `machine' statement.

`local'

If an entry begins with `local', it specifies how to login to all ocal machines. Local machines are unqualified hostnames (ie, hostnames without a period.)

This can be overridden with an entry for a specific machine.

`default'

The `default' entry is used when no other `machine' or `local' keyword matched. It can be used to login anonymously to all unknown sites.

`login'

Specify the username.

`anonymous'

Try an anonymous login, uses anon_password.

`password'

Specify the password, if required.

`account'

Specify account name. Not fully supported, anyone using it?

`cwd'

This keyword specifies a startup directory on the remote server. Yafc changes the current directory when logged in.

`prot'

The prot keyword sets the Kerberos data protection level. Valid protection levels are safe, clear and private.

This is a no-op if not compiled with Kerberos.

`mech'

List the preferred security mechanisms to use. This is the same as default_mechanism, except it is only used for this machine.

`passive'

Boolean option requiring an argument (true/false). If true, use passive mode in data transfers, regardless of the value of use_passive_mode in the configuration file.

5.0.2 Bookmark examples

default login anonymous

As default, login as 'anonymous' and prompt for password

default anonymous

As default, login as 'anonymous' and automatically supply your email address as password.

local login mhe

Login as 'mhe' on all machines on the local network (machines w/o a '.')

machine .foo.bar.se login niels

Login as 'niels' on all hosts on .foo.bar.se domain

machine dent.foo.bar.se login slartibartfast cwd ~/fjord

Login as 'slartibartfast' on dent.foo.bar.se and start in directory ~/fjord

machine slartibartfast@dent.foo.bar.se/fjord

Identical to the example above, but using an ftp URL instead

machine ftp.gurka.com:4711 anonymous

Login as 'anonymous' and automagically supply password from anon_password, connect on non-standard port 4711

machine mayer.physto.se anonymous cwd /pub/yafc alias yafc

Login anonymously to machine mayer.physto.se with other name yafc

machine shell.stacken.kth.se login mhe mech krb4 passive yes alias stacken

Login as mhe using Kerberos 4 authentication, and use passive mode for transfers (overrides the use_passive_mode keyword in the config file)