similar to: *ALERT*: ADM Worm. Worm for Linux x86 found in wild.

Displaying 20 results from an estimated 700 matches similar to: "*ALERT*: ADM Worm. Worm for Linux x86 found in wild."

1999 Mar 29
0
Re: ADM Worm. Worm for Linux x86 found in wild. (fwd)
Hi, some more info on the previous admw0rm alert. Fwd'd from BugTraq Greetings, Jan-Philip Velders ---------- Forwarded message ---------- Date: Fri, 26 Mar 1999 21:17:40 +0100 From: Mixter <mixter@HOME.POPMAIL.COM> To: BUGTRAQ@NETSPACE.ORG Subject: Re: ADM Worm. Worm for Linux x86 found in wild. The "ADM w0rm" is public and can be found at:
1999 Mar 26
2
Re: [Security - intern] *ALERT*: ADM Worm. Worm for Linux x86 found in wild.
On Fri, 26 Mar 1999, Thomas Biege wrote: > Date: Fri, 26 Mar 1999 09:34:10 +0100 (MET) > From: Thomas Biege <thomas@suse.de> > To: Jan-Philip Velders <jpv@jvelders.tn.tudelft.nl> > Cc: linux-security@redhat.com > Subject: Re: [Security - intern] [linux-security] *ALERT*: ADM Worm. Worm for Linux x86 found in wild. > The worm just exploits old security holes, so
1998 Jul 14
1
Different Forms of attack...
Question, there are the teardrop, ping of death, DoS and a host of other forms of attacks. While all of the research that I have been doing concerning another form of an attack.... I became sorta stumped on an idea... is there anywhere.... a description on what to expect or what happenes during any one of these or other attacks listed somewhere? If so, could someone please direct me in that
2018 Feb 27
1
Scheduled AutoCommit Function for WORM Feature
Hello Gluster Community, while reading that article: https://github.com/gluster/glusterfs-specs/blob/master/under_review/worm-compliance.md there seems to be an interesting feature planned for the WORM Xlator: *Scheduled Auto-commit*: Scan Triggered Using timeouts for untouched files. The next scheduled namespace scan will cause the transition. CTR DB via libgfdb can be used to find files that
2004 Feb 23
1
(Fwd) VIRUS (Worm.SomeFool) IN MAIL TO YOU (from <rsync-bounce
I have received the below notice about the rsync list. There is a worm among us. ------- Forwarded message follows ------- Return-Path: <postmaster@innevi.com> Received: from bleep.innevi.com ([64.30.26.9]) by mail.dubois-king.COM (8.11.6/8.11.6) with ESMTP id i1K7n3p14977 for <ppalumbo@dubois-king.com>; Fri, 20 Feb 2004 02:49:03 -0500 Content-Type: text/plain;
1998 Aug 05
6
Problem with TCP_wrappers
Hi, I''m running into something weird here. I''m using RH5.1 with tcp_wrappers 7.6. The syntax for hosts.allow and hosts.deny is: <service list> : <access list> [ : <shell_command> ] Everything works when I _don''t_ use the shell_command. I used the _exact_ line as in the man-pages utilising "safe_finger" (comes with tcp_wrappers), tcpdchk
2017 Jul 07
1
GluserFS WORM hardlink
GlusterFS WORM hard links will not be created OS is CentOS7 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170707/aaea8dfc/attachment.html>
2017 Jul 10
1
GlusterFS WORM mode can't create hard link pliz ㅠ
hard linksA read-only file system does not produce a hard link in GlusterFS WORM mode. Is it impossible? OS is CentOS7 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170710/837d3179/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: error.png
2004 Dec 05
0
VIRUS (Worm.SomeFool.Gen-2) IN MAIL FROM YOU
VIRUS ALERT Our content checker found virus: Worm.SomeFool.Gen-2 in email presumably from you (<logcheck-devel at lists.alioth.debian.org>), to the following recipient: -> barbier at linuxfr.org Please check your system for viruses, or ask your system administrator to do so. Delivery of the email was stopped! For your reference, here are headers from your email:
2002 Feb 19
0
RE Linux and SMB using single passwd
Thanks for the reply. This will not quite do what I want as I dont want local unix users, only smb users. Reason: if a smb user is added and only an smb user and the Linux system uses pam _smb, I can deliver pop mail to the user without them having a local unix user. I have this working very well with LDAP and NIS where I only add a NIS or LDAP user but no unix users and I can still deleiver
2006 Nov 06
1
pptp, ipsec and vpn
Hi All, This is a general VPN question; PPTP VPNs seem to be very easy to set up with CentOS as the VPN server and the built-in windose client, but how do list members feel about the security vunerabilities reported with the MS implementation? Specifically the 6 problems reported here : http://www.schneier.com/pptp-faq.html or maybe im being paranoid? Would any of you roll this solution out
1998 Sep 01
5
/bin/login problem
I would be surprised if someone hasn''t encountered this already, but I haven''t found any discussion of the nature of this problem. I run RehHat 5.0. If a user makes a mistake in the login process such as the following: login: mistake password: xxx Login incorrect! login: username password xxxx bash$ a ps will show, among other things, 2333 /bin/login --mistake. Since
2018 Mar 12
0
Expected performance for WORM scenario
Hi, Gluster will never perform well for small files. I believe there is nothing you can do with this. Ondrej From: gluster-users-bounces at gluster.org [mailto:gluster-users-bounces at gluster.org] On Behalf Of Andreas Ericsson Sent: Monday, March 12, 2018 1:47 PM To: Gluster-users at gluster.org Subject: [Gluster-users] Expected performance for WORM scenario Heya fellas. I've been
2018 Mar 13
0
Expected performance for WORM scenario
Well, it might be close to the _synchronous_ nfs, but it is still well behind of the asynchronous nfs performance. Simple script (bit extreme I know, but helps to draw the picture): #!/bin/csh set HOSTNAME=`/bin/hostname` set j=1 while ($j <= 7000) echo ahoj > test.$HOSTNAME.$j @ j++ end rm -rf test.$HOSTNAME.* Takes 9 seconds to execute on the NFS share, but 90 seconds on
2003 Apr 29
2
Samba, Linux, and file locking
Many moons ago, Samba used to build perfectly on Linux. Ever since I upgraded from 2.2.3, though, I've had to hack the configure script to get it to build, because Samba's configure is utterly and unshakeably convinced that no file locking of any kind exists on Linux. Once so configured, it builds, tests and runs perfectly. Can anyone tell me why Samba started disbelieving in
2010 Sep 01
2
Makefile bug in nut-2.4.3
I'm just in the process of upgrading from nut-2.4.1 to 2.4.3 on a dual-Xeon box running Solaris 10 amd64 (i686-pc-solaris2.10). I configured as follows: ./configure --prefix=/opt/nut --with-gnu-ld --with-serial --without-usb --with-cgi --with-gd-includes=-I/usr/local/include --with-gd-libs="-L/usr/local/lib -R/usr/local/lib -lgd" --with-user=nut --with-group=nut
2018 Mar 13
1
Expected performance for WORM scenario
On Tue, Mar 13, 2018 at 2:42 PM, Ondrej Valousek < Ondrej.Valousek at s3group.com> wrote: > Yes, I have had this in place already (well except of the negative cache, > but enabling that did not make much effect). > > To me, this is no surprise ? nothing can match nfs performance for small > files for obvious reasons: > Could you give profile info of the run you did with
2010 Sep 09
2
HP R3000XR charge level
This is not a NUT question per se ... or at least, I don't think it is. I just replaced the battery pack in my HP R3000XR; the new batteries were shipped with 90% charge, were at about 87% when they went in, and were up to 98% charge the next day. Last weekend, the server that runs NUT went down for no apparent reason, wiping out its boot blocks, corrupting its boot archive beyond
2018 Mar 14
0
Expected performance for WORM scenario
That seems unlikely. I pre-create the directory layout and then write to directories I know exist. I don't quite understand how any settings at all can reduce performance to 1/5000 of what I get when writing straight to ramdisk though, and especially when running on a single node instead of in a cluster. Has anyone else set this up and managed to get better write performance? On 13 March
2001 Sep 27
4
ssh2 key passphrase problems in 2.9.9 on Linux
I've just compiled and installed openssh-2.9.9p2 (compiled against openssl-0.9.6b using gcc-3.0.0) on a Slackware 7-based Linux machine (kernel 2.4.6ac2). The previously installed version was 2.9p2, compiled against openssl-0.9.6a, also with gcc-3.0.0, but with a different build of gcc-3.0.0. Everything seems to work fine except for one problem: passphrase matching for ssh2 keys