Menu
▾
▴
ipcop-devel — Development mailinglist for the IPCop project.
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(259) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(361) |
Feb
(71) |
Mar
(270) |
Apr
(164) |
May
(55) |
Jun
(218) |
Jul
(203) |
Aug
(146) |
Sep
(105) |
Oct
(70) |
Nov
(156) |
Dec
(223) |
| 2003 |
Jan
(229) |
Feb
(126) |
Mar
(461) |
Apr
(288) |
May
(203) |
Jun
(64) |
Jul
(97) |
Aug
(228) |
Sep
(384) |
Oct
(208) |
Nov
(88) |
Dec
(291) |
| 2004 |
Jan
(425) |
Feb
(382) |
Mar
(457) |
Apr
(300) |
May
(323) |
Jun
(326) |
Jul
(487) |
Aug
(458) |
Sep
(636) |
Oct
(429) |
Nov
(174) |
Dec
(288) |
| 2005 |
Jan
(242) |
Feb
(148) |
Mar
(146) |
Apr
(148) |
May
(200) |
Jun
(134) |
Jul
(120) |
Aug
(183) |
Sep
(163) |
Oct
(253) |
Nov
(248) |
Dec
(63) |
| 2006 |
Jan
(96) |
Feb
(65) |
Mar
(88) |
Apr
(172) |
May
(122) |
Jun
(111) |
Jul
(83) |
Aug
(210) |
Sep
(102) |
Oct
(37) |
Nov
(28) |
Dec
(41) |
| 2007 |
Jan
(82) |
Feb
(84) |
Mar
(218) |
Apr
(61) |
May
(66) |
Jun
(35) |
Jul
(55) |
Aug
(64) |
Sep
(20) |
Oct
(92) |
Nov
(420) |
Dec
(399) |
| 2008 |
Jan
(149) |
Feb
(72) |
Mar
(209) |
Apr
(155) |
May
(77) |
Jun
(150) |
Jul
(142) |
Aug
(99) |
Sep
(78) |
Oct
(98) |
Nov
(82) |
Dec
(25) |
| 2009 |
Jan
(38) |
Feb
(86) |
Mar
(129) |
Apr
(64) |
May
(106) |
Jun
(121) |
Jul
(149) |
Aug
(110) |
Sep
(74) |
Oct
(98) |
Nov
(83) |
Dec
(46) |
| 2010 |
Jan
(53) |
Feb
(43) |
Mar
(86) |
Apr
(185) |
May
(44) |
Jun
(58) |
Jul
(41) |
Aug
(47) |
Sep
(52) |
Oct
(49) |
Nov
(47) |
Dec
(66) |
| 2011 |
Jan
(58) |
Feb
(33) |
Mar
(37) |
Apr
(31) |
May
(8) |
Jun
(8) |
Jul
(2) |
Aug
(28) |
Sep
(75) |
Oct
(46) |
Nov
(40) |
Dec
(7) |
| 2012 |
Jan
(61) |
Feb
(32) |
Mar
(20) |
Apr
(6) |
May
(11) |
Jun
(8) |
Jul
(1) |
Aug
(16) |
Sep
(21) |
Oct
(12) |
Nov
(12) |
Dec
(1) |
| 2013 |
Jan
(15) |
Feb
(8) |
Mar
(21) |
Apr
(25) |
May
(18) |
Jun
(20) |
Jul
(21) |
Aug
|
Sep
(1) |
Oct
(9) |
Nov
(10) |
Dec
(13) |
| 2014 |
Jan
(33) |
Feb
(41) |
Mar
(10) |
Apr
(44) |
May
(3) |
Jun
|
Jul
(6) |
Aug
(2) |
Sep
(1) |
Oct
(7) |
Nov
(10) |
Dec
(12) |
| 2015 |
Jan
(1) |
Feb
(17) |
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2016 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
(5) |
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
(4) |
2
(4) |
3
(1) |
4
(8) |
5
(1) |
|
6
(2) |
7
(1) |
8
(8) |
9
(6) |
10
(3) |
11
(1) |
12
(2) |
|
13
(5) |
14
(2) |
15
(1) |
16
(1) |
17
(1) |
18
(1) |
19
|
|
20
|
21
|
22
(7) |
23
(7) |
24
(2) |
25
(1) |
26
(1) |
|
27
(13) |
28
(2) |
29
(3) |
30
(6) |
31
(3) |
|
|
|
From: Mark W. <ma...@wo...> - 2003-07-31 18:37:31
|
Hello, You can download a trial fixes 3 for IPCop 1.3.0 on the website. URL:http://prdownloads.sourceforge.net/ipcop/1.3.0-20030731-fixes3.tar.gz MD5:9c22cfa206d7684c1522eb09964c4506 Size:2780137 bytes It includes the following fixes: - Kernel updated to 2.4.21 - SSH security fix - Permissions on restartsquid - Fixed bug where dhcp would not always die when restarted - Make PulsarDSL more persistent - Fix VPN shutdown when link drops - Fixed access to IPCop across VPN - GUI access when non-transparent proxy configured - Fixed dhcp for DSL links - Fixed traffic graphs script running multiple times - Updated PPPoE binary You need to install this patch manually by untarring it under /tmp and running /tmp/setup. Most patches are minor, except for the kernel update. I would like everyone to test this release before we announce it to the public. Please look at the list above and test the features mentioned. Kind regards, Mark Wormgoor -- *************************************************************** * |\ /| | /| / Mark Wormgoor * * | \ / | | / | / mailto:ma...@wo... * * | \/ |ark |/ |/ormgoor http://www.wormgoor.com/mark/ * *************************************************************** |
|
From: nils <ni...@ei...> - 2003-07-31 13:06:26
|
hi, I was just wondering if there is a way to get ipcop to email a summary of current event say every week/month. nils |
|
From: Arnt K. <ar...@c2...> - 2003-07-31 01:33:33
|
On Wed, 30 Jul 2003 22:13:18 +0100, "Neil A. Hillard" <ne...@re...> wrote in message <bfj85EJuTDK$Ew...@da...>: > In message <200...@c2...>, Arnt Karlsen > <ar...@c2...> writes > > On Wed, 30 Jul 2003 11:45:34 +0200, "Sven Milstein" > > <sve...@tr...> mailed, but most likely meant to post, > > in message > > <ALE...@tr...>, so I > > posted my answer. ;-) > > > > > > > Bearing in mind you get a PIII 733, 64Mb RAM and a 8 or > > > > > 10Gb disk for £129 new (who knows how much 2nd hand) > > > > > and bearing in mind the form factor it might just be an > > > > > idea, added to the fact that apparently Micro$oft loses > > > > > money on each one sold (but they make shed loads on > > > > > each game) might be an incentive !!! I haven't got one > > > > > but have been contemplating one just to run as a web > > > > > server, etc. > > > > > > > > > > I've currently got several running on some Compaq Small > > > > > Form Factor PII 350s and they work a treat (picked up > > > > > for£99 each, I think). > > > > > > > > > > Any thoughts ??? > > > > > > the problem (except the booting stuff) is that the xbox only comes > > > with one ethernet port. i didnt see any additional ethernet > > > adapters on the market. And a firewall with just one interface > > > seems not to be the best idea... > > > > ..agreed, but you say MS Xbox cannot take a pci etc nic? ..are there free slots in Xboxes, anyone? > > ..but it does have usb connectors, how many, and are they usb 1 > > or can they meet usb 2 specs? Linux can do usb networking, and > > so can ipcop, once we add support for usb networking. > > I believe it has 4 USB 1.1 ports (well, it's got a built in 4-port > hub). ..ok, usb-1.1 still beats coax wire, so this is worthwhile. ;-) > Allegedly the cut-down w2k kernel is unable to handle extra downstream > hubs although Linux has absolutely no problem !!! (Surprise, surprise) > > Booting shouldn't be a problem if you don't mind 'modifying' an X-box > with the Cromwell BIOS (see http://xbox-linux.sourceforge.net/). A > clean-room BIOS that will boot you straight into Linux... > > It was just a thought, anyway !!! ..riiiiight. ;-) > Even with just the one NIC it ought to make a half decent web or mail > server (unfortunately there's only 64Mb RAM). -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. |
|
From: Neil A. H. <ne...@re...> - 2003-07-30 21:15:31
|
In message <200...@c2...>, Arnt Karlsen <ar...@c2...> writes >On Wed, 30 Jul 2003 11:45:34 +0200, "Sven Milstein" ><sve...@tr...> mailed, but most likely meant to post, >in message <ALE...@tr...>, >so I posted my answer. ;-) > >> > > Bearing in mind you get a PIII 733, 64Mb RAM and a 8 or >> > > 10Gb disk for =A3129 new (who knows how much 2nd hand) and >> > > bearing in mind the form factor it might just be an idea, >> > > added to the fact that apparently Micro$oft loses money on >> > > each one sold (but they make shed loads on each game) >> > > might be an incentive !!! I haven't got one but have been >> > > contemplating one just to run as a web server, etc. >> > > >> > > I've currently got several running on some Compaq Small >> > > Form Factor PII 350s and they work a treat (picked up for >> > > =A399 each, I think). >> > > >> > > Any thoughts ??? >> the problem (except the booting stuff) is that the xbox only comes >> with one ethernet port. i didnt see any additional ethernet adapters >> on the market. And a firewall with just one interface seems not to >> be the best idea... > >..agreed, but you say MS Xbox cannot take a pci etc nic? > >..but it does have usb connectors, how many, and are they usb 1 >or can they meet usb 2 specs? Linux can do usb networking, and >so can ipcop, once we add support for usb networking. I believe it has 4 USB 1.1 ports (well, it's got a built in 4-port hub). Allegedly the cut-down w2k kernel is unable to handle extra downstream hubs although Linux has absolutely no problem !!! (Surprise, surprise) Booting shouldn't be a problem if you don't mind 'modifying' an X-box with the Cromwell BIOS (see http://xbox-linux.sourceforge.net/). A clean-room BIOS that will boot you straight into Linux... It was just a thought, anyway !!! Even with just the one NIC it ought to make a half decent web or mail server (unfortunately there's only 64Mb RAM). Neil. --=20 Neil A. Hillard E-Mail: ne...@re... Regional Webs Ltd. Web: http://www.regionalwebs.net/ |
|
From: Arnt K. <ar...@c2...> - 2003-07-30 19:38:32
|
On Wed, 30 Jul 2003 11:45:34 +0200, "Sven Milstein" <sve...@tr...> mailed, but most likely meant to post, in message <ALE...@tr...>, so I posted my answer. ;-) > > > Bearing in mind you get a PIII 733, 64Mb RAM and a 8 or > > > 10Gb disk for £129 new (who knows how much 2nd hand) and > > > bearing in mind the form factor it might just be an idea, > > > added to the fact that apparently Micro$oft loses money on > > > each one sold (but they make shed loads on each game) > > > might be an incentive !!! I haven't got one but have been > > > contemplating one just to run as a web server, etc. > > > > > > I've currently got several running on some Compaq Small > > > Form Factor PII 350s and they work a treat (picked up for > > > £99 each, I think). > > > > > > Any thoughts ??? > the problem (except the booting stuff) is that the xbox only comes > with one ethernet port. i didnt see any additional ethernet adapters > on the market. And a firewall with just one interface seems not to > be the best idea... ..agreed, but you say MS Xbox cannot take a pci etc nic? ..but it does have usb connectors, how many, and are they usb 1 or can they meet usb 2 specs? Linux can do usb networking, and so can ipcop, once we add support for usb networking. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. |
|
From: Guy E. <gu...@tr...> - 2003-07-30 08:12:06
|
Driver Version : 3.2.8 Release Date : 24-July-2003 Changes in this version... - Line sync improvements. - CRC errors now reported with Debug=1. - GtiRxStartBin default now 0x20. New drivers can be compiled using the Engine at http://adsl4linux.no-ip.org A precompiled driver for IPCop1.3 can be downloaded at http://adsl4linux.no-ip.org/download.html |
|
From: Mark W. <ma...@wo...> - 2003-07-30 06:53:29
|
Hi, > at the risk of cross posting... > > I've had some troubles with crashes & thanks to ipcop-user@ got as far as > suspecting ext3 (and/or a bad disk). > > http://marc.theaimsgroup.com/?t=105924415300001&r=1&w=2 > > this is all a little bit beyond me in truth, but it seems there are > patches > for ext3 on 2.4.20. Given there is a new release of IPCop in the > pipeline, > is it too late to get them included, assuming they aren't already? I > don't > think I can do this on a vanilla install myself ... > > http://www.zip.com.au/~akpm/linux/ext3/ > > apologies if it's all in hand :) If I'm correct, these bugs only surface when mounting ext3 with: -o data=journal Since we don't do that, you probably won't have filesystem corruption through ext3. All bugs are fixed in 2.4.21, which will be used in the next release. Kind regards, Mark -- *************************************************************** * |\ /| | /| / Mark Wormgoor * * | \ / | | / | / mailto:ma...@wo... * * | \/ |ark |/ |/ormgoor http://www.wormgoor.com/mark/ * *************************************************************** |
|
From: Gilles E. <gil...@wa...> - 2003-07-30 06:11:32
|
----- Original Message ----- From: "Murray" <mu...@mi...> To: <IPC...@li...> Sent: Tuesday, July 29, 2003 9:09 PM Subject: [IPCop-devel] ext3 > > at the risk of cross posting... > > I've had some troubles with crashes & thanks to ipcop-user@ got as far as > suspecting ext3 (and/or a bad disk). > > http://marc.theaimsgroup.com/?t=105924415300001&r=1&w=2 > > this is all a little bit beyond me in truth, but it seems there are patches > for ext3 on 2.4.20. Given there is a new release of IPCop in the pipeline, > is it too late to get them included, assuming they aren't already? I don't > think I can do this on a vanilla install myself ... > > http://www.zip.com.au/~akpm/linux/ext3/ > > apologies if it's all in hand :) > Some of them (if not all) are include in standard 2.4.21 kernel used for V1.3.1 http://www.kernel.org/pub/linux/kernel/v2.4/ChangeLog-2.4.21 |
|
From: Harry G. <ha...@hg...> - 2003-07-30 03:09:46
|
At 10:27 PM +0200 7/29/03, Serge van Ginderachter (svgn) wrote: >For your info.... I have a RH7.3 box auto-updating with apt4rpm >(<http://ayo.freshrpms.net>http://ayo.freshrpms.net >redhat/7.3/i386). SSHD crashes since this update last night. I'll >have to look into it from the console... I've got a 7.3 system updating using autoupdate. I updated last night and haven't had a problem. Just tried again for a sanity check. Harry |
|
From: Serge v. G. (svgn) <ser...@or...> - 2003-07-29 20:29:05
|
For your info.... I have a RH7.3 box auto-updating with apt4rpm (http://ayo.freshrpms.net redhat/7.3/i386). SSHD crashes since this update last night. I'll have to look into it from the console... -----Original Message----- From: John Edwards [mailto:sh...@co...] Sent: dinsdag 29 juli 2003 21:57 To: ipc...@li... Subject: [IPCop-devel] [RHSA-2003:222-01] Updated openssh packages available Hi Minor security bug in RedHat's OpenSSH, which allows the some information on valid usernames to leak: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --------------------------------------------------------------------- Red Hat Security Advisory Synopsis: Updated openssh packages available Advisory ID: RHSA-2003:222-01 Issue date: 2003-07-29 Updated on: 2003-07-29 Product: Red Hat Linux Keywords: openssh pam timing information leak Cross references: Obsoletes: RHSA-2002:127 CVE Names: CAN-2003-0190 - --------------------------------------------------------------------- 1. Topic: Updated OpenSSH packages are now available. These updates close an information leak caused by sshd's interaction with the PAM system. 2. Relevant releases/architectures: Red Hat Linux 7.1 - i386 Red Hat Linux 7.1 for iSeries (64 bit) - ppc Red Hat Linux 7.1 for pSeries (64 bit) - ppc Red Hat Linux 7.2 - i386, ia64 Red Hat Linux 7.3 - i386 Red Hat Linux 8.0 - i386 Red Hat Linux 9 - i386 3. Problem description: OpenSSH is a suite of network connectivity tools that can be used to establish encrypted connections between systems on a network and can provide interactive login sessions and port forwarding, among other functions. When configured to allow password-based or challenge-response authentication, sshd (the OpenSSH server) uses PAM (Pluggable Authentication Modules) to verify the user's password. Under certain conditions, OpenSSH versions prior to 3.6.1p1 reject an invalid authentication attempt without first attempting authentication using PAM. If PAM is configured with its default failure delay, the amount of time sshd takes to reject an invalid authentication request varies widely enough that the timing variations could be used to deduce whether or not an account with a specified name existed on the server. This information could then be used to narrow the focus of an attack against some other system component. These updates contain backported fixes that cause sshd to always attempt PAM authentication when performing password and challenge-response authentication for clients. 4. Solution: Before applying this update, make sure all previously released errata relevant to your system have been applied. To update all RPMs for your particular architecture, run: rpm -Fvh [filenames] where [filenames] is a list of the RPMs you wish to upgrade. Only those RPMs which are currently installed will be updated. Those RPMs which are not installed but included in the list will not be updated. Note that you can also use wildcards (*.rpm) if your current directory *only* contains the desired RPMs. Please note that this update is also available via Red Hat Network. Many people find this an easier way to apply updates. To use Red Hat Network, launch the Red Hat Update Agent with the following command: up2date This will start an interactive process that will result in the appropriate RPMs being upgraded on your system. 5. RPMs required: Red Hat Linux 7.1: SRPMS: ftp://updates.redhat.com/7.1/en/os/SRPMS/openssh-3.1p1-7.src.rpm i386: ftp://updates.redhat.com/7.1/en/os/i386/openssh-3.1p1-7.i386.rpm ftp://updates.redhat.com/7.1/en/os/i386/openssh-clients-3.1p1-7.i386.rpm ftp://updates.redhat.com/7.1/en/os/i386/openssh-server-3.1p1-7.i386.rpm ftp://updates.redhat.com/7.1/en/os/i386/openssh-askpass-3.1p1-7.i386.rpm ftp://updates.redhat.com/7.1/en/os/i386/openssh-askpass-gnome-3.1p1-7.i386.r pm Red Hat Linux 7.1 for iSeries (64 bit): SRPMS: ftp://updates.redhat.com/7.1/en/os/iSeries/SRPMS/openssh-3.1p1-7.src.rpm ppc: ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-3.1p1-7.ppc.rpm ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-clients-3.1p1-7.ppc.r pm ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-server-3.1p1-7.ppc.rp m ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-askpass-3.1p1-7.ppc.r pm ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-askpass-gnome-3.1p1-7 .ppc.rpm Red Hat Linux 7.1 for pSeries (64 bit): SRPMS: ftp://updates.redhat.com/7.1/en/os/pSeries/SRPMS/openssh-3.1p1-7.src.rpm ppc: ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-3.1p1-7.ppc.rpm ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-clients-3.1p1-7.ppc.r pm ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-server-3.1p1-7.ppc.rp m ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-askpass-3.1p1-7.ppc.r pm ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-askpass-gnome-3.1p1-7 .ppc.rpm Red Hat Linux 7.2: SRPMS: ftp://updates.redhat.com/7.2/en/os/SRPMS/openssh-3.1p1-8.src.rpm i386: ftp://updates.redhat.com/7.2/en/os/i386/openssh-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.2/en/os/i386/openssh-clients-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.2/en/os/i386/openssh-server-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.2/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.2/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.r pm ia64: ftp://updates.redhat.com/7.2/en/os/ia64/openssh-3.1p1-8.ia64.rpm ftp://updates.redhat.com/7.2/en/os/ia64/openssh-clients-3.1p1-8.ia64.rpm ftp://updates.redhat.com/7.2/en/os/ia64/openssh-server-3.1p1-8.ia64.rpm ftp://updates.redhat.com/7.2/en/os/ia64/openssh-askpass-3.1p1-8.ia64.rpm ftp://updates.redhat.com/7.2/en/os/ia64/openssh-askpass-gnome-3.1p1-8.ia64.r pm Red Hat Linux 7.3: SRPMS: ftp://updates.redhat.com/7.3/en/os/SRPMS/openssh-3.1p1-8.src.rpm i386: ftp://updates.redhat.com/7.3/en/os/i386/openssh-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.3/en/os/i386/openssh-clients-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.3/en/os/i386/openssh-server-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.3/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm ftp://updates.redhat.com/7.3/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.r pm Red Hat Linux 8.0: SRPMS: ftp://updates.redhat.com/8.0/en/os/SRPMS/openssh-3.4p1-4.src.rpm i386: ftp://updates.redhat.com/8.0/en/os/i386/openssh-3.4p1-4.i386.rpm ftp://updates.redhat.com/8.0/en/os/i386/openssh-clients-3.4p1-4.i386.rpm ftp://updates.redhat.com/8.0/en/os/i386/openssh-server-3.4p1-4.i386.rpm ftp://updates.redhat.com/8.0/en/os/i386/openssh-askpass-3.4p1-4.i386.rpm ftp://updates.redhat.com/8.0/en/os/i386/openssh-askpass-gnome-3.4p1-4.i386.r pm Red Hat Linux 9: SRPMS: ftp://updates.redhat.com/9/en/os/SRPMS/openssh-3.5p1-6.9.src.rpm i386: ftp://updates.redhat.com/9/en/os/i386/openssh-3.5p1-6.9.i386.rpm ftp://updates.redhat.com/9/en/os/i386/openssh-clients-3.5p1-6.9.i386.rpm ftp://updates.redhat.com/9/en/os/i386/openssh-server-3.5p1-6.9.i386.rpm ftp://updates.redhat.com/9/en/os/i386/openssh-askpass-3.5p1-6.9.i386.rpm ftp://updates.redhat.com/9/en/os/i386/openssh-askpass-gnome-3.5p1-6.9.i386.r pm 6. Verification: MD5 sum Package Name - -------------------------------------------------------------------------- bfbd152a2069230041ff1298b0562061 7.1/en/os/SRPMS/openssh-3.1p1-7.src.rpm 48c37500a4c7984673878edbef7e9cde 7.1/en/os/i386/openssh-3.1p1-7.i386.rpm 3f59bffd703bac24632f4e34e2beed22 7.1/en/os/i386/openssh-askpass-3.1p1-7.i386.rpm def478c5b3f97af908e3cb4d8306662b 7.1/en/os/i386/openssh-askpass-gnome-3.1p1-7.i386.rpm e9947146ea766572cbd9457f320a4f06 7.1/en/os/i386/openssh-clients-3.1p1-7.i386.rpm 879cbb50923935cebf20b39578dc8eed 7.1/en/os/i386/openssh-server-3.1p1-7.i386.rpm bfbd152a2069230041ff1298b0562061 7.1/en/os/iSeries/SRPMS/openssh-3.1p1-7.src.rpm 7c8aa13e79e6c856181852de76c86722 7.1/en/os/iSeries/ppc/openssh-3.1p1-7.ppc.rpm b1a591c23d345fd96f2d0fab2eb958be 7.1/en/os/iSeries/ppc/openssh-askpass-3.1p1-7.ppc.rpm ae6d48792fea701e75b114333babe37c 7.1/en/os/iSeries/ppc/openssh-askpass-gnome-3.1p1-7.ppc.rpm f7ee0ce5cefe22043828863da06ce331 7.1/en/os/iSeries/ppc/openssh-clients-3.1p1-7.ppc.rpm d9f993c8fa47ec3956f5e1e3c6f176d5 7.1/en/os/iSeries/ppc/openssh-server-3.1p1-7.ppc.rpm bfbd152a2069230041ff1298b0562061 7.1/en/os/pSeries/SRPMS/openssh-3.1p1-7.src.rpm 7c8aa13e79e6c856181852de76c86722 7.1/en/os/pSeries/ppc/openssh-3.1p1-7.ppc.rpm b1a591c23d345fd96f2d0fab2eb958be 7.1/en/os/pSeries/ppc/openssh-askpass-3.1p1-7.ppc.rpm ae6d48792fea701e75b114333babe37c 7.1/en/os/pSeries/ppc/openssh-askpass-gnome-3.1p1-7.ppc.rpm f7ee0ce5cefe22043828863da06ce331 7.1/en/os/pSeries/ppc/openssh-clients-3.1p1-7.ppc.rpm d9f993c8fa47ec3956f5e1e3c6f176d5 7.1/en/os/pSeries/ppc/openssh-server-3.1p1-7.ppc.rpm 22f17a835f12a4131a21487d5ee3dec6 7.2/en/os/SRPMS/openssh-3.1p1-8.src.rpm 013694ec0e839f077e7980d9cebfa277 7.2/en/os/i386/openssh-3.1p1-8.i386.rpm a942a051510a5a0aa34b0774d6eb8ee0 7.2/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm de35a67fa21ec478aff57ce5c830f84e 7.2/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.rpm 8c9d37f46f76093eccea80571d687d46 7.2/en/os/i386/openssh-clients-3.1p1-8.i386.rpm 42ec08d8633862da9c988524fecdafbb 7.2/en/os/i386/openssh-server-3.1p1-8.i386.rpm d9441bbe925832b82766b8140fb4bb77 7.2/en/os/ia64/openssh-3.1p1-8.ia64.rpm 58765b526317e03dcf9371d9b225fa68 7.2/en/os/ia64/openssh-askpass-3.1p1-8.ia64.rpm 46b8de0e5072ff7ee614c7e5dfc536b9 7.2/en/os/ia64/openssh-askpass-gnome-3.1p1-8.ia64.rpm 1e95e8ca735b971bcb1a1824becaa582 7.2/en/os/ia64/openssh-clients-3.1p1-8.ia64.rpm 8ae51f6f0116f60fd29545b4f9560613 7.2/en/os/ia64/openssh-server-3.1p1-8.ia64.rpm 22f17a835f12a4131a21487d5ee3dec6 7.3/en/os/SRPMS/openssh-3.1p1-8.src.rpm 013694ec0e839f077e7980d9cebfa277 7.3/en/os/i386/openssh-3.1p1-8.i386.rpm a942a051510a5a0aa34b0774d6eb8ee0 7.3/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm de35a67fa21ec478aff57ce5c830f84e 7.3/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.rpm 8c9d37f46f76093eccea80571d687d46 7.3/en/os/i386/openssh-clients-3.1p1-8.i386.rpm 42ec08d8633862da9c988524fecdafbb 7.3/en/os/i386/openssh-server-3.1p1-8.i386.rpm 81ed2140e12f15e4518fc2fe3aef10eb 8.0/en/os/SRPMS/openssh-3.4p1-4.src.rpm d625e5b2eca982b5b92ac0862eae1b73 8.0/en/os/i386/openssh-3.4p1-4.i386.rpm 34e91b60c3b5296c8e5185d5cf832013 8.0/en/os/i386/openssh-askpass-3.4p1-4.i386.rpm 536394cfe9c2b3068580269b346f6c1f 8.0/en/os/i386/openssh-askpass-gnome-3.4p1-4.i386.rpm ce583ee467532c9af9b9482cc90cd375 8.0/en/os/i386/openssh-clients-3.4p1-4.i386.rpm a81ee000ffc59c3f210fb4f08a02f2a7 8.0/en/os/i386/openssh-server-3.4p1-4.i386.rpm 321f50363605e1976cc19b7ceacf6d26 9/en/os/SRPMS/openssh-3.5p1-6.9.src.rpm 71613a13c1e40faa16f9a01fabf0e8b3 9/en/os/i386/openssh-3.5p1-6.9.i386.rpm 7b70f6b671b87385646d382115974724 9/en/os/i386/openssh-askpass-3.5p1-6.9.i386.rpm 9a8d60a683b055feba9855db74467fff 9/en/os/i386/openssh-askpass-gnome-3.5p1-6.9.i386.rpm 5c18b658c8bed7c434d8d9f142a95e7f 9/en/os/i386/openssh-clients-3.5p1-6.9.i386.rpm 3971445a5ee73f5c8b7fdc022b0432e8 9/en/os/i386/openssh-server-3.5p1-6.9.i386.rpm These packages are GPG signed by Red Hat for security. Our key is available from http://www.redhat.com/security/keys.html You can verify each package with the following command: rpm --checksig -v <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: md5sum <filename> 7. References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0190 8. Contact: The Red Hat security contact is <sec...@re...>. More contact details at http://www.redhat.com/solutions/security/news/contact.html Copyright 2003 Red Hat, Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD4DBQE/JqtfXlSAg2UNWIIRArN1AJj2J4983TGK0tX2JtuvVnRMan4PAJ9+aGuz eCjkS4HgrwVgCiekk+e+zg== =8jD6 -----END PGP SIGNATURE----- ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ IPCop-devel mailing list IPC...@li... https://lists.sourceforge.net/lists/listinfo/ipcop-devel |
|
From: John E. <sh...@co...> - 2003-07-29 20:11:50
|
Hi
Minor security bug in RedHat's OpenSSH, which allows the some
information on valid usernames to leak:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- ---------------------------------------------------------------------
Red Hat Security Advisory
Synopsis: Updated openssh packages available
Advisory ID: RHSA-2003:222-01
Issue date: 2003-07-29
Updated on: 2003-07-29
Product: Red Hat Linux
Keywords: openssh pam timing information leak
Cross references:
Obsoletes: RHSA-2002:127
CVE Names: CAN-2003-0190
- ---------------------------------------------------------------------
1. Topic:
Updated OpenSSH packages are now available. These updates close an
information leak caused by sshd's interaction with the PAM system.
2. Relevant releases/architectures:
Red Hat Linux 7.1 - i386
Red Hat Linux 7.1 for iSeries (64 bit) - ppc
Red Hat Linux 7.1 for pSeries (64 bit) - ppc
Red Hat Linux 7.2 - i386, ia64
Red Hat Linux 7.3 - i386
Red Hat Linux 8.0 - i386
Red Hat Linux 9 - i386
3. Problem description:
OpenSSH is a suite of network connectivity tools that can be used to
establish encrypted connections between systems on a network and can
provide interactive login sessions and port forwarding, among other functions.
When configured to allow password-based or challenge-response
authentication, sshd (the OpenSSH server) uses PAM (Pluggable
Authentication Modules) to verify the user's password. Under certain
conditions, OpenSSH versions prior to 3.6.1p1 reject an invalid
authentication attempt without first attempting authentication using PAM.
If PAM is configured with its default failure delay, the amount of time
sshd takes to reject an invalid authentication request varies widely enough
that the timing variations could be used to deduce whether or not an
account with a specified name existed on the server. This information
could then be used to narrow the focus of an attack against some other
system component.
These updates contain backported fixes that cause sshd to always attempt
PAM authentication when performing password and challenge-response
authentication for clients.
4. Solution:
Before applying this update, make sure all previously released errata
relevant to your system have been applied.
To update all RPMs for your particular architecture, run:
rpm -Fvh [filenames]
where [filenames] is a list of the RPMs you wish to upgrade. Only those
RPMs which are currently installed will be updated. Those RPMs which are
not installed but included in the list will not be updated. Note that you
can also use wildcards (*.rpm) if your current directory *only* contains the
desired RPMs.
Please note that this update is also available via Red Hat Network. Many
people find this an easier way to apply updates. To use Red Hat Network,
launch the Red Hat Update Agent with the following command:
up2date
This will start an interactive process that will result in the appropriate
RPMs being upgraded on your system.
5. RPMs required:
Red Hat Linux 7.1:
SRPMS:
ftp://updates.redhat.com/7.1/en/os/SRPMS/openssh-3.1p1-7.src.rpm
i386:
ftp://updates.redhat.com/7.1/en/os/i386/openssh-3.1p1-7.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/openssh-clients-3.1p1-7.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/openssh-server-3.1p1-7.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/openssh-askpass-3.1p1-7.i386.rpm
ftp://updates.redhat.com/7.1/en/os/i386/openssh-askpass-gnome-3.1p1-7.i386.rpm
Red Hat Linux 7.1 for iSeries (64 bit):
SRPMS:
ftp://updates.redhat.com/7.1/en/os/iSeries/SRPMS/openssh-3.1p1-7.src.rpm
ppc:
ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-clients-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-server-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-askpass-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/iSeries/ppc/openssh-askpass-gnome-3.1p1-7.ppc.rpm
Red Hat Linux 7.1 for pSeries (64 bit):
SRPMS:
ftp://updates.redhat.com/7.1/en/os/pSeries/SRPMS/openssh-3.1p1-7.src.rpm
ppc:
ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-clients-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-server-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-askpass-3.1p1-7.ppc.rpm
ftp://updates.redhat.com/7.1/en/os/pSeries/ppc/openssh-askpass-gnome-3.1p1-7.ppc.rpm
Red Hat Linux 7.2:
SRPMS:
ftp://updates.redhat.com/7.2/en/os/SRPMS/openssh-3.1p1-8.src.rpm
i386:
ftp://updates.redhat.com/7.2/en/os/i386/openssh-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/openssh-clients-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/openssh-server-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.rpm
ia64:
ftp://updates.redhat.com/7.2/en/os/ia64/openssh-3.1p1-8.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/openssh-clients-3.1p1-8.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/openssh-server-3.1p1-8.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/openssh-askpass-3.1p1-8.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/openssh-askpass-gnome-3.1p1-8.ia64.rpm
Red Hat Linux 7.3:
SRPMS:
ftp://updates.redhat.com/7.3/en/os/SRPMS/openssh-3.1p1-8.src.rpm
i386:
ftp://updates.redhat.com/7.3/en/os/i386/openssh-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/openssh-clients-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/openssh-server-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.rpm
Red Hat Linux 8.0:
SRPMS:
ftp://updates.redhat.com/8.0/en/os/SRPMS/openssh-3.4p1-4.src.rpm
i386:
ftp://updates.redhat.com/8.0/en/os/i386/openssh-3.4p1-4.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/openssh-clients-3.4p1-4.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/openssh-server-3.4p1-4.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/openssh-askpass-3.4p1-4.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/openssh-askpass-gnome-3.4p1-4.i386.rpm
Red Hat Linux 9:
SRPMS:
ftp://updates.redhat.com/9/en/os/SRPMS/openssh-3.5p1-6.9.src.rpm
i386:
ftp://updates.redhat.com/9/en/os/i386/openssh-3.5p1-6.9.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/openssh-clients-3.5p1-6.9.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/openssh-server-3.5p1-6.9.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/openssh-askpass-3.5p1-6.9.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/openssh-askpass-gnome-3.5p1-6.9.i386.rpm
6. Verification:
MD5 sum Package Name
- --------------------------------------------------------------------------
bfbd152a2069230041ff1298b0562061 7.1/en/os/SRPMS/openssh-3.1p1-7.src.rpm
48c37500a4c7984673878edbef7e9cde 7.1/en/os/i386/openssh-3.1p1-7.i386.rpm
3f59bffd703bac24632f4e34e2beed22 7.1/en/os/i386/openssh-askpass-3.1p1-7.i386.rpm
def478c5b3f97af908e3cb4d8306662b 7.1/en/os/i386/openssh-askpass-gnome-3.1p1-7.i386.rpm
e9947146ea766572cbd9457f320a4f06 7.1/en/os/i386/openssh-clients-3.1p1-7.i386.rpm
879cbb50923935cebf20b39578dc8eed 7.1/en/os/i386/openssh-server-3.1p1-7.i386.rpm
bfbd152a2069230041ff1298b0562061 7.1/en/os/iSeries/SRPMS/openssh-3.1p1-7.src.rpm
7c8aa13e79e6c856181852de76c86722 7.1/en/os/iSeries/ppc/openssh-3.1p1-7.ppc.rpm
b1a591c23d345fd96f2d0fab2eb958be 7.1/en/os/iSeries/ppc/openssh-askpass-3.1p1-7.ppc.rpm
ae6d48792fea701e75b114333babe37c 7.1/en/os/iSeries/ppc/openssh-askpass-gnome-3.1p1-7.ppc.rpm
f7ee0ce5cefe22043828863da06ce331 7.1/en/os/iSeries/ppc/openssh-clients-3.1p1-7.ppc.rpm
d9f993c8fa47ec3956f5e1e3c6f176d5 7.1/en/os/iSeries/ppc/openssh-server-3.1p1-7.ppc.rpm
bfbd152a2069230041ff1298b0562061 7.1/en/os/pSeries/SRPMS/openssh-3.1p1-7.src.rpm
7c8aa13e79e6c856181852de76c86722 7.1/en/os/pSeries/ppc/openssh-3.1p1-7.ppc.rpm
b1a591c23d345fd96f2d0fab2eb958be 7.1/en/os/pSeries/ppc/openssh-askpass-3.1p1-7.ppc.rpm
ae6d48792fea701e75b114333babe37c 7.1/en/os/pSeries/ppc/openssh-askpass-gnome-3.1p1-7.ppc.rpm
f7ee0ce5cefe22043828863da06ce331 7.1/en/os/pSeries/ppc/openssh-clients-3.1p1-7.ppc.rpm
d9f993c8fa47ec3956f5e1e3c6f176d5 7.1/en/os/pSeries/ppc/openssh-server-3.1p1-7.ppc.rpm
22f17a835f12a4131a21487d5ee3dec6 7.2/en/os/SRPMS/openssh-3.1p1-8.src.rpm
013694ec0e839f077e7980d9cebfa277 7.2/en/os/i386/openssh-3.1p1-8.i386.rpm
a942a051510a5a0aa34b0774d6eb8ee0 7.2/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm
de35a67fa21ec478aff57ce5c830f84e 7.2/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.rpm
8c9d37f46f76093eccea80571d687d46 7.2/en/os/i386/openssh-clients-3.1p1-8.i386.rpm
42ec08d8633862da9c988524fecdafbb 7.2/en/os/i386/openssh-server-3.1p1-8.i386.rpm
d9441bbe925832b82766b8140fb4bb77 7.2/en/os/ia64/openssh-3.1p1-8.ia64.rpm
58765b526317e03dcf9371d9b225fa68 7.2/en/os/ia64/openssh-askpass-3.1p1-8.ia64.rpm
46b8de0e5072ff7ee614c7e5dfc536b9 7.2/en/os/ia64/openssh-askpass-gnome-3.1p1-8.ia64.rpm
1e95e8ca735b971bcb1a1824becaa582 7.2/en/os/ia64/openssh-clients-3.1p1-8.ia64.rpm
8ae51f6f0116f60fd29545b4f9560613 7.2/en/os/ia64/openssh-server-3.1p1-8.ia64.rpm
22f17a835f12a4131a21487d5ee3dec6 7.3/en/os/SRPMS/openssh-3.1p1-8.src.rpm
013694ec0e839f077e7980d9cebfa277 7.3/en/os/i386/openssh-3.1p1-8.i386.rpm
a942a051510a5a0aa34b0774d6eb8ee0 7.3/en/os/i386/openssh-askpass-3.1p1-8.i386.rpm
de35a67fa21ec478aff57ce5c830f84e 7.3/en/os/i386/openssh-askpass-gnome-3.1p1-8.i386.rpm
8c9d37f46f76093eccea80571d687d46 7.3/en/os/i386/openssh-clients-3.1p1-8.i386.rpm
42ec08d8633862da9c988524fecdafbb 7.3/en/os/i386/openssh-server-3.1p1-8.i386.rpm
81ed2140e12f15e4518fc2fe3aef10eb 8.0/en/os/SRPMS/openssh-3.4p1-4.src.rpm
d625e5b2eca982b5b92ac0862eae1b73 8.0/en/os/i386/openssh-3.4p1-4.i386.rpm
34e91b60c3b5296c8e5185d5cf832013 8.0/en/os/i386/openssh-askpass-3.4p1-4.i386.rpm
536394cfe9c2b3068580269b346f6c1f 8.0/en/os/i386/openssh-askpass-gnome-3.4p1-4.i386.rpm
ce583ee467532c9af9b9482cc90cd375 8.0/en/os/i386/openssh-clients-3.4p1-4.i386.rpm
a81ee000ffc59c3f210fb4f08a02f2a7 8.0/en/os/i386/openssh-server-3.4p1-4.i386.rpm
321f50363605e1976cc19b7ceacf6d26 9/en/os/SRPMS/openssh-3.5p1-6.9.src.rpm
71613a13c1e40faa16f9a01fabf0e8b3 9/en/os/i386/openssh-3.5p1-6.9.i386.rpm
7b70f6b671b87385646d382115974724 9/en/os/i386/openssh-askpass-3.5p1-6.9.i386.rpm
9a8d60a683b055feba9855db74467fff 9/en/os/i386/openssh-askpass-gnome-3.5p1-6.9.i386.rpm
5c18b658c8bed7c434d8d9f142a95e7f 9/en/os/i386/openssh-clients-3.5p1-6.9.i386.rpm
3971445a5ee73f5c8b7fdc022b0432e8 9/en/os/i386/openssh-server-3.5p1-6.9.i386.rpm
These packages are GPG signed by Red Hat for security. Our key is
available from http://www.redhat.com/security/keys.html
You can verify each package with the following command:
rpm --checksig -v <filename>
If you only wish to verify that each package has not been corrupted or
tampered with, examine only the md5sum with the following command:
md5sum <filename>
7. References:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0190
8. Contact:
The Red Hat security contact is <sec...@re...>. More contact
details at http://www.redhat.com/solutions/security/news/contact.html
Copyright 2003 Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
iD4DBQE/JqtfXlSAg2UNWIIRArN1AJj2J4983TGK0tX2JtuvVnRMan4PAJ9+aGuz
eCjkS4HgrwVgCiekk+e+zg==
=8jD6
-----END PGP SIGNATURE-----
|
|
From: Murray <mu...@mi...> - 2003-07-29 19:09:44
|
at the risk of cross posting... I've had some troubles with crashes & thanks to ipcop-user@ got as far as suspecting ext3 (and/or a bad disk). http://marc.theaimsgroup.com/?t=105924415300001&r=1&w=2 this is all a little bit beyond me in truth, but it seems there are patches for ext3 on 2.4.20. Given there is a new release of IPCop in the pipeline, is it too late to get them included, assuming they aren't already? I don't think I can do this on a vanilla install myself ... http://www.zip.com.au/~akpm/linux/ext3/ apologies if it's all in hand :) |
|
From: <ja...@gu...> - 2003-07-28 01:12:53
|
Guys - this is not needed. Now for dual boot or other issues... Get VMWARE and load and a linux under it. You can even test IPCop in that play space. Also VMWARE gets rid of the motherboard and harddrive issues, because your Os hands that - that fakes it to the next one. You can get test drive for thirty days - just go to their website. Jackb On 27 Jul 2003 at 15:45, Baud1200 wrote: > "But don't tell me you've put those 3 disks in some _idiot_ raid-0 > setup with no backup. ;-)" > > Apparently raid-o is useless now too according to you?. I have plenty > of backup, that's what CDRW's are for. > > "..if your disks uses ntfs, you will wanna repartition from wintendo, > else, do the fdisk work from dsl, " > > LOL, so basically rip apart my workstation and reinstall my OS.. great > advice.. thx. > > Wouldn't worry about it, there were actually some users that took the > time to email me privately with a working link to a compiled version, > rather than debate with me as to why I should compile it myself. > > FYI, 1.3.1A4 is more stable on my firewall than some of the previous > versions that WERE posted as compiled ISO's, both alpha or beta! > > I see no reason to continue this post further, there is no point in > more flame posts on this forum. > > > > > > > ------------------------------------------------------- > This SF.Net email sponsored by: Free pre-built ASP.NET sites including > Data Reports, E-commerce, Portals, and Forums are available now. > Download today and enter to win an XBOX or Visual Studio .NET. > http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_ > 01/01 _______________________________________________ IPCop-devel > mailing list IPC...@li... > https://lists.sourceforge.net/lists/listinfo/ipcop-devel > |
|
From: Arnt K. <ar...@c2...> - 2003-07-28 00:01:03
|
On Sun, 27 Jul 2003 15:45:08 -0600, Baud1200 <bau...@sh...> wrote in message <0HIP00E97DHB68@l-daemon>: > "But don't tell me you've put those 3 disks in some _idiot_ raid-0 > setup with no backup. ;-)" > > Apparently raid-o is useless now too according to you?. I have plenty > of backup, that's what CDRW's are for. ..cooked raid-0 without backups, _are_ useless. ;-) ..with backup, you're home free, apart from the wee fees. ;-) > "..if your disks uses ntfs, you will wanna repartition from wintendo, > else, do the fdisk work from dsl, " > > LOL, so basically rip apart my workstation and reinstall my OS.. great > advice.. thx. .."reinstall"???, are you telling me you cannot make space on your raid-0 disks at all, from wintendo??? > Wouldn't worry about it, there were actually some users that took the > time to email me privately with a working link to a compiled version, > rather than debate with me as to why I should compile it myself. ..excellent, buys us guineapig time much quicker. ;-) > FYI, 1.3.1A4 is more stable on my firewall than some of the previous ..these are non-wireless 1.3.1alpha4 iso's? Urls? (Preferrably to the build source snapshots/tarballs, I'd like to diff them to see what tricks Mattias threw in.) > versions that WERE posted as compiled ISO's, both alpha or beta! ..advice of you opinion when you have enough data to compare with the official 1.3.0. > I see no reason to continue this post further, there is no point in > more flame posts on this forum. .. ;-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. |
|
From: Baud1200 <bau...@sh...> - 2003-07-27 21:39:13
|
"But don't tell me you've put those 3 disks in some _idiot_ raid-0 setup with no backup. ;-)" Apparently raid-o is useless now too according to you?. I have plenty of backup, that's what CDRW's are for. "..if your disks uses ntfs, you will wanna repartition from wintendo, else, do the fdisk work from dsl, " LOL, so basically rip apart my workstation and reinstall my OS.. great advice.. thx. Wouldn't worry about it, there were actually some users that took the time to email me privately with a working link to a compiled version, rather than debate with me as to why I should compile it myself. FYI, 1.3.1A4 is more stable on my firewall than some of the previous versions that WERE posted as compiled ISO's, both alpha or beta! I see no reason to continue this post further, there is no point in more flame posts on this forum. |
|
From: Arnt K. <ar...@c2...> - 2003-07-27 20:32:57
|
On Sun, 27 Jul 2003 12:58:57 -0600, Baud1200 <bau...@sh...> wrote in message <0HIP00M4D5SDLU@l-daemon>: > "..if it runs wintendo _and_ Office, it has enough omph > to chew cvs code, so grab space and dual-boot it. ;-) > ..no excuses," > > > Ok Arnt, Great then, can you explain to me how you would go about > getting this procedure to work on a Soyo K7V Dragon+ Mobo with a > modded RAID BIOS? It runs on 3 HD's in a RAID config, and I don't have > the room in the case, or cash for another single HD ATM. Can it still > "chew cvs code"? ..oh yeah, you've got _plenty_ omph. It can boot any of the 3 disks, floppy, cdrom and over lan, so _no_ problem. But don't tell me you've put those 3 disks in some _idiot_ raid-0 setup with no backup. ;-) ..if your disks uses ntfs, you will wanna repartition from wintendo, else, do the fdisk work from dsl, see its wee install docs in /root. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. |
|
From: Alan H. <al...@fa...> - 2003-07-27 19:38:12
|
On Wed, Jul 23, 2003 at 03:42:45PM +0100, Dave Roberts wrote: > I also think it would make more sense to include the blue interface as a > selection in the Network configuration type section of the setup program > rather than a separate option on the main setup menu. I do realise that > this would involve a considerable amount of rewriting to allow orange > and blue to be selected with toggles/checkboxes. The way the code works for the network interface configuration isn't very intuitive. And it makes sense to break it out as eventually I hope to add real wireless card support to IPcop rather than just relying on an ethernet card + access point to do it. > The other thing I want to ask about. What's involved in putting a > 802.11a/b/g wireless NIC actually in the IPCop machine? Is this > currently supported with this blue interface? Not yet. But it will be. I've just got tied up a bit at the moment, but hope to be able to spend some time fixing up IPcop soon. The intention is to support both IPSEC and CIPE over wireless links. CIPE is much much easier to setup as a VPN connection, and CIPE is available for Windows too. Alan. |
|
From: Baud1200 <bau...@sh...> - 2003-07-27 18:53:02
|
"..if it runs wintendo _and_ Office, it has enough omph to chew cvs code, so grab space and dual-boot it. ;-) ..no excuses," Ok Arnt, Great then, can you explain to me how you would go about getting this procedure to work on a Soyo K7V Dragon+ Mobo with a modded RAID BIOS? It runs on 3 HD's in a RAID config, and I don't have the room in the case, or cash for another single HD ATM. Can it still "chew cvs code"? |
|
From: Arnt K. <ar...@c2...> - 2003-07-27 17:48:49
|
On Sun, 27 Jul 2003 09:35:50 -0600, Baud1200 <bau...@sh...> wrote in message <0HIO007CPWDUPY@l-daemon>: > > Is there something in the CVS that you specifically need?" Phill, > thanks for one of the few genuine responses. > I am unable to build the CVS because I don not have the sufficient > hardware ..bull, recognise this header line? "X-Mailer: Microsoft Office Outlook, Build 11.0.5329" ..if it runs wintendo _and_ Office, it has enough omph to chew cvs code, so grab space and dual-boot it. ;-) ..no excuses, get http://damnsmalllinux.org/ , install onto hard disk as needed, give it a Gig of ext3fs, then 'apt-get update' and 'apt-get upgrade', when done, 'apt-get install cvs' etc whatever else you need. ..dsl also provides a _nice_ wee web server to install ipcop. ;-) > to do so, not because I can't follow the directions on how to do it. > I was looking for improved purple interface support for one though; > and hoping for an added 2'nd red interface; not to mention my previous > snort issues which seem to have gone ignored. > > In closing, if I really didn't like IPCop, or care what happened to > it, I would not be taking the time to post here in hopes of making > some improvement to either the product itself, or to contribute to the > fashion it is developed in. Of course I like the software... I just > want to see at its fullest potential, like almost everyone else here. > > As I write this.. WOW THX.. someone (Arnt) actually posted an external > link after a load of flames.. THANK YOU ..you've set up dual booting 'n cvs now? ;-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. |
|
From: Eric O. <er...@ob...> - 2003-07-27 16:44:46
|
on 27/7/03 4:35 pm, Baud1200 at bau...@sh... wrote: > My hope by posting this was for someone who understands what I have written, > having compiled the ISO themselves, will post or email me an external link > to it where it can be downloaded. I'll burn you an iso of 1.3.1alpha4 from the latest CVS, and post it to if you like, but I'll warn you that I'm unable to build isos with ECI ADSL support or traffic graphs that work, due to some limitations of my build system. I'm sorry, I don't have a broadband connection, or access to a suitable ftp space, to make it available quickly online. Please note that due to development/changes to the language files, the only language available for the install in 1.3.1alpha is English. But, you can change it to another language from the webgui once you've installed it. This will be addressed when development moves to beta testing. Let me know off list if you are interested. Might take a while to get to you though... Eric |
|
From: Baud1200 <bau...@sh...> - 2003-07-27 15:29:55
|
"Making demands as you have sours the enjoyment and is counter-productive." It "sours my enjoyment" to have users flame a post asking for access to current technology; while no one at all has comments on technical posts I have made. http://marc.theaimsgroup.com/?l=ipcop-devel&m=105805279206926&w=2 Funny, as a lot of ppl using IPCop now are using it due to this sort of behavior associated with another Linux firewall project. My hope by posting this was for someone who understands what I have written, having compiled the ISO themselves, will post or email me an external link to it where it can be downloaded. For constructive criticism... what is the point of starting something if you will not finish it. ie. Why put ANY alpha versions on sourceforce if you do not intend to continue doing this with all of them, buggy or not. When I downloaded and installed the IPcop 1.3.1A2 ISO, it gave an error and terminated the install after only a few moments, did I complain, NO. I knew it was an alpha version and still in development, and I knew I could count on an updated alpha version being posted to the web within 1/2 a month judging by the time in between the previous uploaded ISO's. Isn't the point of alpha and beta releases so that people who would actually use the software will install it on their machines in a collaborated effort to find bugs and new issues in the software. I guess some seem to think this can be done better with only a few people. Imagine if MS with over 10k beta testers can release a buggy version of Windows, what a software with even less public testers can do. Is there something in the CVS that you specifically need?" Phill, thanks for one of the few genuine responses. I am unable to build the CVS because I don not have the sufficient hardware to do so, not because I can't follow the directions on how to do it. I was looking for improved purple interface support for one though; and hoping for an added 2'nd red interface; not to mention my previous snort issues which seem to have gone ignored. In closing, if I really didn't like IPCop, or care what happened to it, I would not be taking the time to post here in hopes of making some improvement to either the product itself, or to contribute to the fashion it is developed in. Of course I like the software... I just want to see at its fullest potential, like almost everyone else here. As I write this.. WOW THX.. someone (Arnt) actually posted an external link after a load of flames.. THANK YOU Baud1200 |
|
From: Arnt K. <ar...@c2...> - 2003-07-27 15:14:40
|
On Sat, 26 Jul 2003 13:40:40 -0600, Baud1200 <bau...@sh...> wrote in message <0HIN0076ED1S73@l-daemon>: > Ouch. still no precompiled build since IPcop 1.3.1 Alpha 3. ..no? Try http://www.sys-thema.com/ipcop-1.3.1alpha4-wireless.iso , Mattia can use more guineapigs. > I'm not kidding, I have been checking > http://prdownloads.sourceforge.net/ipcop/ now every day (sometimes 2x > a day) looking for someone to FINALLY post an updated IPCop ISO. What > a waste of time, nothing for close to a month and half. ..agreed, _you_ wasted it, _waiting_ for someone _else_ to do what _you_could_ have done. ;-) ..<wail snip> > "I am not lazy to compile it, frankly I don't have a PC with Linux on > it available to do this, nor the time; and prolly not the know-how > either. .._take_ your time, _get_ the know-how, STFW & RTFM etc, and _find_out_. ;-) ..failing that, it _is_ possible to pay someone else to do it, just speak up. ;-) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;-) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. |
|
From: Dave R. <da...@cz...> - 2003-07-27 10:11:44
|
> From: Francois Jeanmougin=20 > Subject: Re: [IPCop-devel] CVS releases...... no ISOs still :-( > Suggestion (as far as I have no time yet toi get involved in=20 > the main development), is it really hard toi?: >=20 > - Have a stable branch with security updates made using a patching > scheme or something like that. > - Have a development branch with really different version numbers. I think some people would still have difficulty understanding the difference between stable and alpha/beta code. Like some people have difficulty distiguishing between good and bad manners. Dave |
|
From: Francois J. <Fra...@ad...> - 2003-07-27 09:34:07
|
On Sun, Jul 27, 2003 at 12:32:44AM -0400, Phil Barnett wrote: > On Saturday 26 July 2003 3:40 pm, Baud1200 wrote: > > > Ouch. still no precompiled build since IPcop 1.3.1 Alpha 3. > > Alpha means still changing and in development. It is not for people to be > testing with. It is for developers to be hacking on. > > If you are unable to build it, then it is for sure not for you. Suggestion (as far as I have no time yet toi get involved in the main development), is it really hard toi?: - Have a stable branch with security updates made using a patching scheme or something like that. - Have a development branch with really different version numbers. Having an alpha release sharing the same major(1) and minor(3) as the stable official release seems to be much confusing. For my point of view ipcop really is the good one in the firewall distributions. Thanks for it. François. |
|
From: Ray E. <Ra...@El...> - 2003-07-27 07:07:43
|
> -----Original Message-----
> From: Baud1200 [mailto:bau...@sh...]
> Sent: Sunday, 27 July 2003 5:11
> To: ipc...@li...
> Subject: [IPCop-devel] CVS releases...... no ISOs still :-(
>
>
> Ouch. still no precompiled build since IPcop 1.3.1 Alpha 3.
>
You need to be aware that cvs alpha releases are shared development code
used by the developers to contribute to and work on. They are NOT for use in
production firewall's or outside of the lab environment.
You should also be aware that the developers of the IPcop project are
volunteers who contribute code (unrewarded) *_because_
they_enjoy_working_on_the_project_*. Much of this work comes at a personal
cost of spending hours cutting IPcop code where they may easily choose
otherwise in order to meet their various personal and business commitments.
The obvious (and respected) consequence of this is that there are no
specific timescales for delivery of the next iterations. As such they
deserve much respect for this input. Making demands as you have sours the
enjoyment and is counter-productive.
As always team, thanks for the remarkable work, and an excellent firewall.
RGDS Ray Ellison
Ray Ellison
Microsoft Certified Systems Engineer (Win NT4/2000)
PH: 0419 285 246
email: Ra...@El...
Please send attachments using MIME encoding.
Public Key Available On Request.
----------------------------------------------------------------------------
------------
How secure is your computer on the Internet?
When did you last run Windows Update?
Have you applied the MS Office servicepacks?
Is your Antivirus program up to date, and can it scan email before you read
it?
Do you have a firewall installed?
It makes you think doesn't it.......
----------------------------------------------------------------------------
------------
|