12-21-2018
Yes... it also has been clear at the unix.com forums for 20 of those 30 years.
We do not support "hacking" which means "illegal activity of any kind including software piracy, breaking into systems without authorization, yadda yadda yadda...)\
Doing "creative legal things" is not "hacking"... hacking is illegal or unethical related activity; and has been that way for unix.com in our rules since 2000.
5 More Discussions You Might Find Interesting
1. What is on Your Mind?
I have updated the backend hosting for UNIX.COM and would appreciate feedback either in the form of a vote in the poll or a post so that we can plan for more changes if any are needed.
In particular let me us know if you see any strange behavior from the site as there may still be some... (8 Replies)
Discussion started by: reborg
8 Replies
2. IP Networking
Setup a site to site VPN between two cisco routers.
One of the site locations is unable to access ports such as https://example.com:9001
How do I let them go into port 9001?
They can ssh, ftp, telnet and everything else.
Is this a VPN issue or ACL access issue?
I put
permit ip host... (0 Replies)
Discussion started by: photon
0 Replies
3. IP Networking
Hi,
I am trying to establish vpn between my linux server and cisco asa at client side.
I installed openswan on my cent os.
Linux Server
eth0 - 182.2.29.10
Gateway - 182.2.29.1
eth1 - 192.9.200.75
I have simple IPtables Like
WAN="eth0"
LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies
4. IP Networking
Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? "
A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies
5. IP Networking
Hi @all,
I try to connect 2 LANs with IPSec/Openswan
LAN 1: 192.168.0.0/24
LAN 2: 192.168.1.0/24
This is my Config:
conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
LEARN ABOUT SUSE
log::dispatch::syslog
Log::Dispatch::Syslog(3) User Contributed Perl Documentation Log::Dispatch::Syslog(3)
NAME
Log::Dispatch::Syslog - Object for logging to system log.
SYNOPSIS
use Log::Dispatch;
my $log =
Log::Dispatch->new
( outputs =>
[ [ 'Syslog',
min_level => 'info',
ident => 'Yadda yadda' ]
]
);
$log->emerg( "Time to die." );
DESCRIPTION
This module provides a simple object for sending messages to the system log (via UNIX syslog calls).
Note that logging may fail if you try to pass UTF-8 characters in the log message. If logging fails and warnings are enabled, the error
message will be output using Perl's "warn".
CONSTRUCTOR
The constructor takes the following parameters in addition to the standard parameters documented in Log::Dispatch::Output:
o ident ($)
This string will be prepended to all messages in the system log. Defaults to $0.
o logopt ($)
A string containing the log options (separated by any separator you like). See the openlog(3) and Sys::Syslog docs for more details.
Defaults to ''.
o facility ($)
Specifies what type of program is doing the logging to the system log. Valid options are 'auth', 'authpriv', 'cron', 'daemon', 'kern',
'local0' through 'local7', 'mail, 'news', 'syslog', 'user', 'uucp'. Defaults to 'user'
o socket ($)
Tells what type of socket to use for sending syslog messages. Valid options are listed in "Sys::Syslog".
If you don't provide this, then we let "Sys::Syslog" simply pick one that works, which is the preferred option, as it makes your code
more portable.
AUTHOR
Dave Rolsky, <autarch@urth.org>
perl v5.12.1 2009-09-22 Log::Dispatch::Syslog(3)