up2date behaviour

[William Wong]

Hey,

I installed the SRPM for postfix so that SASL is enabled.  If a new security
patch for postfix was released, would up2date install a new postfix that
DIDN'T have SASL support?

- Will




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Re: Trouble ticket system

[William Wong]

There's also mantis.  I haven't been following this thread in detail.  Don't
know if it's already been mentioned.

- Will

- Original Message -
From: "Anthony E. Greene" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 11, 2002 12:51 PM
Subject: Re: Trouble ticket system


> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 11-Sep-2002/07:57 -0400, Chris Mason <[EMAIL PROTECTED]> wrote:
> >Finally got it installed and it is fabulous. Pretty hard to install and
> >configure, but very complex and full featured. Overkill for my needs,
> >but very nice.
>
> I looked at RT, but it seemed over-capable and over-complicated for my
> needs. I needed something easy to install and manage. I also wanted
> something that I was confident would work with my favorite database,
> PostgreSQL. After some looking around, I found Teacup PRMS:
>
>   http://www.altara.org/teacup.html
>
> It's not a full-featured as RT, but if your needs are simple, then Teacup
> may be good enough. It's easy to install and has header/footer templates
> for the web pages to make it easy to give it a style that is consistent
> your intranet.
>
> Here's a whole list of similar software:
>
>   http://linas.org/linux/pm.html
>
> Tony
> - --
> Anthony E. Greene 
> OpenPGP Key: 0x6C94239D/7B3D BD7D 7D91 1B44 BA26  C484 A42A 60DD 6C94 239D
> AOL/Yahoo Chat: TonyG05  HomePage: 
> Linux: the choice of a GNU Generation. 
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: Anthony E. Greene 0x6C94239D <[EMAIL PROTECTED]>
>
> iD8DBQE9f3SHpCpg3WyUI50RAtrKAJ9HZH5fxwtUARuaWKHWhvSZcdfKSACfepC7
> v6PfUUMS4WLQd2cufM5TjGA=
> =+VJH
> -END PGP SIGNATURE-
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
> https://listman.redhat.com/mailman/listinfo/redhat-list
>




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Re: Don't display firewall messages to screen

[William Wong]

I had the same problem.  But one day it seemed to magically disappear.

Some reasons why it may have went away:
1) ran "service iptables save" to save firewall rules
2) up2date'd the system including new kernel
3) reboot after that (so that new kernel takes effect)

I suspect updat'n the kernel did the job, since I had commented out'n
ANYTHING to console in syslog and it still did wrote junk to the screen.

BTW, I'm using RedHat 7.3 and I believe I'm already on the 2rd kernel update
they released: 2.4.18-10

- Will

- Original Message -
From: "Tom Pollerman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 10, 2002 10:51 AM
Subject: Re: Don't display firewall messages to screen


