Gentoo: BIND Cache poisoning


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Gentoo: BIND Cache poisoning
# 1  
Old 07-11-2008
Gentoo: BIND Cache poisoning

LinuxSecurity.com: A weakness in the DNS protocol has been reported, which could lead to cache poisoning on recursive resolvers.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

5 More Discussions You Might Find Interesting

1. Linux

File cache /Page cache Linux

Hi All, could any one point out any open source test-suites for "File cache" testing and as well as performance test suites for the same. Currently my system is up with Linux/ext4. Regards Manish (0 Replies)
Discussion started by: hmanish
0 Replies

2. Linux

getting info on Cache Size, Data Cache etc..

Hi all I saw in Microsoft web site www.SysInternals.com a tool called CoreInfo from able to print out on screen the size of the Data and Instruction caches of your processor, the Locigal to Physical Processor mapping, the number of the CPU sockets. etc.. Do you know if in Linux is available a... (2 Replies)
Discussion started by: manustone
2 Replies

3. Cybersecurity

Dns cache poisoning upgrade to bind9.5.0p2

Hi again guys, It seems this is a global thing affecting all the DNS bind versions prior to July 28 2008. I have my work cut out for me very soon, I see at least a handful of servers in my list that either need to patching or upgrading. How many of you guys are affected? Anybody successfully... (4 Replies)
Discussion started by: sparcguy
4 Replies

4. IP Networking

how can we spoof ethernet by ARP cache poisoning on unix through a program

how can we spoof ethernet by ARP cache poisoning on unix through a program... can anyone post the source code to achieve this... (1 Reply)
Discussion started by: ud4u
1 Replies

5. UNIX for Advanced & Expert Users

UBC cache vs. Metadata cache

hi, What is the difference between UBC cache and Metadata cache ? where can i find UBC cache Hits and Metadata cache Hits in hp-ux? Advanced thanx for the help. (2 Replies)
Discussion started by: sushaga
2 Replies
Login or Register to Ask a Question
Catalyst::Plugin::Session::Store::File(3pm)		User Contributed Perl Documentation	       Catalyst::Plugin::Session::Store::File(3pm)

NAME
Catalyst::Plugin::Session::Store::File - File storage backend for session data. SYNOPSIS
use Catalyst qw/Session Session::Store::File Session::State::Foo/; MyApp->config->{'Plugin::Session'} = { storage => '/tmp/session' }; # ... in an action: $c->session->{foo} = 'bar'; # will be saved DESCRIPTION
"Catalyst::Plugin::Session::Store::File" is an easy to use storage plugin for Catalyst that uses an simple file to act as a shared memory interprocess cache. It is based on "Cache::FileCache". METHODS get_session_data store_session_data delete_session_data delete_expired_sessions These are implementations of the required methods for a store. See Catalyst::Plugin::Session::Store. setup_session Sets up the session cache file. CONFIGURATION
These parameters are placed in the hash under the "Plugin::Session" key in the configuration hash. storage Specifies the directory root to be used for the sharing of session data. The default value will use File::Spec to find the default tempdir, and use a file named "MyApp/session/data", where "MyApp" is replaced with the appname. Note that the file will be created with mode 0640, which means that it will only be writeable by processes running with the same uid as the process that creates the file. If this may be a problem, for example if you may try to debug the program as one user and run it as another, specify a directory like "/tmp/session-$>", which includes the UID of the process in the filename. relative Makes the storage path relative to $c-path_to> namespace The namespace associated with this cache. Defaults to an empty string if not explicitly set. If set, the session data will be stored in a directory called "MyApp/session/data/<namespace">. cache_depth The number of subdirectories deep to session object item. This should be large enough that no session directory has more than a few hundred objects. Defaults to 3 unless explicitly set. directory_umask The directories in the session on the filesystem should be globally writable to allow for multiple users. While this is a potential security concern, the actual cache entries are written with the user's umask, thus reducing the risk of cache poisoning. If you desire it to only be user writable, set the 'directory_umask' option to '077' or similar. Defaults to '000' unless explicitly set. SEE ALSO
Catalyst, Catalyst::Plugin::Session, Cache::FileCache. AUTHOR
Sascha Kiefer, esskar@cpan.org COPYRIGHT AND LICENSE
Copyright (C) 2005 Sascha Kiefer This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2009-10-08 Catalyst::Plugin::Session::Store::File(3pm)