Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Simple Authentication and Security Layer


Related Topics

In the News (Wed 16 Dec 09)

  
  RFC 2222 (rfc2222) - Simple Authentication and Security Layer (SASL)
During the authentication protocol exchange, the mechanism performs authentication, transmits an authorization identity (frequently known as a userid) from the client to server, and negotiates the use of a mechanism-specific security layer.
The client responds with a Kerberos ticket and an authenticator for the principal "service.hostname@realm", where "service" is the service name specified in the protocol's profile, "hostname" is the first component of the host name of the server with all letters in lower case, and where "realm" is the Kerberos realm of the server.
The security layers and their corresponding bit-masks are as follows: 1 No security layer 2 Integrity (krb_mk_safe) protection 4 Privacy (krb_mk_priv) protection Other bit-masks may be defined in the future; bits which are not understood must be negotiated off.
www.faqs.org /rfcs/rfc2222.html   (3745 words)

  
  Simple Authentication and Security Layer - Wikipedia, the free encyclopedia
It decouples authentication mechanisms from application protocols, in theory allowing any authentication mechanism supported by SASL to be used in any application protocol that uses SASL.
SASL typically only handles authentication, and another mechanism (such as TLS) is used for encrypting transferred content.
A SASL mechanism is modelled as a series of challenges and responses.
en.wikipedia.org /wiki/SASL   (271 words)

  
 SASL Overview - GNU Simple Authentication and Security Layer 0.0.14
SASL mechanisms are named by strings, from 1 to 20 characters in length, consisting of upper-case letters, digits, hyphens, and/or underscores.
During the authentication protocol exchange, the mechanism performs authentication, transmits an authorization identity (frequently known as a userid) from the client to server, and negotiates the use of a mechanism-specific security layer.
If the use of a security layer is agreed upon, then the mechanism must also define or negotiate the maximum cipher-text buffer size that each side is able to receive.
jamesthornton.com /gnu/gsasl/SASL-Overview.html   (529 words)

  
 Simple
Simple harmonic motion Simple harmonic motion is the motion of a simple harmonic oscillator, a motion that is neither dr...
Simple LR parser A Simple LR parser or SLR parser is an LR(1) parser.
Simple random sample In statistics, a simple random sample from a population is a sample chosen randomly, in which each...
www.brainyencyclopedia.com /topics/simple.html   (952 words)

  
 SASL: Simple Authentication and Security Layer
SASL is the Simple Authentication and Security Layer, a method for adding authentication support to connection-based protocols.
To use SASL, a protocol includes a command for identifying and authenticating a user to a server and for optionally negotiating protection of subsequent protocol interactions.
The main contributors to the Cyrus SASL Library are Rob Earhart, Tim Martin, Larry Greenfield, and Rob Siemborski.
asg.web.cmu.edu /sasl   (237 words)

  
 Network Working Group J   (Site not responding. Last check: 2007-10-10)
In the case that a profile explicitly permits multiple successful SASL negotiations to occur, then in no case may multiple security layers be simultaneously in effect.
SASL mechanism registrations may not be deleted; mechanisms which are no longer believed appropriate for use can be declared OBSOLETE by a change to their "intended use" field; such SASL mechanisms will be clearly marked in the lists published by IANA.
When a server or client supports multiple authentication mechanisms, each of which has a different security strength, it is possible for an active attacker to cause a party to use the least secure mechanism supported.
home.gwu.edu /~lmzhou/SASL/RFC2222_SASL.htm   (3604 words)

  
 Simple Authentication and Security Layer (SASL)
SASL protocol specifications describe the identity form(s) used in authorization and, in particular, prescribe the syntax and semantics of the authorization identity character string to be transferred by mechanisms.
If use of a security layer is negotiated in the authentication protocol exchange, the layer is installed by the server after indicating the outcome of the authentication exchange and installed by the client upon receipt of the outcome indication.
Once the security layer is in effect in the protocol data stream, it remains in effect until either a subsequently negotiated security layer is installed or the underlying transport connection is closed.
www.ipa.go.jp /security/rfc/RFC4422EN.html   (8239 words)

  
 Cyrus SASL for System Administrators
SASL, the Simple Authentication and Security Layer, is a generic mechanism for protocols to accomplish authentication.
If there are n protocols and m different ways of authenticating, SASL attempts to make it so only n plus m different specifications need be written instead of n times m different specifications.
How SASL works is governed by what mechanism the client and server choose to use and the exact implementation of that mechanism.
www.sendmail.org /~ca/email/cyrus/sysadmin.html   (1774 words)

  
 The Internet Report   (Site not responding. Last check: 2007-10-10)
