Login or Register to Ask a Question and Join Our Community


Security Advisories (RSS)

Slackware: xine-lib

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Slackware: xine-lib
# 1  
Old 04-01-2008
Slackware: xine-lib
LinuxSecurity.com: New xine-lib packages are available for Slackware 10.0, 10.1, 10.2, 11.0, 12.0, and -current to fix security issues. Earlier versions of xine-lib suffer from an integer overflow which may lead to a buffer overflow that could potentially be used to gain unauthorized access to the machine if a malicious media file is played back. File types affected this time include .flv, .mov, .rm, .mve, .mkv, and .cak.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT REDHAT

pam_timestamp

pam_timestamp(8)					   System Administrator's Manual					  pam_timestamp(8)

NAME

       pam_timestamp - authenticate using cached successful authentication attempts

SYNOPSIS

       auth sufficient /lib/security/pam_timestamp.so
       session optional /lib/security/pam_timestamp.so

DESCRIPTION

       In  a nutshell, pam_timestamp caches successful authentication attempts, and allows you to use a recent successful attempt as the basis for
       authentication.

       When an application opens a session using pam_timestamp, a timestamp file is created in the timestampdir directory for the user.   When	an
       application attempts to authenticate the user, a pam_timestamp will treat a sufficiently- recent timestamp file as grounds for succeeding.

ARGUMENTS

       debug  turns on debugging via syslog(3).

       timestampdir=name
	      tells pam_timestamp.so where to place and search for timestamp files.  This should match the directory configured for sudo(1) in the
	      sudoers(5) file.

       timestamp_timeout=number
	      tells pam_timestamp.so how long it should treat timestamp files as valid after their last modification date.  This should match  the
	      value configured for sudo(1) in the sudoers(5) file.

       verbose
	      attempt to inform the user when access is granted.

EXAMPLE

       /etc/pam.d/some-config-tool:
       auth sufficient /lib/security/pam_timestamp.so verbose auth required   /lib/security/pam_unix.so
       session required /lib/security/pam_permit.so session optional /lib/security/pam_timestamp.so

CAVEATS

       Users  can  get	confused  when	they  aren't always asked for passwords when running a given program.  Some users reflexively begin typing
       information before noticing that it's not being asked for.

SEE ALSO

       pam_timestamp_check(8)

BUGS

       Let's hope not, but if you find any, please email the author.

AUTHOR

       Nalin Dahyabhai <nalin@redhat.com>

Red Hat Linux							    2002/02/07							  pam_timestamp(8)