Owner`s manual

LICENSE

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.
Acknowledgments
Appreciation Time!!!! There are far too many people to try to thank
them all; many people have contributed to the development of
Kerberos V5. This is only a partial listing....
Thanks to Kevin Coffman and the CITI group at the University of
Michigan for providing patches for implementing RPCSEC_GSS
authentication in the RPC library.
Thanks to Derrick Schommer for reporting multiple memory leaks.
Thanks to Quanah Gibson-Mount of Stanford University for helping
exercise the thread support code.
Thanks to Michael Tautschnig for reporting the heap buffer overflow
inthe password history mechanism. [MITKRB5-SA-2004-004]
Thanks to Wyllys Ingersoll for finding a buffer-size problem in
theRPCSEC_GSS implementation.
Thanks to the members of the Kerberos V5 development team at
MIT, both past and present: Danilo Almeida, Jeffrey Altman, Jay
Berkenbilt, Richard Basch, Mitch Berger, John Carr, Don Davis,
Alexandra Ellwood, Nancy Gilman, Matt Hancher, Sam Hartman, Paul
Hill, Marc Horowitz, Eva Jacobus, Miroslav Jurisic, Barry Jaspan,
Geoffrey King, John Kohl, Peter Litwack, Scott McGuire, Kevin
Mitchell, Cliff Neuman, Paul Park, Ezra Peisach, Chris Provenzano,
Ken Raeburn, Jon Rochlis, Jeff Schiller, Jen Selby, Brad Thompson,
Harry Tsai, Ted Ts’o, Marshall Vale, Tom Yu.
Very special thanks go to Marshall Vale, our departing team leader.
Over the past few years, Marshall has been extremely valuable to
us as mentor, advisor, manager, and friend. Marshall’s devotion as a
champion of Kerberos has helped our team immensely through many
trials and hardships. We will miss him tremendously, and we wish
him the best in his future endeavors.
Exhibit-U
Copyright (c) 1989 The Regents of the University of California.
All rights reserved.
This code is derived from software contributed to Berkeley by Mike
Muuss.
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.
n
License Information for the Software
Used in the Unit
About GPL (GNU-General Public
License), LGPL (GNU Lesser General
Public License) License
This product uses GPL/LGPL software and software
made by other companies.
After you purchase this product, you may procure,
modify or distribute the source code of the GPL/
LGPL software that is used in the product.
DENON provides the source code based on the
GPL and LPGL licenses at the actual cost upon your
request to our customer service center. However,
note that we make no guarantees concerning the
source code. Please also understand that we do not
offer support for the contents of the source code.