About iTunes Store authorization and deauthorization


 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS About iTunes Store authorization and deauthorization
# 1  
Old 10-31-2008
About iTunes Store authorization and deauthorization

Deauthorizing a computer allows you to manage which computers can play music, videos, audiobooks, or other content purchased from the iTunes Store. Authorization helps protect the copyrights on the content you buy. You can use your digital rights management (DRM)-protected music purchases1 from the iTunes Store on up to five different computers (these can be any mix of Macintosh or Windows-compatible computers). When you play an item you've purchased, your computer is "authorized" to play content purchased using your Apple Account. Note: Songs you encode in AAC format from a source other than the iTunes Store, such as your own audio CDs, and songs from iTunes Plus downloads do not need to be authorized.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
gss_auth_rules(5)                                       Standards, Environments, and Macros                                      gss_auth_rules(5)

NAME
gss_auth_rules - overview of GSS authorization DESCRIPTION
The establishment of the veracity of a user's credentials requires both authentication (Is this an authentic user?) and authorization (Is this authentic user, in fact, authorized?). When a user makes use of Generic Security Services (GSS) versions of the ftp or ssh clients to connect to a server, the user is not neces- sarily authorized, even if his claimed GSS identity is authenticated, Authentication merely establishes that the user is who he says he is to the GSS mechanism's authentication system. Authorization is then required: it determines whether the GSS identity is permitted to access the specified Solaris user account. The GSS authorization rules are as follows: o If the mechanism of the connection has a set of authorization rules, then use those rules. For example, if the mechanism is Kerberos, then use the krb5_auth_rules(5), so that authorization is consistent between raw Kerberos applications and GSS/Kerberos applications. o If the mechanism of the connection does not have a set of authorization rules, then authorization is successful if the remote user's gssname matches the local user's gssname exactly, as compared by gss_compare_name(3GSS). FILES
/etc/passwd System account file. This information may also be in a directory service. See passwd(4). ATTRIBUTES
See attributes(5) for a description of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
ftp(1), ssh(1), gsscred(1M), gss_compare_name(3GSS), passwd(4), attributes(5), krb5_auth_rules(5) SunOS 5.10 13 Apr 2004 gss_auth_rules(5)