Re: Possible compromise ?

From: Peter Rosa (prosa_at_pro.sk)
Date: 01/27/04

  • Next message: Remko Lodder: "RE: [Freebsd-security] Re: Possible compromise ?"
    To: <freebsd-security@freebsd.org>
    Date: Tue, 27 Jan 2004 21:35:15 +0100
    
    

    Sorry, my syslog is not configured to save auth.* info :-(((
    I did not read syslog.conf carefully...

    PR

    ----- Original Message -----
    From: "Mark Ogden" <ogden@eng.utah.edu>
    To: "Peter Rosa" <prosa@pro.sk>
    Cc: <freebsd-security@freebsd.org>
    Sent: Tuesday, January 27, 2004 9:28 PM
    Subject: Re: Possible compromise ?

    > Peter Rosa on Tue, Jan 27, 2004 at 09:23:45PM +0100 wrote:
    > > OK, sorry for unclear previous message.
    > >
    > > In the past, one man teached me the FreeBSD basics and also installed my
    > > gateway. In that time, I was not able to install and setup FreeBSD by
    > > myself. He left there some holes - e.g. open virtual consoles, unset
    > > firewall, etc. As the time went, I learned a lot about Unixes and
    FreeBSD
    > > and I tried to setup my own firewall, install and setup some programs
    (with
    > > big help of this and Questions lists, manpages and other books).
    > >
    > > When I tried to setup more security on that system, except other things,
    I
    > > disabled all virtual tty's, because there is no need to connect to this
    > > machine remotelly (it's located 5 steps from my desk). In the past, that
    man
    > > connected to my system remotely from various IPs.
    > >
    > > Now, when I cat /var/log/lastlog, in the very bottom of the file, I can
    read
    > > some connects from remote machines to ttyp0 and ttyp1.
    >
    > take a look at the /var/log/auth.log, it will show you everyone that
    > remote connected and was denied.
    >
    > -Mark
    >
    > >It's impossible for
    > > me to retrieve connection dates from that file. Of course, I read man
    last,
    > > man wtmp, etc., but there is nothing about /var/log/lastlog file.
    > >
    > > May be, that lines was added in the deep past, when the machine was
    open.
    > > But may be, it was done in few previous days...
    > >
    > > I know, if my machine was compromised, it is impossible to believe in
    > > anything on that machine (also kernel, sources). So, are there some
    other
    > > ways to get information about connection dates?
    > >
    > > Peter Rosa
    > >
    > > _______________________________________________
    > > freebsd-security@freebsd.org mailing list
    > > http://lists.freebsd.org/mailman/listinfo/freebsd-security
    > > To unsubscribe, send any mail to
    "freebsd-security-unsubscribe@freebsd.org"
    >

    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"


  • Next message: Remko Lodder: "RE: [Freebsd-security] Re: Possible compromise ?"

    Relevant Pages

    • Re: Damaged PC
      ... if you want to call it that is the NIC cable connection. ... That was initially disconnected until setup started looking for a network, ... I was also unable to do a repair install. ... >> software to look for viruses, trojans, etc results in reboots. ...
      (microsoft.public.windowsxp.hardware)
    • RE: Exchange 2003/5.5 Setup Issue
      ... When I first setup the ADC, the wizard forced me to setup a connection ... Once I found out Exchange setup was trying to ... install the new 2003 server in to. ...
      (microsoft.public.exchange.setup)
    • Re: Possible compromise ?
      ... I was not able to install and setup FreeBSD by ... > me to retrieve connection dates from that file. ...
      (FreeBSD-Security)
    • Re: [Freebsd-security] Re: Possible compromise ?
      ... Subject: [Freebsd-security] Re: Possible compromise? ... I was not able to install and setup FreeBSD by ... >> me to retrieve connection dates from that file. ...
      (FreeBSD-Security)
    • Re: 3 PC SOHO Network setup problem
      ... As I say below, my setup should ... >>so security on the wireless side is not a major concern. ... no PC has an internet connection other than through the router. ... > only by the Guest account, which means this computer will be open to anyone. ...
      (microsoft.public.windowsxp.network_web)