eftp4linux EUROFILE implementation initial check in.

Not yet fully integrated in isdn4k-utils build procedure (menu config) yet.
This commit is contained in:
he 1999-06-29 16:22:34 +00:00
parent cc7f6d1b86
commit 0a692c0143
15 changed files with 3349 additions and 0 deletions

2
NEWS
View File

@ -1,6 +1,8 @@
Recent changes made to the isdn4k-utils archive are listed here,
most recent on top.
------------------
1999-06-29 he (Henner Eisen <eis@baty.hanse.de)
eurofile - eftp4linux EUROFILE implementation initially checked in
1999/06/07 paul (Paul Slootman <paul@isdn4linux.de>)
This file started!

View File

@ -1,3 +1,4 @@
CVS
vbox3
distexclude
eurofile

164
eurofile/CHANGES Normal file
View File

@ -0,0 +1,164 @@
/* $Id: CHANGES,v 1.1 1999/06/29 16:22:34 he Exp $
# Change log for eftp4Linux
#
# [new] means 'new feature added'
# [fix] means 'bug fixed'
# [chg] means 'changed' (algorithm, data types or somewhat)
# [imp] means 'improved' (more robust/efficient/comfortable code)
#
# in chronological order from bottom to top
#
#
#
# Changelog starts with 0.0.5, based on patches submitted by Matthias
# Stolte ms@msdatec.de.
#
# (The inital Changlogs have been compressed. Hopefully, I did not
# miss any important info -- HE).
#
$Log: CHANGES,v $
Revision 1.1 1999/06/29 16:22:34 he
eftp4linux EUROFILE implementation initial check in.
Not yet fully integrated in isdn4k-utils build procedure (menu config) yet.
--------------
Version 0.0.11
--------------
- [new] doc/design.txt added (needs completion)
- [chg] src/* changed directory names and structure which also affects
#include directives and Makefiles.
- [chg] Support CVS in built procedure.
--------------
Version 0.0.10
--------------
- [fix] tdu_buf.c::tdu_parse_li(): fixed base (255 -> 256)
- [imp] eft_server.c, eft_dir.c, eftd.c, eft.c: modified (also format
changes!!) and added more LogBook messages.
- [fix] tdu_log.c::tdu_mk_printable: proper handling for len<0
(cures previous segmentation faults).
- [imp] eftd.sh.in: automatically remove '-m' option when EFTD_DEBUG=1
(for debugging under gdb) is set.
-------------
Version 0.0.9
-------------
- [imp] eftd.c, eftp.c, tdu_log.c: support for udata and address
logging.
- [fix] eftd.sh EFTD_OPTIONS set from from eft.msn could be lost.
Clarified some comments.
- [imp] eftd.c Proposed some locations for end of session LogBook messages.
-------------
Version 0.0.8
-------------
- [fix] Updated README, ETSI standards now available free of charge.
- [new] 18.02.1999, ms@msdatec.de
eftd.8.sgml created.
- [chg] 17.02.1999, ms@msdatec.de
src/lib/eftc, set_default_adress: Now using combination of
gethostname() and gethostbyname() because getdomainname()
didn't work as expected.
- [imp] eftd.sh: (based on patch provided by Matthias Stolte)
Better custumization by means of more variables.
- [imp] eftd.sh: (based on suggestion from Knuth Posern)
Support for several different MSNs on different
interfaces. This allows the server to accept connections
from different S0 interfaces which cannot use a common MSN.
- [imp] tdu_log.c and several other files: Changes in logging
infrastructure (in particular for a supporting an eft log
file facilty). (loggin to log file with several processes
in parallel has not been tested yet and might cuase problems).
- [chg] eftd.c, doc/eftd: The log changes imply changes for eftd's
command line interface. New option -b for selecting log[book]
file. Removed -v. New semantics for -l -d and -L.
This might break old script files.
- [chg] eft_names.c, eft_server.c, eft_dir.c: some modification in
filename-transfername-mapping.
-------------
Version 0.0.7
-------------
Integrated Michael Mauch's improved readline and mget/mput support:
- [imp] eftp.c new readline support, using the alternate interface.
- [chg] eftp.c non-terminal input now read by fgets or getdelim
instead of read
- [chg] read_line.c removed
- [chg] src/Makefile and configure.in adapted for readline support.
- [new] eftp.c mget/mput added.
Fixes for glibc2 compatibility (thanks to Michael Dietrich)
- [fix] eftp.c, eftd.c: sigset now initialized by utility functions.
- [fix] eft_names.c: errno.h included.
- [fix] eft_tmpfile.c zeroed struct stat instances before symlink
attack paranoia check.
Misc
- [chg] moved eft_map_to_user() handling to eft_server.c and change to
default user only if user is not in passwd database. This also
fixes a bug (username wrong in logfile output).
- [fix] eft_dir.c::eft_valid_dent_s_k() now only selects symlinks that
refer to regular files.
- [fix] eft_names.c::eft_file_is_hidden() added missing resetting of errno
- [fix] eft_server.c::eft_log_xfer() use eft->user_name for username field
- [imp] eft_dir.c: (several locations) modified generation of
filestore references. Now, no longer should any client have an
excuse to break on this.
- [imp] eftd.c can now listen simultaneously on different X.25
adresses
-------------
Version 0.0.6
-------------
The first 3 changes were contributed by Michael Mauch <michael.mauch@gmx.de>
- [new] eftp.c started implementing readline support.
- [new] eftp.c some new local commands, in particular `lcd' and `!` shell
escape
- [fix] calc date (month was one to large) in fileheader.c::fh2timet()
- [fix] removed erroneous return in lib/eft_client.c::eft_getcwd()
- [chg] Istructions in README updated for newer kernels and
isdn4k-utils 3.0beta2.
- [new] eftd.c, eftd.sh: Added support for serving multiple connections
simultaneously [-m option].
- [new] eftd.c, eft_i4l.c: network interface names are now determined
automatically by analysing /proc filesystem entries.
- [chg] added RCS/CVS $Id macros to almost all files
(preparation for later inclusion in i4l CVS tree)
- [imp] eft_dir.c: now generating globally unique filestore reference
strings (for SLIST primitive) which conform better with
ETS 300 383 annex C (that annex is informative only).
- [chg] added RCS/CVS $Id macros to almost all files
(preparation for later inclusion in i4l CVS tree)
- [fix] tdu.h,slave.c: return type of tdu_typed_data_received()
- [fix] eftd.c: parantheses in have_opt() for clarifying if-else
- [fix] #define'd HAVE_GETCWD (hack) in authlib/divfunc.c
- [chg] include public header files eft.h and tdu_user.h with
bracket <> notation, change make rules accordingly and
remove *.h symlinks
- [imp] new database lookup and mangeling based transfer name mapping
improved. Now activated by default.
-------------
Version 0.0.5
-------------
1998-11-30
integrated changes provided by ms@msdatec.de
- [new] eft.c: initial address now <host>.<domain>, if possible
- [new] eftd.c, option '-h/-?'
- [new] eftd.c, eft_check_user(), main(), show_help()
user mapping (option -n)
if authentification fails and "eft_map_to_user" is not null,
"eft_map_to_user" is tried for authentification (a password isn't
supported yet)
- [imp] eft_dir, eft_store_slist()
hardcoded ".++eft_flat" replaced by eft_flat_dir_name
- [imp] eftd.c, eft_setup_user():
hardcoded ".++eft_flat" replaced by eft_flat_dir_name
- [new] src/eftd.c: haveopt() created
- [new] src/eftd.c: main()
version output on command line request 'V'
- [new] eftd.c, show_help() created
- [imp] eftd.sh

34
eurofile/COPYING Normal file
View File

@ -0,0 +1,34 @@
Source code in directories src and src/lib is subject to the
`GNU LIBRARY GENERAL PUBLIC LICENSE' [ LGPL ], refer to COPYING.LIB.
It is copyrighted by Henner Eisen.
Although some files will not build as a library but as unix
executables, they are licensed under the LGPL nevertheless.
This permits you to use them under the terms of the GPL as well as
modifying them such that they become part of a library which can be
licensed under the terms of the LGPL.
Source code in directory src/authlib is subject to different licenses
(a BSD style license with advertisment clause). Refer to COPYING.auth
for further details.
Note that with the default configuration, eftd needs src/authlib to
work. With former versions of eftp4linux, some license restrictions
of authlib conflicted with the LGPL.
As of eftp4linux-0.0.3, the authorization routines are attached to the
EUROFILE state machine code at run time by means of function calls and
parameters. Thus, a server using the eftp4linux library and
attaching authlib is a work that uses the library (the LGPL'ed
code) in the sense of the LGPL. Thus, there is no problem with
distributing eftd binaries any more (and the specially granted
permissions necessary in eftp4linux-0.0.2 are obsolete now).
Note that the eftp client program is linked with the GNU readline
library which is licensend under the GPL. Thus, the eftp binary
automatically is subject to the GPL, even though the sources of eftp
itsself are licensed under the LGPL (which explicitly permits to
to also licence the code under ther GPL).
Henner

481
eurofile/COPYING.LIB Normal file
View File

@ -0,0 +1,481 @@
GNU LIBRARY GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1991 Free Software Foundation, Inc.
675 Mass Ave, Cambridge, MA 02139, USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the library GPL. It is
numbered 2 because it goes with version 2 of the ordinary GPL.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Library General Public License, applies to some
specially designated Free Software Foundation software, and to any
other libraries whose authors decide to use it. You can use it for
your libraries, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it
in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid
anyone to deny you these rights or to ask you to surrender the rights.
These restrictions translate to certain responsibilities for you if
you distribute copies of the library, or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link a program with the library, you must provide
complete object files to the recipients so that they can relink them
with the library, after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
Our method of protecting your rights has two steps: (1) copyright
the library, and (2) offer you this license which gives you legal
permission to copy, distribute and/or modify the library.
Also, for each distributor's protection, we want to make certain
that everyone understands that there is no warranty for this free
library. If the library is modified by someone else and passed on, we
want its recipients to know that what they have is not the original
version, so that any problems introduced by others will not reflect on
the original authors' reputations.
Finally, any free program is threatened constantly by software
patents. We wish to avoid the danger that companies distributing free
software will individually obtain patent licenses, thus in effect
transforming the program into proprietary software. To prevent this,
we have made it clear that any patent must be licensed for everyone's
free use or not licensed at all.
Most GNU software, including some libraries, is covered by the ordinary
GNU General Public License, which was designed for utility programs. This
license, the GNU Library General Public License, applies to certain
designated libraries. This license is quite different from the ordinary
one; be sure to read it in full, and don't assume that anything in it is
the same as in the ordinary license.
The reason we have a separate public license for some libraries is that
they blur the distinction we usually make between modifying or adding to a
program and simply using it. Linking a program with a library, without
changing the library, is in some sense simply using the library, and is
analogous to running a utility program or application program. However, in
a textual and legal sense, the linked executable is a combined work, a
derivative of the original library, and the ordinary General Public License
treats it as such.
Because of this blurred distinction, using the ordinary General
Public License for libraries did not effectively promote software
sharing, because most developers did not use the libraries. We
concluded that weaker conditions might promote sharing better.
However, unrestricted linking of non-free programs would deprive the
users of those programs of all benefit from the free status of the
libraries themselves. This Library General Public License is intended to
permit developers of non-free programs to use free libraries, while
preserving your freedom as a user of such programs to change the free
libraries that are incorporated in them. (We have not seen how to achieve
this as regards changes in header files, but we have achieved it as regards
changes in the actual functions of the Library.) The hope is that this
will lead to faster development of free libraries.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, while the latter only
works together with the library.
Note that it is possible for a library to be covered by the ordinary
General Public License rather than by this special one.
GNU LIBRARY GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library which
contains a notice placed by the copyright holder or other authorized
party saying it may be distributed under the terms of this Library
General Public License (also called "this License"). Each licensee is
addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also compile or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
c) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
d) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the source code distributed need not include anything that is normally
distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties to
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Library General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
Appendix: How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Library General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Library General Public License for more details.
You should have received a copy of the GNU Library General Public
License along with this library; if not, write to the Free
Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

111
eurofile/COPYING.authlib Normal file
View File

@ -0,0 +1,111 @@
src/authlib contains an authentication library derived from wu-ftpd.
It has been adapted for use with eftd by Georg v.Zezschwitz
Source code in src/authlib carries copyright notices and license
conditions of different people and organizations. This file is only
a summary therof and does neither claim to be complete nor correct.
Refer to the source files for the authoritative copyright
and license statements.
/* Copyright (c) 1989 The Regents of the University of California. All rights
* reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions are
* met: 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer. 2.
* Redistributions in binary form must reproduce the above copyright notice,
* this list of conditions and the following disclaimer in the documentation
* and/or other materials provided with the distribution. 3. All advertising
* materials mentioning features or use of this software must display the
* following acknowledgement: This product includes software developed by the
* University of California, Berkeley and its contributors. 4. Neither the
* name of the University nor the names of its contributors may be used to
* endorse or promote products derived from this software without specific
* prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY
* EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
* DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR
* ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
* SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
* CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*/
/*-
* Copyright (c) 1990 The Regents of the University of California.
* All rights reserved.
*
* This code is derived from software contributed to Berkeley by
* Chris Torek.
*
* Redistribution and use in source and binary forms are permitted
* provided that: (1) source distributions retain this entire copyright
* notice and comment, and (2) distributions including binaries display
* the following acknowledgement: ``This product includes software
* developed by the University of California, Berkeley and its contributors''
* in the documentation or other materials provided with the distribution
* and in all advertising materials mentioning features or use of this
* software. Neither the name of the University nor the names of its
* contributors may be used to endorse or promote products derived
* from this software without specific prior written permission.
* THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
* IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
* WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
*/
/* Copyright (c) 1993, 1994 Washington University in Saint Louis
* All rights reserved.
*
* Redistribution and use in source and binary forms, with or without
* modification, are permitted provided that the following conditions are
* met: 1. Redistributions of source code must retain the above copyright
* notice, this list of conditions and the following disclaimer. 2.
* Redistributions in binary form must reproduce the above copyright notice,
* this list of conditions and the following disclaimer in the documentation
* and/or other materials provided with the distribution. 3. All advertising
* materials mentioning features or use of this software must display the
* following acknowledgement: This product includes software developed by the
* Washington University in Saint Louis and its contributors. 4. Neither the
* name of the University nor the names of its contributors may be used to
* endorse or promote products derived from this software without specific
* prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY WASHINGTON UNIVERSITY AND CONTRIBUTORS
* ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
* LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
* A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL WASHINGTON
* UNIVERSITY OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
* INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
* BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
* LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
* CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
* ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
* POSSIBILITY OF SUCH DAMAGE.
*/
/* This software is Copyright 1997 by Stan Barber.
*
* Permission is hereby granted to copy, reproduce, redistribute or otherwise
* use this software as long as: there is no monetary profit gained
* specifically from the use or reproduction of this software, it is not
* sold, rented, traded or otherwise marketed, and this copyright notice is
* included prominently in any copy made.
*
* The author make no claims as to the fitness or correctness of this software
* for any use whatsoever, and it is provided as is. Any use of this software
* is at the user's own risk.
*/