The Simple Authentication and Security Layer (SASL) is a framework for providing authentication and data security services in connection-oriented protocols via replaceable mechanisms.
This document describes how a SASL mechanism is structured, describes how protocols include support for SASL, and defines the protocol for carrying a data security layer over a connection.
Simple Authentication and Security Layer (SASL) (70349 bytes)
ietfreport.isoc.org /ids-wg-sasl.html   (644 words)

  
 GNU Simple Authentication and Security Layer 0.2.10   (Site not responding. Last check: 2007-10-10)
SASL is used by network servers (e.g., IMAP, SMTP) to request authentication from clients, and in clients to authenticate against servers.
GNU SASL is written in pure ANSI C89 to be portable to embedded and otherwise limited platforms.
This appendix contain clarification to various SASL specification that we felt were necessary to include, if for nothing else it may serve as a guide for other implementors that worry about the same issues.
josefsson.org /libgsasl/gsasl.html   (11124 words)

  
 [No title]
Myers Standards Track [Page 5] RFC 2222 SASL October 1997 In the case that a profile explicitly permits multiple successful SASL negotiations to occur, then in no case may multiple security layers be simultaneously in effect.
Myers Standards Track [Page 8] RFC 2222 SASL October 1997 The security layers and their corresponding bit-masks are as follows: 1 No security layer 2 Integrity (krb_mk_safe) protection 4 Privacy (krb_mk_priv) protection Other bit-masks may be defined in the future; bits which are not understood must be negotiated off.
Myers Standards Track [Page 13] RFC 2222 SASL October 1997 The client's selection of a SASL mechanism is done in the clear and may be modified by an active attacker.
www.ietf.org /rfc/rfc2222.txt   (3625 words)

  
 Simple Authentication and Security Layer (SASL)
This document is written to serve two different audiences, protocol designers using this specification to support authentication in their protocol, and implementors of clients or servers for those protocols using this specification.
Registration of a SASL mechanism is done by filling in the template in section 6.4 and sending it in to iana@isi.edu.
SASL mechanism registrations will be posted in the anonymous FTP directory "ftp://ftp.isi.edu/in-notes/iana/assignments/sasl- mechanisms/" and all registered SASL mechanisms will be listed in the periodically issued "Assigned Numbers" RFC [currently STD 2, RFC 1700].
xml.resource.org /public/rfc/html/rfc2222.html   (3799 words)

  
 The Java Community Process(SM) Program - JSRs: Java Specification Requests - detail JSR# 028
Simple Authentication and Security Layer (SASL) specifies a challenge-response protocol in which data is exchanged between the client and the server for the purposes of authentication and (optional) establishment of a security layer on which to carry on subsequent communications.
It also provides a pluggable authentication framework that allows SASL mechanisms to be added dynamically to the runtime environment.
The SASL negotiation protocol is defined by RFC 2222.
jcp.org /en/jsr/detail?id=028   (446 words)

  
 Simple Authentication and Security Layer (sasl) Charter
Using Digest Authentication as a SASL Mechanism (96406 bytes)
Simple Authentication and Security Layer (SASL) (RFC 4422) (73206 bytes)
The PLAIN Simple Authentication and Security Layer (SASL) Mechanism (RFC 4616) (20270 bytes)
www.ietf.org /html.charters/sasl-charter.html   (278 words)

  
 What is SASL? - A Word Definition From the Webopedia Computer Dictionary   (Site not responding. Last check: 2007-10-10)
Originating with RFC 2222, written by John Myers while at Netscape Communications, SASL is a method for adding authentication support to connection-based protocols.
SASL takes effect when a protocol initiates a command for identifying and authenticating a user to a server.
With this option in effect, SASL places a security layer between the protocol and the connection.
www.pcwebopedia.com /TERM/S/SASL.html   (108 words)

  
 GNU Simple Authentication and Security Layer - Summary [Savannah]
GNU SASL is an implementation of the Simple Authentication and Security Layer framework and a few common SASL mechanisms.
The library is flexible with regards to the authorization infrastructure used, as it utilizes callbacks into the application to decide whether an user is authorized or not.
GNU SASL is developed for the GNU/Linux system, but runs on over 20 platforms including most major Unix platforms and Windows.
savannah.gnu.org /projects/gsasl   (248 words)

  
 O'Reilly Network: Using SASL: Pluggable Security
The Simple Authentication and Security Layer (SASL) allows administrators to configure just the right amount of security for the networked applications in their environments.
The way to read this is pretty simple: when the client (C:) establishes a TCP connection to the server (S:), the server sends the time-honored 220 greeting.
One of the cool things about SASL is that even though the administrator has a lot of flexibility in configuring which mechanisms are available, this doesn't translate into a lot of complexity.
www.oreillynet.com /pub/a/network/2002/04/09/sasl.html   (1850 words)

  
 Security and the Java Platform
