Sponsored Content
Special Forums Cybersecurity How to know when you've been hacked Post 302246341 by techlinux on Monday 13th of October 2008 11:24:08 AM
Old 10-13-2008
Guard your file system
Guard against Cross-Site Scripting vulnerabilities
Verify form posts
Protect against Cross-Site Request Forgeries
Guard your database
Guard your session data
 

3 More Discussions You Might Find Interesting

1. Linux

pc hacked

Hi, i think someone has hacked my server, the following rules used to come which i haven't put. Please help me i couldnt find out how this rules are apply, i think someone has put an script which generates enables the rules. But after restarting the iptables everything seems to be working... (0 Replies)
Discussion started by: naik_mit
0 Replies

2. Cybersecurity

Server hacked on known port

Hi, There is a recent case whereby it was reported that one of the production servers was hacked on port 1521. However, I am not sure how this was possible, as I checked that the OS firewall (iptables) is on : # /etc/init.d/iptables status Table: nat Chain PREROUTING (policy ACCEPT) num ... (7 Replies)
Discussion started by: anaigini45
7 Replies

3. Cybersecurity

Our system was hacked

Someone made a mistake, and left our router wide open, pointing all ports to a SCO 6.0.0 system. Within 24 hours, the following happened. The contents of all the files (except tar files) in three directories, one directory on each of three different file systems, were replaced with nulls. None... (3 Replies)
Discussion started by: jgt
3 Replies
Scope::Guard(3) 					User Contributed Perl Documentation					   Scope::Guard(3)

NAME
Scope::Guard - lexically-scoped resource management SYNOPSIS
my $guard = guard { ... }; # or my $guard = scope_guard &handler; # or my $guard = Scope::Guard->new(sub { ... }); $guard->dismiss(); # disable the handler DESCRIPTION
This module provides a convenient way to perform cleanup or other forms of resource management at the end of a scope. It is particularly useful when dealing with exceptions: the "Scope::Guard" constructor takes a reference to a subroutine that is guaranteed to be called even if the thread of execution is aborted prematurely. This effectively allows lexically-scoped "promises" to be made that are automatically honoured by perl's garbage collector. For more information, see: <http://www.drdobbs.com/cpp/184403758> METHODS
new my $guard = Scope::Guard->new(sub { ... }); # or my $guard = Scope::Guard->new(&handler); The "new" method creates a new "Scope::Guard" object which calls the supplied handler when its "DESTROY" method is called, typically at the end of the scope. dismiss $guard->dismiss(); # or $guard->dismiss(1); "dismiss" detaches the handler from the "Scope::Guard" object. This revokes the "promise" to call the handler when the object is destroyed. The handler can be re-enabled by calling: $guard->dismiss(0); EXPORTS
guard "guard" takes a block and returns a new "Scope::Guard" object. It can be used as a shorthand for: Scope::Guard->new(...) e.g. my $guard = guard { ... }; Note: calling "guard" anonymously, i.e. in void context, will raise an exception. This is because anonymous guards are destroyed immediately (rather than at the end of the scope), which is unlikely to be the desired behaviour. scope_guard "scope_guard" is the same as "guard", but it takes a code ref rather than a block. e.g. my $guard = scope_guard &handler; or: my $guard = scope_guard sub { ... }; or: my $guard = scope_guard $handler; As with "guard", calling "scope_guard" in void context will raise an exception. VERSION
0.20 SEE ALSO
o B::Hooks::EndOfScope o End o Guard o Hook::Scope o Object::Destroyer o Perl::AtEndOfScope o ReleaseAction o Scope::local_OnExit o Scope::OnExit o Sub::ScopeFinalizer o Value::Canary AUTHOR
chocolateboy <chocolate@cpan.org> COPYRIGHT
Copyright (c) 2005-2010, chocolateboy. This module is free software. It may be used, redistributed and/or modified under the same terms as Perl itself. perl v5.16.2 2010-05-16 Scope::Guard(3)
All times are GMT -4. The time now is 06:25 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy