| A new NTP chapter is available for use. You can find it in
LASSIE::UCX$DOC:MGMT_NTP.PS
The new NTP chapter will be part of the revised management guide
(availabilty to be announced at a later date.)
If you find problems, errors, or have any feedback on the chapter,
pls send mail to LASSIE::GILCHREST.
Thx,
--Jeanne
|
|
-< Revised Management Guide Ready for Review >-
The first draft of the revised management guide is ready for technical
review.
Several chapters have been heavily revised to include new V4.2
material, correct errors, and improve readability and usability.
Much work on the book remains, however, and all review comments are
welcome.
You can copy the file from
LASSIE::V42_MANAGE_DRAFT1.PS
Please send all comments to LASSIE::GILCHREST.
|
| RE: Note 5349.2 by TNPUBS::PETERS
> Please send all comments to LASSIE::GILCHREST.
Hello,
Because I'm not sure that my mails were delivered, here is a copy of them.
Best regards,
Pierre-Etienne
From: SOS6::DIETZ 23-MAY-1997 10:34:56.62
To: [email protected]
Subj: V42_MANAGE_DRAFT1.PS, replying to note 5349.2
REF: 5349.2 Documentation Announcements by TNPUBS::PETERS
-< Revised Management Book Ready for Review >-
V42_MANAGE_DRAFT1.PS 3014/3015 24-APR-1997
Hello Jeanne,
I am happy to notice a collision of your proposal to review the
management book, and of the need of a customer that asks whether
some features are (un)documented or removed.
Here are a first set of remarks.
I will try to read some more chapters of this book.
Thanks and best regards,
Pierre-Etienne
1) UCX$FTPD_SECURITY logical name:
---------------------------------
In the V4.2 UCX Mgt Guide, this logical name is forgotten,
see paragraph 12.2.3 Managing FTP with Logical Names.
It has been specified in [UCX-VMS V3.3/RN] Release Notes,
Paragraph 6.1.2, Omitted Documentation: FTP Logical Names
o UCX$FTPD_SECURITY
If you define UCX$FTPD_SECURITY systemwide, FTP prompts
for a password, even if there is not a user name to
match the one specified by the FTP user.
2) UCX$FTP_ANONYMOUS_DIRECTORY logical name:
-------------------------------------------
... no usage example is provided ...
see paragraph 12.2.3 Managing FTP with Logical Names.
The following syntax possibilities were developped by
Len D'Alberti on UCX V3.3 ECO ~6, and I have re-checked
them ("sanity check") today with V4.1 PAT8:
(suggested) Usage example:
$define /sys /nolog UCX$FTP_ANONYMOUS_DIRECTORY -
utl$common:[ucxftp.pub], -
utl$common:[ucxftp.pub.*], -
utl$common:[ucxftp.pub...]
that will allow an access:
to the default Anonymous account directory
to utl$common:[ucxftp.pub]*.*;*,
to utl$common:[ucxftp.pub.*]*.*;*,
and to utl$common:[ucxftp.pub...]*.*;*.
3) UCX$UUENCODE / UCX$UUDECODE:
-------------------------------
... Absent from V4.0, V4.1, V4.2 ...
Yet, some documentation was available into
- UCX V2.0E Release Notes Paragraph 8
- UCX V3.1 Config & Install Annex B
In example: V2.0E contained,
! DEC_TCP/IP_Services_for_OpenVMS_____________________
! Release Notes January 1994
! These Release Notes apply to Versions 2.0, 2.0B,
! 2.0D, and 2.0E.
! [...]
! 8 Version 2.0: Functional Enhancements
! 8.2 Services
! o Conversion between 7-bit and 8-bit file representations
! is now available.
! The UNIX utilities, uuencode and uudecode, are
! implemented to support SMTP which uses 7-bit characters
! only. These utilities perform bit conversion as
! follows:
! o uuencode - 8-bit to 7-bit representation
! o uudecode - 7-bit to 8-bit representation
! To encode files, issue:
! $ @SYS$SYSTEM:UCX$ENCODE "uuencode" in_file out_file
! where in_file is the 8-bit file to be encoded and out_file
! is the resulting 7-bit file.
! To decode files, issue:
! $ @SYS$SYSTEM:UCX$DECODE "uudecode" in_file [out_file]
! where in_file is the 7-bit file to be decoded. The
! resulting decoded file name is implicit in the encoded
! file, but if the file name is an illegal OpenVMS file
! name, you can specify an output file name.
I would suggest something like (I just adapted the old text to
the new file name and file location):
UUENCODE AND UUDECODE TOOLS:
o Conversion between 7-bit and 8-bit file representation
The UNIX utilities, uuencode and uudecode, are
implemented to support SMTP which uses 7-bit characters
only. These utilities perform bit conversion as
follows:
o uuencode - 8-bit to 7-bit representation
o uudecode - 7-bit to 8-bit representation
To encode files, issue:
$ UUENCODE :== $SYS$SYSTEM:UCX$UUENCODE
$ UUENCODE in_file out_file
where in_file is the 8-bit file to be encoded and out_file
is the resulting 7-bit file.
To decode files, issue:
$ UUDECODE :== $SYS$SYSTEM:UCX$UUDECODE
$ UUDECODE in_file [out_file]
where in_file is the 7-bit file to be decoded. The
resulting decoded file name is implicit in the encoded
file, but if the file name is an illegal OpenVMS file
name, you can specify an output file name.
NB: In case the out_file is specified, use as syntax
for the output file name,
either "device:[directory]file.extension"
or "file.extension",
but not just "device:[directory]" which would produce
a wrong result.
|
| RE: Note 5349.2 by TNPUBS::PETERS ...continued...
> Please send all comments to LASSIE::GILCHREST.
Hello, this is a 2nd comment:
From: PRSSOS::DIETZ 26-MAY-1997 15:07:31.89
To: [email protected]
Subj: V42_MANAGE_DRAFT1.PS Anonymous FTP suggestion
Hello Jeanne,
A need for a FTP precision that has been noticed by a customer:
His CLAIM was:
" Anonymous FTP File Access: one can only transfer (get/put)
files whose owner is ANONYMOUS. Is that documented? "
An ANSWER has been provided below, pointed by ">" marks.
I have tried to translate here my answer to the customer. Feel
free to change/adapt/modify it as necessary.
The SUGGESTION for a Documentation Modification. See below.
Thanks Jeanne, to tell me whether this mail is reaching you, because
the VMSmail address LASSIE::GILCHREST stays "unreachable"
now for one week. (I already sent you a mail on the 23-MAY-1997,
about a similar subject).
Best regards,
Pierre-Etienne Dietz (UCX-Support team, France)
............................................................................
Chapter 12 File Transfer Protocol (FTP) [page 12-12]
12.2 Configuring Anonymous FTP
[...]
On the local FTP Server, local users can access files without
password authentification. Remote users do not require an account.
>
File access is controlled by regular OpenVMS access restrictions:
> By default, UCX$CONFIG (Menus: Optional Components, Set up Anonymous FTP
> Account and Directories) will create an ANONYMOUS account on the
> root directory SYS$SYSDEVICE:[ANONYMOUS]. Usual OpenVMS file
> protection will provide to inbound Anonymous FTP sessions,
> an access limited to,
> o this [ANONYMOUS] directory,
> o any of its [ANONYMOUS...] subdirectories,
> o the contained files whose UIC is [ANONYMOU,ANONYMOUS].
>
> In example, a remote anonymous FTP client can
> o View these directories
> o Copy files to and from these directories
> and his access is limited to directories and files that are owned
> by the [ANONYMOU,ANONYMOUS] account.
>
How you can set up Anonymous FTP determines the availibility
of end-user features. Your configuration can offer or limit the
following features:
> (The following logical names GUEST$PUBLIC and ANONYMOUS$USER
> are just examples of directories that could be setup in order
> to provide an Anonymous FTP Service)
o View directories
o View the guest and public directories
If you set up a public directory, users can look at
bulletin-board information and files of interest. the public area is
read-only. Its name is GUEST$PUBLIC.
[...]
|