> On Mon, 09 Sep 2002 20:58:48 -0700
> Stephen Rasku <[EMAIL PROTECTED]> wrote:
>
> > On Saturday 07 September 2002 07:38 pm, Robert Canary wrote:
> > > try adding
> > > *.debug /var/log/debug.log
> >
> > I tried that.  It logs the firewall messages (plus some other
> > things) to that file.  But it still logs to /var/log/messages and it
> > still logs to the screen.  I don't actually want it to any
> > additional places.  I just want it to stop logging to the screen.
> >
> > > it is hard to tell which facility to capture, but since you have
> > > debuggibg turned on I am guessing it should be in the .debug sub
> > > facility.
> >
> > From this firewall message:
> > Sep  9 19:27:08 hostname kernel: Dropped: IN=eth0 OUT=
> > MAC=00:05:xx:xx:xx:xx:00:00:77:95:6e:c6:08:00 SRC=24.68.18.131
> > DST=xx.xx.xx.xx LEN=78 TOS=0x00 PREC=0x00 TTL=125 ID=5039 PROTO=UDP
> > SPT=137 DPT=137 LEN=58
> >
> > It appears that it is the kernel facility that is being logged.
> > This makes sense since it's a kernel module that does the filtering.
> >
> > From this portion of my "iptables -L" command
> >
> > LOGall  --  anywhere anywhere   LOG
> > level warning prefix `Dropped:
> >
> > it appears that it's logging with a priority of 'warning'.  When I
> > wrote that I was "debugging" my firewall, I was trying to figure out
> > why it isn't working.  For the time being, I am assuming it is
> > because of an incorrect firewall rule.  I added a rule to display
> > every received packet so I can see what is being received and what
> > is being dropped.  I didn't actually modify syslog.conf to log any
> > facilities at the debug level to do this.
> >
> > >
> > > You might want to try creating a log file local1 thru local7
> >
> > I don't think this will make any difference since the firewall rules
> > seem to be logging using the kernel facility.
> >
> > ...Stephen
> >
> >
>   I run ipchains, so am not up on the syntax or options for iptables.
>   In syslog if you only specify a single priority in a selector
> (without modifiers) you're specifying THAT priority and all HIGHER
> priorities. Might it be that your 'LOG level warning' in the iptables
> rules is being interpreted as *.warn to syslog and, since it is a
> single priority, gets broadcast to everyone because of the line in
> /etc/syslog.conf :
>*.emerg*
>
> As a test, just to see if the screen messages disappear, you could
> comment out the above line and restart syslog.  If they do, you might
> try changing the syntax in your iptable rule to read 'LOG
> level=warning'. The = limits the priority level to warning only -
> nothing higher.
>
>   Best,
>
>   Tom
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
> https://listman.redhat.com/mailman/listinfo/redhat-list
>




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Re: sort/trim file

[William Wong]

sort file | uniq > newfile

- Original Message -
From: "Ashley M. Kirchner" <[EMAIL PROTECTED]>
To: "Red Hat Mailing List" <[EMAIL PROTECTED]>
Sent: Sunday, September 08, 2002 3:40 AM
Subject: sort/trim file


>
> I have a file that contains several hundred IP addresses, and the
reason it contains so many is because all of them have been repeated at some
point or another (several times).  How can I, from this old file, generate a
new file that contains only one instance of those IPs?
>
> Probably something with cat, grep and some other routine.  If someone
can figure this out, that'd be great.
>
> --
> H | "Life is the art of drawing without an eraser." - John Gardner
>   +
>   Ashley M. Kirchner    .   303.442.6410 x130
>   Director of Internet Operations / SysAdmin. 800.441.3873 x130
>   Photo Craft Laboratories, Inc.. 3550 Arapahoe Ave, #6
>   http://www.pcraft.com . .  ..   Boulder, CO 80303, U.S.A.
>
>
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
> https://listman.redhat.com/mailman/listinfo/redhat-list
>




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list

Re: postfix & sasl & redhat 7.3

[William Wong]

Ok finally got it working.  The PAM wasn't working right and un-chroot'n
smtpd for postfix let sasldb work.  I had to recompile cyrus to support
pwcheck so it could read /etc/shadow.

Thanks for the help everyone.

- Will

- Original Message -
From: "Mike Burger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, August 23, 2002 3:36 PM
Subject: Re: postfix & sasl & redhat 7.3


> On my 7.1 box, I'm using the sasl installed with teh system.
>
> I just needed to make sure that postfix was compiled with the sasl stuff
in
> it, and as I said in my last message, I used the src.rpm to do so.
>
> William Wong <[EMAIL PROTECTED]> said:
>
> > I'm pretty sure custom compiling would work nicely (my last ditch
option),
> > but I'm trying to use the default cyrus rpm that installed with RedHat
7.3
> > (cyrus-sasl-1.5.24-25).  I'm wondering if anyone has ever got it work
with
> > these default Redhat packages.
> >
> > - Will
> >
> > - Original Message -
> > From: "Teodor Georgiev" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, August 23, 2002 11:38 AM
> > Subject: Re: postfix & sasl & redhat 7.3
> >
> >
> > >
> > > 1. compile SASL with the saslauthd method (the default for Cyrus SASL
2.x)
> > > 2. in pwcheck use saslauthd as method.
> > > 3. start saslauthd with the appropriate options and tell it the
backend.
> > >
> > > man saslauthd and you will see :)
> > >
> > > - Original Message -
> > > From: "William Wong" <[EMAIL PROTECTED]>
> > > To: <[EMAIL PROTECTED]>
> > > Sent: Friday, August 23, 2002 6:22 PM
> > > Subject: Re: postfix & sasl & redhat 7.3
> > >
> > >
> > > > Hi Mike,
> > > >
> > > > Thanks for the suggestion, though I'm still having problems.  I
changed
> > my
> > > > /usr/lib/sasl/smtpd.conf to use pam as the pwcheck_method and it
doesn't
> > > > like it (unfortunately).  I ldconfig'd to reload the libraries just
in
> > > case.
> > > >
> > > > This one's a headache as I've gotten sasl to work on a redhat 6.2
> > system,
> > > > though I did custom compile both postfix and sasl for that to work.
> > > >
> > > > - Will
> > > >
> > > > - Original Message -
> > > > From: "Mike Burger" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Thursday, August 22, 2002 11:06 AM
> > > > Subject: Re: postfix & sasl & redhat 7.3
> > > >
> > > >
> > > > > You'll probably need to create /etc/pam.d/smtp and
/etc/pam.d/smtpd,
> > > both
> > > > > containing the following:
> > > > >
> > > > > #%PAM-1.0
> > > > > authrequired /lib/security/pam_stack.so
> > > > service=system-auth
> > > > > account required /lib/security/pam_stack.so
> > > > service=system-auth
> > > > >
> > > > > These will allow the smtp and smtpd systems to authenticate
against
> > pam.
> > > > >
> > > > > On Thu, 22 Aug 2002, William Wong wrote:
> > > > >
> > > > > > Hi there,
> > > > > >
> > > > > > I've looked through the list archives but the suggestions don't
seem
> > > to
> > > > help
> > > > > > my problem.  It goes like this...
> > > > > >
> > > > > > I'm using the default packages that come with the redhat 7.3
> > > > distribution
> > > > > > for postfix & sasl. (sasl came preinstalled with the "server"
type
> > > > > > configuration).  I then installed the source RPM for postfix and
> > > enabled
> > > > > > SASL in the spec file, compiled the package and isntalled it.
I've
> > > > created
> > > > > > entries using saslpasswd and added the necessary options in
main.cf
> > > for
> > > > > > postfix to enable sasl (notably the enable).  I've confirmed
this by
> > > > > > telnet'n to port 25 and sending a ehlo mydomain.com.  It doest
> > respond
> > > > with
> > > > > > PLAIN/CRAM/etc as auth methods.
> > > > > >
&g

postfix & sasl & redhat 7.3

[William Wong]

Hi there,

I've looked through the list archives but the suggestions don't seem to help
my problem.  It goes like this...

I'm using the default packages that come with the redhat 7.3 distribution
for postfix & sasl. (sasl came preinstalled with the "server" type
configuration).  I then installed the source RPM for postfix and enabled
SASL in the spec file, compiled the package and isntalled it.  I've created
entries using saslpasswd and added the necessary options in main.cf for
postfix to enable sasl (notably the enable).  I've confirmed this by
telnet'n to port 25 and sending a ehlo mydomain.com.  It doest respond with
PLAIN/CRAM/etc as auth methods.

However I don't know why postfix will NOT authenticate.

To be sure I've made the sasldb file world readable (to test), however in
the maillog file it says there's an SASL authentication failure.

The suggetions I've seen on this list were: Go DL some guy's RPMs, or
recompile postfix with SASL.  Well I don't see the need to DL someone else's
RPMS when redhat has provided the sources already and I've already compiled
postfix with SASL enabled.

Can anyone offer any light to this problem?

Thanks in advance!

Regards,
- Will




-- 
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list