On Wed, 28 May 2003 [EMAIL PROTECTED] wrote:
> I added a rule alloing net2fw conection on tcp port 80.
>
> Added in sh-httpd.conf
> CLIENT_ADDRS="192.168.1. My.IP.Net."
> I tryed also to change the SERVER_NAME/ADDR to ppp0_IP
>
> In hosts.allow I added
> sh-httpd: My.IP.Net.0/255.255.255.0
> I
On Wednesday 28 May 2003 06:15 pm, Theodore Wynnychenko wrote:
> any other ideas on login or su?
As 'root', do:
chmod +4111 /path/to/su
If 'su' isn't run suid, then most likely /etc/shadow isn't
being read because 'su' is running as your non-root user.
--
~Lynn Avants
Linux Embedded Appliance
I added a rule alloing net2fw conection on tcp port 80.
Added in sh-httpd.conf
CLIENT_ADDRS="192.168.1. My.IP.Net."
I tryed also to change the SERVER_NAME/ADDR to ppp0_IP
In hosts.allow I added
sh-httpd: My.IP.Net.0/255.255.255.0
I tryed also to uncomment in hosts.deny the PARANOID
restarted in
Heyas All,
Anyone else out there thinking about LEAF, IPV6, bigger networks, and
policy routing ?
cheers,
/steve
---
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697
thanks Ray. i tried using login.
after connecting via lsh with a user account i tried "login". i also tried
"login root",
"exec login", "exec login root"
they all return the same message:
No utmp entry. you must exec "login" from the lowest level "sh"
also, when i use the "exec login" ver
On Wed, 28 May 2003, Ray Olszewski wrote:
> At 12:23 PM 5/28/2003 -0700, glenn greenfield wrote:
> [...]
> >My router is AT form factor and I have no keyboard for it. Not a problem
> >as I just boot the Bering disk on another system(of course I can't ssh in
> >until I get Bering working). Is i
>Or ... booting the LEAF disk on different hardware long enough to do a
>configuration is probably easier than trying to edit the files after
>mounting the disk on a different Linux system. This is what you say you are
>doing now, right? (Or am I misreading that part?) What are you finding
>un
On Wed, 28 May 2003, glenn greenfield wrote:
> >> My router is AT form factor and I have no keyboard for it. Not a
> >> problem as I just boot the Bering disk on another system(of course I
> >> can't ssh in until I get Bering working). Is it possible to mount and
> >> edit the floppy directly on
>> My router is AT form factor and I have no keyboard for it. Not a
>> problem as I just boot the Bering disk on another system(of course I
>> can't ssh in until I get Bering working). Is it possible to mount and
>> edit the floppy directly on my Debian box or is booting it the only
>> way to edi
At 12:23 PM 5/28/2003 -0700, glenn greenfield wrote:
[...]
My router is AT form factor and I have no keyboard for it. Not a problem
as I just boot the Bering disk on another system(of course I can't ssh in
until I get Bering working). Is it possible to mount and edit the floppy
directly on my
On Wed, 28 May 2003, glenn greenfield wrote:
[...]
> My router is AT form factor and I have no keyboard for it. Not a
> problem as I just boot the Bering disk on another system(of course I
> can't ssh in until I get Bering working). Is it possible to mount and
> edit the floppy directly on my D
Thanks everyone for the input on loading modules for NIC's and floppy drives. I think
I'm all straightened out (for the moment).
Ray- Now I see the search field on Sourceforge- must have missed it first time around.
Still tho- the Mail Archive link doesn't work for me and I clicked the MARC
At 12:22 PM 5/28/2003 -0500, [EMAIL PROTECTED] wrote:
again, i would like to thank everyone for their input.
yes, the su binary comes from (i think) the Dach distribution.
there is not a problem with path. the command does execute when it
resides in /usr/local/bin.
in fact, if i log in as root, i
again, i would like to thank everyone for their input.
yes, the su binary comes from (i think) the Dach distribution.
there is not a problem with path. the command does execute when it
resides in /usr/local/bin.
in fact, if i log in as root, i can su to root (no password required),
and i do get
> Normally, disabling root logins in regular sshd does NOT prevent
> use of su.
> (I routinely set up sshd this way on my servers.) I'd be surprised if lsh
> is different here ... but once more, I cannot be certain.
neither lshd nor sshd or telnetd could prevent the use of su, because they
simply
On Wednesday 28 May 2003 10:02 am, Ray Olszewski wrote:
> Lynn -- I didn't comment initially, because I'm not sure of what I'm about
> to say. But on other systems I've used, this problem arises when su is not
> properly set up to use PAM password processing. Hence, every possible
> password (inclu
Lynn -- I didn't comment initially, because I'm not sure of what I'm about
to say. But on other systems I've used, this problem arises when su is not
properly set up to use PAM password processing. Hence, every possible
password (including the right one) reads as incorrect.
The original poster
Am Mittwoch, 28. Mai 2003 16:29 schrieb [EMAIL PROTECTED]:
> Browsing over Bering1.2 router conected with PPPoE don't work for all
> sites. Some sites work well other stalls and never end opening the site.
clampmss has to be set in shorewall config.
kp
-
On Wednesday 28 May 2003 09:29 am, [EMAIL PROTECTED] wrote:
> Browsing over Bering1.2 router conected with PPPoE don't work for all
> sites. Some sites work well other stalls and never end opening the site.
>
> I found in http://www.roaringpenguin.com/pppoe/how-to-connect.txt:
> ---
Browsing over Bering1.2 router conected with PPPoE don't work for all sites.
Some sites work well other stalls and never end opening the site.
I found in http://www.roaringpenguin.com/pppoe/how-to-connect.txt:
-
I) I ca
20 matches
Mail list logo
