similar to: FYI: Possible information disclosure in cfingerd.

-------------- next part -------------- Hello everybody!!! First of all I must say that I'm not an English speaker, so this text may sound a little extrange. I apollogize..... Well, I'm having problems with the SMB printing system. I have spent a lot of time (nearly 15 hours and a houndred of configurations) in it but I could not use it as a printing server. System Configuration: One

We just sent the message below to the security advisory predisclosure list, relating to the release of XSA-26 to XSA-32. As you will see, these have now been publicly released. We''ll have a proper conversation about this in a week or two. Thanks for your attention, Ian. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We regret to announce that a member of the predisclosure list

Hi, For those who heard of the recent France Telecom IPR disclosure against Opus, here's our response: https://hacks.mozilla.org/2013/02/defending-opus/ Cheers, Jean-Marc

I haven't seen anything about this here and thought I should pass it along. christopher neitzert <chris at neitzert.com> made two postings to the full-disclosure list earlier today. They stated, in part: ***** Does anyone know of or have source related to a new, and unpublished ssh exploit? An ISP I work with has filtered all SSH connections due to several root level incidents

https://bugzilla.mindrot.org/show_bug.cgi?id=3196 Bug ID: 3196 Summary: [Information Disclosure] OpenSSH_7.4p1 Raspbian-10+deb9u7 discloses OS version Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: Other Status: NEW Severity: security Priority: P5

Asterisk Project Security Advisory - AST-2018-008 Product Asterisk Summary PJSIP endpoint presence disclosure when using ACL Nature of Advisory Unauthorized data disclosure Susceptibility Remote Unauthenticated Sessions Severity Minor

More patch-o-rama :-( ---Mike >From: Michal Zalewski <lcamtuf@dione.ids.pl> >To: bugtraq@securityfocus.com, <vulnwatch@securityfocus.com>, > <full-disclosure@netsys.com> >X-Nmymbofr: Nir Orb Buk >Subject: [Full-Disclosure] Sendmail 8.12.9 prescan bug (a new one) >[CAN-2003-0694] >Sender: full-disclosure-admin@lists.netsys.com >X-BeenThere:

Has anyone around here heard of this ? ---Mike >Subject: Re: [Full-Disclosure] new ssh exploit? >From: christopher neitzert <chris@neitzert.com> >Reply-To: chris@neitzert.com >To: full-disclosure@lists.netsys.com >X-Mailer: Ximian Evolution 1.4.3.99 >Sender: full-disclosure-admin@lists.netsys.com >X-BeenThere: full-disclosure@lists.netsys.com

The cat is out of the bag, so here''s the full disclosure edition of the current security vulnerability. With Rails 1.1.0 through 1.1.5 (minus the short-lived 1.1.3), you can trigger the evaluation of Ruby code through the URL because of a bug in the routing code of Rails. This means that you can essentially take down a Rails process by starting something like /script/profiler, as the code

It seems that users may be disclosing unintended public key info when logging into remote hosts. Use of the words keypair/keyid/etc have been bastardized. Signature is likely better. Note also, the author may be without clue. Setup: [g] - refers to an administrative group of hosts [n] - refers to a host within that group ws[g][n] - management workstations [trusted] User ssh-add's keys for

Has Centos been tested for this yet? -------- Original Message -------- Subject: [Full-disclosure] [ GLSA 200507-05 ] zlib: Buffer overflow Date: Wed, 06 Jul 2005 16:23:20 +0200 From: Thierry Carrez <koon at gentoo.org> Organization: Gentoo Linux To: gentoo-announce at lists.gentoo.org CC: full-disclosure at lists.grok.org.uk, bugtraq at securityfocus.com, security-alerts at

Hi all! I found this today on FD: http://seclists.org/fulldisclosure/2012/Aug/4

The cat is out of the bag, so here''s the full disclosure edition of the current security vulnerability. With Rails 1.1.0 through 1.1.5 (minus the short-lived 1.1.3), you can trigger the evaluation of Ruby code through the URL because of a bug in the routing code of Rails. This means that you can essentially take down a Rails process by starting something like /script/profiler, as the code

> Asterisk Project Security Advisory - ASA-2007-013 > > +----------------------------------------------------------------------------------+ > | Product | Asterisk | > |----------------------+-----------------------------------------------------------| > | Summary | IAX2

> Asterisk Project Security Advisory - ASA-2007-013 > > +----------------------------------------------------------------------------------+ > | Product | Asterisk | > |----------------------+-----------------------------------------------------------| > | Summary | IAX2

I'm running FreeBSD 4.6.2 on two different machines. Both machines have rync installed by way of the ports library, but one of them is running it as a server. I followed the directions in the man pages for running the server using inetd. Here is what happens: rsync rsync://myusername@10.0.0.8/ rsync: server sent "rysnc version 2.5.5 protocol version 26" rather than

Hello, For some reason, I thought little about the "clear" command today.. Let's say a privileged user (root) logs on, edit a sensitive file (e.g, a file containing a password, running vipw, etc) .. then runs clear and logout. Then anyone can press the scroll-lock command, scroll back up and read the sensitive information.. Isn't "clear" ment to clear the

greeting. a short while ago, i may have gone to a site i should not have. maybe. after visiting, i decided i would check for rpm updates. when yumex opened to available packages, it showed that; openssl.x86_64 0:1.0.1e-42.el6_7.4 was available, so i checked it, then clicked install button. during log display, i got error message, tried again. still got error. seems that there is a

Hello I've two strange problems: - smbd I've attached you my smb.conf, inetd.conf and my log file. Sometimes smbd and nmbd run and somtimes only nmbd run (I check it with ps -ax). But I have access over my shares (I test it with my Win95 machine). Also in my log file there're some error messages (I don't now from where the came). - login scripts My scripts won't run but if

From: Rodrigo Barbosa <rodrigob at suespammers.org> > Actually, there is another neat trick for rpm based systems. > You see, rpm, prior to removing anything, will rename that to ${NAME}.OLD. > So, libc.so.6 becomes libc.so.6.OLD, and then removed. > As we all know, if that library is currently open by any running process, > it won't be imediately removed (even tho you