204
eurofile/INSTALL Normal file
View File

@ -0,0 +1,204 @@
Installation instructions for eftp4linux
First, you need to compile 2.2.x kernel with x25 support enabled.
You also need a recent version of the isdn4k-utils compiled against
2.2.x kernel header files and the x25 utility programmes.
Kernel
======
You need a recent kernel 2.2.x kernel that supports some special
features. 2.0.x kernels won't work. When configuring the kernel for
compilation, (i.e. by `make menuconfig') enable the following:
Code maturity level options --->
Enable "Prompt for development and/or incomplete
code/drivers" (CONFIG_EXPERIMENTAL) [select "y"]
Networking options --->
Enable "CCITT X.25 Packet Layer" [select "m" or "y"]
(if this menu entry is missing, you probably havn't
enabled the experimental features above).
ISDN subsystem --->
configure this as usual and additionally enable
"X.25 PLP on top of ISDN" [select "y"]
(if this menu entry is missing, you probably havn't
enabled the X25 PLP support from the networking options).
Set all other options as usual and then compile your kernel, i.e.
make dep
make zImage modules
make modules_install
"make modules_install" is recommended after compilation.
You can additionally do a `make install', but be aware that this might
possibly overwrite your old 2.0.36+ kernel. Without `make install' you will
need to add an additional entry to your /etc/lilo.conf file for
booting your 2.2.x kernel as an alternative to 2.0.x.
It is possible (but not necessary) to apply additional
patches to the kernel before compilation:
ix25-2.1.128.patch fixes a bug in the Linus X.25 PLP layer. This is
only necessary to communicate with certain
buggy eft clients (CSD isdn toolbox,
maybe also some RVS clients). If you want to
communicate with buggy clients, also
enable the "#define X25_PEER_IS_BUGGY"
at the very end of include/net/x25.h
before compiling the kernel.
isdn4linux CVS snapshot has been reported to work more reliably with
2.2.x-kernels. It also provides for a
feature useful for eftd to reliably determine
the peer's isdn No.
Kernels 2.3.4 and newer now contain the new
isdn4linux-code. You can try this (but be
aware that 2.3.x are the non-stable kernels).
isdn4k-utils
============
You need a recent isdnctrl utility (and maybe the loopctrl binary if
you want to test locally with the isdnloop driver).
You need isdn4k-utils-3.0beta2.tar.gz or newer.
The utilities must be compiled against the (patched) 2.2.x
kernel headers. The location of that kernel can be set from the
isdn4k-utils configuration menu.
The 3.0beta2 package is availabe from ftp.franken.de
x25-utils
=========
If you want to use the eftp programme (Eurofile client), you need the
x25_route utility from the x25_utils package. The eurofile server
can also be used without that package.
The package should be available from the same site as this eftp4linux
packages or from ftp.hes.iki.fi:/pub/ham/linux/ax25/ (don't confuse
the x25-utils with the ax25-utils, you only need the x25-utils).
Make sure that the compiler/preprocessor finds the include/linux/x25.h
file. Either add some flags to the makefile or make /usr/src/linux a
symbolic link pointing to your pre2.2 kernel's include/linux directory.
This eftp4linux package
=======================
Just untar the package and type 'make' in the top level makefile.
This should automatically run a configure script. If your new isdnctrl
is installed at an unsusual location, you might want to edit the
./configure script before. The locations searched for are
/usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin.
If you have multiple isdnctrl versions installed, make sure that the
utility found first is the one just compiled as above (against the
(patched) 2.2pre kernel header files).
The directory where the isdn configuration files are located is
assumed to be /etc/isdn. If this is not true for your installation,
either create that directory or set the environment variable
I4LCONFDIR to an alternative directory.
As I could not test with all compiler/libc/distribution combinations,
maybe I missed something. If configuration should fail or some files
are not found during compilation, please tell me.
As of eftp4linux-0.0.7, command line editing in eftp by means of
the GNU readline library is enabled on default. For command
line editing in eftp to work, you need a sufficiently recent
GNU readline library that supports the "alternative interface".
You also need the ncurses library. If the approriate libraries are
not found, readline support will be automatically disabled.
After successful compilation, you should be able to start
the eurofile client or server.
If you need to fix something that might influence the configuration
process, do a 'make distclean' before recompiling.
Starting the the Eurofile applications
======================================
General preparation
===================
If you have omitted the "make modules_install" after your kernel
compilation, the default eft scripts (and probably the init scripts
of your linux distribution as well) won't be able to load the modules
corresponding to your (patched) kernel version. In that case, either
modify all scripts to load the proper modules by absolute pathname
or set the enviromnemnt variable MODPATH to the "modules" directory
of your developer kernel's source tree.
Boot your linux 2.2.x kernel. The isdn subsystem should be
set up to a state where a HL driver capable of l2_prot x75i is
working. If your boot sequence ends up in a state where you can set up
connections on the /dev/ttyI devices, then you are already done with this.
After that, you need to insmod the x25 module with
insmod x25
or
modprobe x25
Copy the file eft.msn present in the sample directory to the
I4LCONFDIR (probably /etc/isdn) and edit it in order to configure
the MSNs to be used by the EUROFILE client and server.
Starting the Eurofile server
============================
Start the daemon as root by the script eftd.sh as present in the
"scripts"-directory by typing
eftd.sh start
After that, you should be able to connect with an eft client to your
linux server via isdn. If your client can only access upper or only
lower case file names (or has other interworking problems), try
prepending a '+' to the user name when logging in.
You can stop EUROFILE service again by
eftd.sh stop
Starting the Eurofile client
============================
To start the client, there is also a script "eftp.sh" (this currently
also needs to be started from the root user, but the script
does a 'cd /tmp' and changes the uid before the client is executed)
eftp.sh ISDN_NUMBER [USER/PASSWD]
in order to start an EUROFILE client and connect to a remote eft server.
(root privileges are currently needed for setting up the network
interfaces -- this will be worked around in a future release).
Note that typing the password on the command line is not safe if
your system is shared with other users who might spoof your password
with the ps command. It also leaves traces in your command history file.
You can also connect to your own server on top of the isdnloop driver
(no paying isdn connection involved) by
eftp.sh localhost [USER/PASSWD]

75
eurofile/Makefile Normal file
View File

@ -0,0 +1,75 @@
# $Id: Makefile,v 1.1 1999/06/29 16:22:37 he Exp $
SHELL = /bin/sh
CVS = cvs
SCRIPTS = scripts/eftd.sh scripts/eftp.sh scripts/eftp_setup
#
#additions to the CHANGES file shall automatically increase the compiled-in
#version string
#
E4L_EXTRA_VERSION_DEP := $(shell pwd)/CHANGES
export E4L_EXTRA_VERSION_DEP
all: ./configure scripts/eftd.sh scripts/eftp.sh scripts/eftp_setup src/config.h Rules.make
make -C src all
config src/config.h Rules.make $(SCRIPTS): configure
./configure
chmod a+x scripts/eftd.sh scripts/eftp.sh scripts/eftp_setup
configure: configure.in
autoconf
permissions: scripts/eftd.sh scripts/eftp.sh scripts/eftp_setup
chown root scripts/eftp_setup
chmod u+s scripts/eftp_setup
chmod a+x $(SCRIPTS)
clean:
rm -f xx[0-9][0-9] CHANGES.tmp
make -C src clean
distclean: clean
rm -f config.* *~ '#'*'#' $(SCRIPTS)
make -C src distclean
rm -f Rules.make eftp4linux*.tar.gz
rm -f `find . \( -name core -o -name '*.orig' -o -name '*.rej' -o \
-name '*~' -o -name '*.bak' -o -name '#*#' -o -name '.*.orig'\
-o -name '.*.rej' -o -name '.SUMS' -o -size 0 \) -print` TAGS
configureclean: distclean
rm -f configure
commit: distclean
$(CVS) commit .
update:
$(CVS) update -dP .
new_version:
echo "Please create the file new_version and fill in the new version number!"
exit 1
# Make a new release. The variable NEW_VERSION must be set in the
# make command's arguments or environment.
# : update
release: distclean
# $(CVS) commit .
@if [ -z "$(NEW_VERSION)" ]; then echo "You must define the variable NEW_VERSION when making a new version!"; exit 1; fi
make -C src new_version
rm -f xx[0-9][0-9]
csplit CHANGES '/$$Log:/+1'
mv -f xx00 CHANGES.tmp
echo '===============' >> CHANGES.tmp
cat xx[0-9][0-9] >> CHANGES.tmp
rm -f xx[0-9][0-9]
# $(CVS) commit -m "Version $(NEW_VERSION)" .
# $(CVS) tag `echo Version_$(NEW_VERSION)|sed s/\\./_/g` .
# tar -czf ../eftp4linux-$(NEW_VERSION).tar.gz .
.PHONY: all config permissions clean distclean release configureclean commit update

322
eurofile/README Normal file
View File

@ -0,0 +1,322 @@
$Id: README,v 1.1 1999/06/29 16:22:37 he Exp $
README file for eftp4linux-0.0.10
=================================
eftp4linux is an Open Source (tm) implementation of the
EUROFILE Transfer Protocol as standardised by a set of ETSI norms
(in particular ETS 300-383 and ETS 300-075). It is freqently used
to transfer files over ISDN.
Currently, the only target OS is Linux > 2.2.x. However, the design
should allow for porting it to other POSIX operating systems
that provide a select() system call and a socket interface to
the X.25/ISO-8208 network layer protocol.
DISCLAIMER
==========
Use on your own risk -- as usual with open (and even close) source software.
However, as this is alpha test software, the risk might be higher
than the risk of just using your favourite linux distribution.
Read the COPYING* files present in the distribution for further details.
WHAT'S NEW
==========
Main changes with respect to 0.0.8:
- better script (MSN sharing) support for serving multiple connections
- improved event logging
- some bug fixes
See the CHANGES file for details.
General features
================
eftp4linux consists of a core library that implements the EUROFILE
related protocols. It also contains two important applications built
on top of this library:
- An EUROFILE client program with command line interface. Command
line editing is supported by means of the GNU readline library.
- An EUROFILE server which can serve multiple connections
simulatneously and suupports navigation (i.e. changing directories).
User authentification is provided by a seperate
authentification library derived from wu-ftpd which allows for fine
grained access control based on user-id, password, and remote isdn
phone number. The design allows for easily exchanging the
authentification routines by user-supplied versions.
This is all still alpha test software.
That means it does certain tasks well at my site, but I know that
they are incomplete, non-conforming and have other bugs as well.
However, they are becoming better and better now and I think that
there are not so many vital missing features left now.
Thus, experienced isdn4linux users are encouraged to test this
and report bugs or success stories, or suggest and contribute improvements.
The navigation support for the server is not fully conformant to the
protocol specifications with respect to some regards. This might in theory
confuse certain clients when the navigation facility is used.
The server and client support extended directory service which could
allow for handling of long filenames, but as several eft implementations
don't support this, you might not take advantages of that.
During several tests it turned out that many commercial EUROFILE
implementations are not protocol conformant, either. One major
inter-working problem is caused by implementations which don't handle
uppercase/lowercase in filenames appropriately. The result is that
some clients can only load either uppercase or lowercase filenames.
A similar problem appears when changing working directories.
Some clients even use upper/lowercase inconsistently when downloading
and uploading files, such clients even cannot access a file uploaded by
themselves before. An even worse problem is that at least one client
replaces '/' characters in directory name by '\'.
IMHO, this is a bug in the commercial EFT implementations. Until the
suppliers of those implementations have fixed this, the server provides
a work-around. If you add a '+' character in front of your login name, the
server will try to treat file names case insensitively and replace '\'
by '/' again. This compatibility mode is somewhat restricted: only the
basename of a file will be handled case-insensitively, the dirname will
currently always be treated as lower case, when the compatibility mode is
active. Thus, in order to avoid trouble, you should always use lower
case directory names in the servers file system tree.
And of course, if multiple files with names differing only in the cases
of the character, you can only access one of them.
Details on this test distribution
==================================
In addition to the files contained in this distribution, you will need
- A recent Linux 2.2.x kernel (2.2.1 or newer is recommended).
It is also possible to replace the isdn subsystem by a recent snapshot
from the isdn4linux CVS server. This is not necessary, but the
CVS version has been reported to work more reliably with recent
kernels. The CVS versions as well as kernels >= 2.3.4 also supports
a new IOCTL which can be used
by eftd for reliably identifying the isdn peer by means of the
remote phone number.
There is also a patch ix25-2.1.128.diff that deals with a low layer
(X.25) interworking problem observed with some clients
(CSD isdn toolbox and maybe also some RVS clients). They send
misformatted X.25 call request packets that confuse the linux X.25 layer.
Applying this patch enables the kernel to correctly reject the
misformatted frames. For working around the interworking problem
you also need to uncomment the last line in include/net/x25.h.
Please read the doc/INTERWORKING file for further details.
The patch should also work with older or newer kernels than 2.1.128.
- the current x25-utils-2.1.x package, which is available from
ftp.hes.iki.fi:/pub/ham/linux/ax25/. The most important programme
therein is the x25_route utility. (x25-utils-2.1.20 is still the
most current release). Don't confuse the x25-utils with the ax25-utils.
The latter is for amateur radio networking and not related to
eftp4linux at all.
- some of the recent isdn4k-utils, in particular isdnctrl (and
loopctrl, if you want to test locally by means of the isdnloop driver).
The isdn4k-utils-3.0beta2.tar.gz. (or newer) are fine.
isdnctrl.c must be compiled against 2.1.x kernel header files.
The 3.0beta2 package is availabe from ftp.franken.de
You can also use an even newer isdn4k-util snapshot from isdn4linux
CVS server. See the isdn4linux FAQ for info about this.
How to build:
=============
See the INSTALL file.
After having typed "make" in the top directory, there will
(hopefully -:) be two important user level programs inside src/:
- eftp is a simple EUROFILE client that allows for transferring files
between a remote machine and your linux box by means of the EUROFILE
transfer protocol on top of isdn. It's command line style user
interface consists of a few ftp-like commands.
- eftd is an EUROFILE server.
Some older programmes, which are of less importance now, will also build:
- x25.echod listens on an x25 socket and echoes back every packet
received. Access to the x25 Q-bit is enabled to demonstrate this
feature which is really necessary for eft and has no equivalent in
TCP/IP sockets.
- tdud.echod listens on an x25 socket and tries to fake an ETS 300 075
protocol session. It mainly encapsulates any received tdu messages in a
t-response-positive tdu message and echoes it back.
Now, you are prepared to test EUROFILE or X.25 on top of isdn4linux. For your
convenience, some scripts are provided in the scripts directory that
ease the task of setting up your system.
See the end of the INSTALL file for quick start instruction or
the files in the doc directory for details.
The server's access control is similar as in the wu-ftp server. In fact,
the access control is taken from wu-ftpd (Georg v.Zezschwitz ported
this, see src/authlib/README for further information). If USER/PASSWD
is omitted, anonymous ftp is assumed. Refer to the eft_wuauth man pages
for learning more about ftp access control and configuring anonymous
access.
It turned out that most EUROFILE clients insert a default
userid/passwd when a user/passwd is not provided explicitly.
With such clients, supply the userid 'ftp' explicitly in order to
access the anonymous EUROFILE account.
Further, as some clients don't support navigation, you should create a
symlink in ~ftp named ".++eft_flat" to, i.e., the pub directory
(cd ~ftp; ln -s pub .++eft_flat). The server will cd to this directory
after login whenever it thinks that the client does not support
navigation. (this is in particular useful with anonymous access
because the ~ftp directory usually contains no downloadable stuff).
The authentication library can even evaluate the peer's
isdn number for its decisions. For this to work reliably,
you need to use the cvs version of isdn4linux as of 1998-08-31 or
newer or a kernel >= 2.3.4.
Other sources of information:
=============================
As you will be using several somewhat exotic and cutting edge parts
of the Linux kernel it might be useful to read the following
mailing lists:
isdn4linux@hub-wue.franken.de or newsgroup de.alt.comm.isdn4linux
linux-x25@vger.rutgers.edu
linux-kernel[-digest]@vger.rutgers.edu
linux-net@vger.rutgers.edu
All lists mentioned above can be subscribed to by sending an e-mail
containing
subscribe LISTNAME
in the message body to
majordomo@DOMAIN
(Replace LISTNAME by the name and DOMAIN by the domain name of the
mailing list).
A description of the linux X.25 implementation and socket interface
is available from the same locations as the x25-utility package.
Watch out for a file x25-doc.tar.gz (MS-Word formatted documents).
A lot of documentation of ITU-T protocols (in particular x.25 and isdn)
is on the "Standards" CD-ROM from Infomagic (http://www.infomagic.com,
reasonable price).
Original ITU standards are quite expensive (http://www.itu.ch
and http://www.etsi.fr). But some libraries collect technical standards,
reading them inside the library is cheaper that ordering them from
your national standard body. For locating such a library,
contact the web server (such as www.din.de) of your natinal
standards body. Users living in Germany might locate such a public
library by following the links in
http://www.beuth.de/partner/index.html.
Good News: ETSI recently made their standards available for download --
Not totally free but at least free of charge. You need to register
first. Quote from ETSI's announcent:
This application is located on
http://webapp.etsi.org/publicationssearch
or can be reached by following "products",
"publications Download" from the ETSI home
page http://www.etsi.org.
http://www.netsmart.gr/teltest/teltest1.1/Lab_file.html
contains a descriptions on the eft core concepts.
The home site of this file, older and (possibly) newer versions, is
ftp://ftp.hamburg.pop.de/pub/LOCAL/linux/i4l-eft/
For reporting bugs or submitting patches, you can reach me by e-mail
(eis@baty.hanse.de).
The file Documentation/isdn/README.x25 present in the (patched) kernel
sources contains general info on linux isdn-X.25 configuration. The
sources of the user level programmes in directory src might also
contain some documentation (and disclaimers :-).
Remark on installing kernel image:
==================================
As you are going to use beta test kernel kernels, it is recommended
that you don't install the compiled kernel as your default kernel
image until you are sure that everything works as expected.
I boot the experimental kernels directly from the source tree
(and I load the modules from there as well).
I've just appended the following lines to my /etc/lilo.conf:
(assume the experimental kernel source tree resides in
/home/kernel/linux-ix25)
Thanks
======
Thanks to all the volunteers who made Linux the powerful OS it is
today. In particular, to all who contributed to isdn4liunx.
Some contributions have been of central importance to the
EUROfile project and I'd like to mention them explicitly:
Jonathan Naylor contributed the Linux X.25 protocol stack
Fritz Elfert contributed the isdnloop driver which was very useful for
keeping my phone bill low while testing.
Lennart Koschella continuously operated a peer eft server that was
used for tests during the initial developement phase.
Point of Presence GmbH provided ftp server space.
Georg v.Zezschwitz adapted the authentification code from the wu-ftpd
which is now used inside the eft server.
Martin Maurer provided protocol traces in the initial phase of development.
Michael Dietrich helped fixing compile/build problems.
Knuth Posern helped tracking down several low layer protocol
compatibility problems.
Matthias Stolte provided enhancements to the setup scripts
and added more command line options to the server.
Michael Mauch added readline and mget/mput support to eftp.
As the eft server's authentication code is derived from wu-ftpd,
the following acknowledgements hold: This product
includes software developed by the Washington University in Saint Louis
and its contributors. This product includes software developed by
the University of California, Berkeley and its contributors.
- Henner

23
eurofile/README.CVS Normal file
View File

@ -0,0 +1,23 @@
$Id: README.CVS,v 1.1 1999/06/29 16:22:38 he Exp $
From version 0.0.11, eftp4linux is added to the isdn4linux cvs
repository. This will allow bug fixes to be faster distributed. It
will also increase availability because the isdn4linux repository
are available from several sources.
As long as it is considered alpha, it will only appear in the isdn4k-utils
configuration menu if the "CONFIG_EXPERIMENTAL" option is set.
You can still cd to the eurofile subdirectory (as described in the
INSTALL file) and compile eftp4linux stand-alone, but you will not
inherit the isdn4k-utils main menu config options then.
As long as it is alpha, it also might not be included with the beta-releases
of the isdn4k-utils package. But in turn, stand-alone snapshots from
the eftp4linux package will contiune to be distributed from the
ftp://ftp.hamburg.pop.de/pub/local/linux/i4l-eft/.
However, not every change commited to cvs will be distrinuted on the
ftp server. Only when important changes (important new features or
imporatnt bug fixes) are present or when sufficiently
many less important changes have accumulated, a new stand-alone release
will be made.

6
eurofile/Rules.make.in Normal file
View File

@ -0,0 +1,6 @@
@EFT_AUTOCONF_WARNING@
# generated from $Id: Rules.make.in,v 1.1 1999/06/29 16:22:39 he Exp $
CRYPTLIB = @CONFIG_LIBCRYPT@
CONFIG_EFTD_WUAUTH = @CONFIG_EFTD_WUAUTH@
CONFIG_EFTP_READLINE = @CONFIG_EFTP_READLINE@
CONFIG_KERNELDIR = @CONFIG_KERNELDIR@

120
eurofile/TODO Normal file
View File

@ -0,0 +1,120 @@
$Id: TODO,v 1.1 1999/06/29 16:22:40 he Exp $
Important:
The server authentication procedure is a port from wu-ftpd.
Review user authentication procedures for possible security
hazards. Check 0-Termination of received string parameters.
Make eftp usable by none-root users. Network interfaces and
X.25 routes are needed to be set up before the isdn connection
can be set up, which is currently done by the eftp.sh shell script
which needs to be run from root. The latter is not acceptable for a
general purpose release.
Not showstoppers, but should be done before a possible stable release:
- more casefix testing with new mangeling method
- selectivly and automatically (for filesystems not supporting
symlinks) disallow symlink-based transfer name database
lookup
- certain disconnect scenarios result in error/warning
messages which are harmless, but might confuse novice users.
- improve autoconf readline support (support non-default
locations of libreadline and lib[n]curses).
- integrate source tree to isdn4k-utils CVS repository.
- 'make install', with reasonable default config files.
- make eftp command input working when stdin is a pipe.
- autoconf is somewhat ugly as several configuration variable
are passed to the source files by different channels
(config.h, -D option) and name schemes are inconsistent.
- scan all source files for FIXME/XXX/#if 0 labels and
try cleaning this up.
- improved event logging (with error indications and
distinction of successful/failed requests).
- improved parameter logging within events (handle unset
parameters nicer).
Currently, when requesting establishment of association and access
regime, the parameters in the corresponding positive response are
not evaluated properly. This might leed to inconsistencies between
the peer's and our own idea of those protocol parameter settings.
To do: Review and improve those regime establishment (and release)
processing.
Currently, exception and error events are often not dealed with
or generated properly. Error events are not counted. Thus, this
implementation might fail if certain error conditions occur.
To do: Review and improve error handling
Currently the CI field of the result/reason parameter of received
T-response-pos/neg is not allways checked for matching the corresponding
command CI.
To do: Check and implement appropriate exeception actions if
mismatch is detected.
Currently the file header is neither analysed nor processed
(just stripped) when files are received.
To do: Analyse file headers and implement appropriate actions.
Currently, certain ETS 300 075 services (in particular T_Delete, T_Rename,
T_Read_Restart) are not supported. The supported
services don't support all (optional) paramaters. Thus, the corresponding
Eurofile services are not supported, either (in particular no
deletion nor renaming of files).
To do:
Enhance protocol processing.
Not urgent at all, might take care of after the first stable release
if anybody is interested:
For future portability to non-posix system, consider implementing a
tdu_stream object which is based on standard C file handles
instead of unix file-descripters. This might also improve performance
due to internal buffering.
The eftp client provided with eftp4linux is a rather primitive
front end (this is intentinoal) to the eft protocol library's
client code.
To Do: write more user friendly client front ends. Or even better,
add eurofile support to existing user tools (i.e. mozilla,
GUI file managers) or write an eft-http gateway by means
of the eftp4linux core library.
Support other authentification methods (PAM comes to mind)
And the "to do" list is incomplete as well.
Meta to do: Enhance "to do" list.
Supplement by ms@msdatec.de:
Until nobody complains, in short form and in German:
- über Konfiguration durch /etc/isdn/eftd.conf nachdenken
- einkommende Dateien schützen
- Log- von Debug-Infos trennen, Loginfos sollen statistikfähig sein
- how2 schreiben
- NEWS-File
- "install" in "Makefile" implementieren
- Versionsnummern von Protokollimplementation, eftd und eftp trennen.
- Sollte das pid-file nicht von eftd selbst gesetzt/geloescht werden?

1718
eurofile/configure vendored Executable file

File diff suppressed because it is too large Load Diff

86
eurofile/configure.in Normal file
View File

@ -0,0 +1,86 @@
dnl Process this file with autoconf to produce a configure script.
dnl $Id: configure.in,v 1.1 1999/06/29 16:22:42 he Exp $
AC_INIT(COPYING.authlib)
#
# Set these according to your preferrences
#
# Shall eurofile daemon use authentification modules from wu-ftpd?
CONFIG_EFTD_WUAUTH=y
# This will be redefined to "n" by the configure script if no readline
# library supporting the alternate interface is found
CONFIG_EFTP_READLINE=y
I4LCONFDIR=`eval echo ${CONFIG_I4LCONFDIR:-"/etc/isdn"}`
I4LCONFFILE=`eval echo ${CONFIG_CONFFILE:-"/etc/isdn"}`
I4LVERSION=${I4LVERSION:-"?.?"}
CONFIG_KERNELDIR=${CONFIG_KERNELDIR:-"/usr/src/linux"}
CONFIG_SBINDIR=${CONFIG_SBINDIR:-"/sbin"}
CONFIG_MANDIR=${CONFIG_MANDIR:-"/usr/man"}
EFT_TOPDIR=${EFT_TOPDIR:-$PWD}
dnl This warning to be inserted in each file generated by configure.
dnl Warning does not apply to this (configure.in) file.
EFT_AUTOCONF_WARNING=".autoconf_warning"
dnl Checks for programs.
AC_PROG_INSTALL
AC_PROG_CC
AC_PATH_PROG(PERL, perl, /usr/bin/perl, /usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin)
AC_PATH_PROG(ISDNCTRL, isdnctrl, /usr/local/sbin/isdnctrl, /usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin)
AC_PATH_PROG(LOOPCTRL, loopctrl, /usr/local/sbin/loopctrl, /usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin)
AC_PATH_PROG(INSMOD, insmod, /sbin/insmod, /usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin)
AC_PATH_PROG(RMMOD, rmmod, /sbin/rmmod, /usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin)
AC_PATH_PROG(IFCONFIG, ifconfig, /sbin/ifconfig, /usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin)
AC_PATH_PROG(X25ROUTE, x25route, /usr/local/sbin/x25route, /usr/local/sbin:/usr/local/bin:/usr/sbin:/sbin:/usr/bin:/bin)
dnl Checks for libraries.
dnl for command line editing to work, we need a (GNU) readline library
dnl which supports the "alternative interface".
AC_CHECK_LIB(readline,rl_callback_handler_install,,CONFIG_EFTP_READLINE="n",-lncurses)
dnl Checks for header files.
AC_HEADER_STDC
AC_CHECK_HEADERS(fcntl.h sys/ioctl.h unistd.h)
AC_CHECK_HEADERS(linux/isdn.h)
dnl Find current kernel source
dnl Checks for typedefs, structures, and compiler characteristics.
dnl Checks for library functions.
dnl some systems don't contain crypt() in the std C library. Linking servers
dnl with passwd based authentication need -lcrypt in that case.
AC_CHECK_FUNC(crypt,CONFIG_LIBCRYPT="",CONFIG_LIBCRYPT="-lcrypt")
AC_CHECK_FUNC(getdelim,HAVE_GETDELIM="HAVE_GETDELIM",HAVE_GETDELIM="DUMMY")
AC_SUBST(INSTALL)
AC_SUBST(I4LCONFDIR)
AC_SUBST(EFT_TOPDIR)
AC_SUBST_FILE(EFT_AUTOCONF_WARNING)
AC_SUBST(I4LVERSION)
AC_SUBST(CONFIG_KERNELDIR)
AC_SUBST(CONFIG_SBINDIR)
AC_SUBST(CONFIG_MANDIR)
AC_SUBST(CONFIG_LIBCRYPT)
AC_SUBST(CONFIG_EFTP_READLINE)
AC_SUBST(CONFIG_EFTD_WUAUTH)
AC_SUBST(HAVE_GETDELIM)
AC_OUTPUT(scripts/eftp_setup scripts/eftp.sh scripts/eftd.sh
src/config.h Rules.make)

2
eurofile/install-sh Executable file
View File

@ -0,0 +1,2 @@
#!/bin/sh
exit 0