Disabling UPnP in Windows Pidgin 2.3.0

David F. Severski davidski-pg at deadheaven.com
Thu Nov 29 19:35:13 EST 2007

On Thu, Nov 29, 2007 at 07:22:26PM -0500, Daniel Atallah wrote:
> On Nov 29, 2007 7:11 PM, David F. Severski <davidski-pg at deadheaven.com>
> wrote:
> > On Thu, Nov 29, 2007 at 06:12:59PM -0500, Evan Schoenberg wrote:
> > > On Nov 29, 2007, at 10:06 AM, <davidski-pg at deadheaven.com> wrote:
> > >> Are there any existing or planned facilities to disable UPnP support in
> > >> the
> > >> Windows Pidgin port?  An old Gaim ticket to provide a config option for
> > >> this
> > >> seems to have gone stale.  The only way I've found to eliminate this
> > >> unnecessary service has been to block it at the host firewall level.
> > >
> > > Out of curiosity, why would you want to disable UPnP?
> >
> > I, like many users, do not use UPnP.  In fact, given the history of UPnP
> > on Windows, it's one of the first services I disable when hardening
> > that OS.
> Pidgin's functionality is in no way dependent on the win32 UPnP service, nor
> does pidgin doesn't interact with it.

Understood.  I was trying to draw attention to the problems inherent when
running systems and services that are not needed.  The XP UPnP service
may have been a poor example, for which I apologize.

Pidgin still has a UPnP client as core functionality which cannot be
turned off.  Pidgin is therefore listening for announcements and
configuration information from a service with no possibility of
instructing the client to ignore any rogue input.  If Pidgin was instead
implementing a Telnet server, I would have the same concern.  I expect
software packages to be as minimally chatty and to listen to only those
services and announcements that I instruct them to be listening for.


More information about the Support mailing list