Project

General

Profile

Actions
Copy link

Bug #1353

closed
PB VJ

unix-command socket created with last character missing

Bug #1353: unix-command socket created with last character missing

Added by Philipp Buehler over 11 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Victor Julien
Target version:
3.2beta1
Affected Versions:
Effort:
Difficulty:
Label:

Description

2.1dev (rev ff8dae3) on OpenBSD5.5/amd64 (./configure --prefix /home/suricata --enable-unix-socket)

The unix-command socket is created in localstatedir, but with one character short:
default:
srwxr-x--- 1 root wheel 0 Dec 24 11:06 suricata-command.socke
using a custom name 'custom.123':
srwxr-x--- 1 root wheel 0 Dec 24 11:10 custom.12

Target filesystem is plain OpenBSD ffs.

PB Updated by Philipp Buehler over 11 years ago Actions
Copy link
 #1

Additional info from logging:
[2898] 24/12/2014 -- 13:54:16 - (unix-manager.c:173) <Warning> (UnixNew) -- [ERRCODE: SC_ERR_INITIALIZATION(45)] - Unable to change permission on socket: Invalid argument (22)

VJ Updated by Victor Julien over 11 years ago Actions
Copy link
 #2

  • Status changed from New to Assigned
  • Assignee set to Eric Leblond
  • Target version changed from TBD to 2.1beta4

VJ Updated by Victor Julien almost 11 years ago Actions
Copy link
 #3

  • Target version changed from 2.1beta4 to 3.0RC1

VJ Updated by Victor Julien over 10 years ago Actions
Copy link
 #4

  • Target version changed from 3.0RC1 to TBD

VJ Updated by Victor Julien over 9 years ago Actions
Copy link
 #5

  • Assignee changed from Eric Leblond to Victor Julien
  • Target version changed from TBD to 70

I can confirm the issue on HardenedBSD. Working on a fix.

VJ Updated by Victor Julien over 9 years ago Actions
Copy link
 #6

  • Status changed from Assigned to Closed
  • Target version changed from 70 to 3.2beta1
Actions
Copy link

Also available in: PDF Atom