Ports Search

Sometimes you want roles. You're not sure about Moose, Mouse, Moo and what was that damned Squirrel thing anyway? Then there's Class::Trait, but it has a funky syntax and the maintainer's deprecated it in favor of Moose::Role and you really don't care that it handles overloading, instance application or has a workaround for the SUPER:: bug. You think a meta-object protocol sounds nifty, but you don't understand it. Maybe you're not sure you want the syntactic sugar for object declaration. Maybe you've convinced your colleagues that roles are a good idea but they're leery of dragging in Moose (your author has had this happen more than once and heard of others making the same complaint). Sometimes you just want good old-fashioned roles which let you separate class responsibility from code reuse.

from the README: Passive OS fingerprinting is based on information coming from a remote host when it establishes a connection to our system. Captured packets contain enough information to identify the operating system. In contrast to active scanners such as nmap and QueSO, p0f does not send anything to the host being identified. For more information, read Spitzner's text at: http://www.enteract.com/~lspitz/finger.html . from the maintainer: Use of this program requires read access to the packet filtering device, typically /dev/bpf0. Granting such access allows the users who have it to put your Ethernet device into promiscuous mode and sniff your network. See http://www.infoworld.com/articles/op/xml/00/05/29/000529opswatch.xml if you do not understand how this can be harmful. Running p0f with no options will cause it to analyse packets intended for other hosts.

from the README: Passive OS fingerprinting is based on information coming from a remote host when it establishes a connection to our system. Captured packets contain enough information to identify the operating system. In contrast to active scanners such as nmap and QueSO, p0f does not send anything to the host being identified. For more information, read Spitzner's text at: http://www.enteract.com/~lspitz/finger.html . from the maintainer: Use of this program requires read access to the packet filtering device, typically /dev/bpf0. Granting such access allows the users who have it to put your Ethernet device into promiscuous mode and sniff your network. See http://www.infoworld.com/articles/op/xml/00/05/29/000529opswatch.xml if you do not understand how this can be harmful. Running p0f with no options will cause it to analyse packets intended for other hosts.

mod_encoding - Apache module for non-ascii filename interoperability This module improves non-ascii filename interoperability of apache (and mod_dav). It seems many WebDAV clients send filename in its platform-local encoding. But since mod_dav expects everything, even HTTP request line, to be in UTF-8, this causes an interoperability problem. I believe this is a future issue for specification (RFC?) to standardize encoding used in HTTP request-line and HTTP header, but life would be much easier if mod_dav (and others) can handle various encodings sent by clients, TODAY. This module does just that. This module adds following directives: EncodingEngine, SetServerEncoding, AddClientEncoding, DefaultClientEncoding, and NormalizeUsername. Note by maintainer: It also solves the problem with the "hostname\\username" way of authentication that Windows machines do when they attach to a DAV server. See the use of the NormalizeUsername directive.

If you have an AT&T Wireless, Bell Canada/Bell Mobility, Cellular One, Cingular, Cricket, Sprint PCS, SkyTel, or T-Mobile cell phone or pager, and you want the ability to send SMS messages to it via a command-line utility, this is what you need. All this program requires is a computer with a baseline Perl 5.x installation and web access. NO EXTRA PERL MODULES REQUIRED! How does it work? SendSMS connects to your service provider's web page and pretends to submit a form to their 'Instant Messaging' web page. Currently, AT&T Wireless, Bell Canada/Bell Mobility, Cellular One, Cingular, Cricket, SkyTel, Sprint PCS, and T-Mobile are supported. Users are encouraged to modify the provided templates to add support for any providers who are currently unsupported. Other Service Providers If you are interested in supporting another service provider please try to modify sendSMS on your own. It is not hard at all. Instructions and examples are included in the code, and if you're familiar with the site you're porting to, it takes about 15 minutes. If you get sendSMS working with any other providers' web sites, please email Paul Kreiner [deacon at thedeacon.org] and/or the port maintainer a patch so it can be added to the next release.