Security features -- cryptography, authentication and authorization, public key infrastructure, and more -- are built in.
The Java security model is based on a customizable "sandbox" in which Java software programs can run safely, without potential risk to systems or users.
Authenticates peers over an untrusted network and protects the integrity and privacy of data transmitted between them.
java.sun.com /security   (461 words)

  
 JSR 28 - SASL   (Site not responding. Last check: 2007-10-10)
SASL defines a method for adding authentication support to connection-based protocols.
The API should facilitate control of SASL policies on a site-wide basis; site administrators should be able to configure the preferred and allowed authentication mechanisms, encryption strengths, and other mechanism selection parameters.
The API should provide a means for configuring adequate defaults, so that clients can be implemented without detailed awareness of the SASL authentication options and parameters, but allow sophisticated clients to express detailed requirements.
www.worldspot.com /jsr28   (257 words)

  
 GNU SASL Library (Libgsasl) - GNU Project - Free Software Foundation (FSF)
The core GNU SASL library, and most mechanisms, are licensed under the GNU Lesser General Public License.
A mailing list where GNU SASL users may help each other exists, and you can reach it by sending e-mail to help-gsasl@gnu.org.
If you provide paid services for GNU SASL, and would like to be mentioned here, also contact me.
josefsson.org /gsasl   (1028 words)

  
 [No title]   (Site not responding. Last check: 2007-10-10)
SIMPLE AUTHENTICATION AND SECURITY LAYER (SASL) MECHANISMS ---------------------------------------------------------- (last updated 05 April 2005) The Simple Authentication and Security Layer (SASL) [RFC2222] is a method for adding authentication support to connection-based protocols.
Procedures for registering new SASL mechanisms are given in the section "Registration procedures" of RFC2222.
References ---------- [RFC2222] Myers, J., "Simple Authentication and Security Layer (SASL)", RFC 2222, Netscape Communications, October 1997.
www.iana.org /assignments/sasl-mechanisms   (272 words)

  
 PHP Classes - Class: Simple Authentication and Security Layer
When the HTTP server requires authentication, the SASL package provides support for implementing authentication mechanisms like: Basic, Digest, PLAIN, LOGIN, CRAM-MD5, NTLM (Windows or Linux/Unix with Samba).
When the POP3 server requires authentication the SASL package provides support for implementing authentication mechanisms like: PLAIN, LOGIN, CRAM-MD5, NTLM (Windows or Linux/Unix with Samba).
When the SMTP server requires authentication the SASL package provides support for implementing authentication mechanisms like: PLAIN, LOGIN, CRAM-MD5, NTLM (Windows or Linux/Unix with Samba).
www.phpclasses.org /browse/package/1888.html   (221 words)

  
 Sun ONE Directory Server 5.2 Plug-In API Programming Guide: Chapter 6 Handling Authentication
Directory Server supports the two authentication methods described in RFC 2251: simple authentication, rendered more secure through the use of Secure Socket Layer (SSL) for transport; and Simple Authentication and Security Layer (SASL).
If the plug-in bypasses the comparison of authentication information in the client request to authentication information stored in the directory, then the plug-in returns a non-zero value, such as 1, to prevent the server from completing the bind after the pre-operation bind function returns.
The example is intended only to illustrate how a SASL authentication plug-in works, not to provide a secure mechanism for use in production.
docs.sun.com /source/816-6702-10/authent.html   (2667 words)

  
 ipedia.com: POP3 Article   (Site not responding. Last check: 2007-10-10)
P ost O ffice P rotocol version 3 is an application layer Internet standard protocol used to retrieve email from a remote server to a local client over a TCP/IP connection.
Post Office Protocol version 3 is an application layer Internet standard protocol used to retrieve email from a remote server to a local client over a TCP/IP connection.
Although plain text transmission of passwords in POP3 is still common, POP3 currently supports several authentication methods to provide varying levels of protection against illegitimate access to a user's email.
www.ipedia.com /pop3.html   (478 words)

  
 XFOR: Connecting Internet Mail Service (IMS) to IMS with Simple Authentication and Security Layer (SASL)
You can use Simple Authentication and Security Layer (SASL) to link two Exchange Server computers with the Internet Mail Service together if you declare the administrator of the target Internet Mail Service as the SASL account.
Key Manager is used to create the public/private key pair, which used to negotiate a secure connection.
At this point you should have a valid key pair and should be able to start using SSL encryption to encrypt your SMTP transmissions.
support.microsoft.com /support/kb/articles/q174/7/54.asp   (486 words)

  
 GSSAPI - GNU Simple Authentication and Security Layer 0.2.10   (Site not responding. Last check: 2007-10-10)
GSS-API is a framework, similar to SASL, for authentication.
(A new SASL mechanism to support non-Kerberos 5 GSS-API mechanisms may be supported in the future.)
Note that authentication is performed by the GSS-API library.
www.gnu.org /software/gsasl/manual/html_node/GSSAPI.html   (95 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.