From owner-freebsd-security  Tue Aug 29 13:02:45 1995
Return-Path: security-owner
Received: (from majordom@localhost)
          by freefall.FreeBSD.org (8.6.11/8.6.6) id NAA22273
          for security-outgoing; Tue, 29 Aug 1995 13:02:45 -0700
Received: from ns1.win.net (ns1.win.net [204.215.209.3])
          by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id NAA22266
          for <security@freebsd.org>; Tue, 29 Aug 1995 13:02:41 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id QAA01140 for security@freebsd.org; Tue, 29 Aug 1995 16:07:57 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199508292007.QAA01140@ns1.win.net>
Subject: libc seeking/finding
To: security@freebsd.org
Date: Tue, 29 Aug 1995 16:07:56 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 378       
Sender: security-owner@freebsd.org
Precedence: bulk


I'm rebuilding a number of images due to the recent libc change.  I can locate
all the staticly linked images and take care of them.

I just realized that I might have a lot of dynamically linked images that are
using the older libc.so.* modules.  Does anybody know of a slick way to hunt
down the images that are using the older libc's?

Regards,

Mark Hittinger
bugs@win.net