- contains security fix
Damir Rajnovic <gaus@CISCO.COM> on bugtraq:
"We updated our unsupported version of TACACS+ server so it is no longer
vulnerable to oversized T+ packets."
- took again maintainership of port, actually I never wanted to quit
was a committ failure when using port submission from PR
options `start' and `stop' now (unless I have forgotten any). This allows
us to call the scripts from /etc/rc.shutdown with the correct option.
The (42 or so) ports that already DTRT before are unchanged.
Taken from tasic@planka.carrier.kiev.ua
+ some modifications by me
(style, patch additions to compile cleanly, pkg/*)
added convert utility to port/package to enable people
to do migrations, if needed, see the docu for details.
PR: 13716
Submitted by: tasic@planka.carrier.kiev.ua
Port was o.k. to get tacacs up and running using a Cisco router and
I really missed it.
- Added me as maintainer of the port
- Moved sources to my homepage download area
- Compressed sources using bzip2
- Removed some not needed variables in Makefile
- Committed with new nd5 checksum
bsd.port.mk rev. 1.304 for details on the change.
The fix here is one of the following.
(1) Define USE_BZIP2 instead of BUILD_DEPENDS on bzip2 and redefining
EXTRACT_* commands.
(2) Change ${EXTRACT_CMD} to ${TAR} when the command is obviously
calling the "tar" command (i.e., arguments like "-xzf" are spelled
out).
(3) If ${EXTRACT_CMD} is called directly with ${EXTRACT_BEFORE_ARGS},
add ${EXTRACT_AFTER_ARGS} to the command line as well.
(4) If any of EXTRACT_CMD, EXTRACT_BEFORE_ARGS or EXTRACT_AFTER_ARGS
is set, define the other two too.
tac_plus provides Cisco systems routers and access servers
with authentication, authorisation and accounting services.
A configuration file controls the details of authentication,
authorisation and accounting.
PR: 2869
Submitted by: Igor Vinokurov<igor@zynaps.ru>
Note: Although there is no terms and conditions on redistribution found,
the author says there is no restriction. (This is stated in more
recent alpha version.) The only concern is the U.S. Export restriction,
but Cisco has been granted with the right to export their software,
according to the author. And also I haven't been able to find any
implementation that may violate the export control in the source code,
either. So, I import this without any RESTRICTED or NO_CDROM defined.
