Page 1 of 1

Couldn't get the port at 378

PostPosted: Wed Jul 11, 2012 2:15 pm
by help40
/usr/local/bin/lptout1 0
Error: Couldn't get the port at 378

what to do to be able to use my parallel port again ?
I am using it to power cycle my "device" when internet goes down
now I am stuck

Re: Couldn't get the port at 378

PostPosted: Thu Jul 12, 2012 8:01 am
by spender
What grsecurity logs appear in the kernel log? What's the strace of it?

-Brad

Re: Couldn't get the port at 378

PostPosted: Wed Jul 18, 2012 7:21 am
by help40
spender wrote:What grsecurity logs appear in the kernel log? What's the strace of it?

-Brad


is that what you are asking for ?

Jul 15 14:58:36 kernel: grsec: denied use of ioperm() by /usr/local/bin/lptout[lptout:13913] uid/euid:0/0 gid/egid:0/0, parent /usr/local/bin/dslmon.sh[dslmon.sh:2061] uid/euid:0/0 gid/egid:0/0

or when I execute it manually
Jul 18 17:12:21 kernel: grsec: From 46.10.108.246: denied use of ioperm() by /usr/local/bin/lptout[lptout:610] uid/euid:0/0 gid/egid:0/0, parent /bin/bash[bash:595] uid/euid:0/0 gid/egid:0/0

Also more info about kernel I am using ...
$ uname -a
Linux 2.6.32.59-grsec-smp #1 SMP Sat Jul 7 16:09:09 EEST 2012 i686 Intel(R) bla bla ......

Re: Couldn't get the port at 378

PostPosted: Wed Jul 18, 2012 7:29 am
by help40
I checked now the forum for "ioperm" .... and my config file too

is that I must to change to be able to use my "parallel program" again ?

# Memory Protections
#
# CONFIG_GRKERNSEC_KMEM is not set
# CONFIG_GRKERNSEC_VM86 is not set
CONFIG_GRKERNSEC_IO=y
CONFIG_GRKERNSEC_PROC_MEMMAP=y
# CONFIG_GRKERNSEC_BRUTE is not set
# CONFIG_GRKERNSEC_MODHARDEN is not set
# CONFIG_GRKERNSEC_HIDESYM is not set
# CONFIG_GRKERNSEC_KERN_LOCKOUT is not set

Re: Couldn't get the port at 378

PostPosted: Wed Jul 18, 2012 8:14 am
by spender
Yes, you'll need to disable that feature.

-Brad