Ticket #209 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

While starting up, wrong pidfile can lead to wrong socks file

Reported by: bryan Owned by: bryan
Priority: blocker Milestone: 1.2.9
Component: binary/shell Version: 1.2.9
Keywords: Cc:

Description

This is from the mess of moving tempdir/datadir all over the place example:

.restart ->

  • .../.pid.bot is written with 'PID /tmp/.socks-FOO'
  • control is transferred to new binary
  • new binary finds ~/.ssh/.../.pid.bot with 'PID /tmp/.socks-BAR'
  • binary fails to open proper socks file.

Change History

Changed 5 years ago by bryan

  • status changed from new to assigned

On upgraded nets with bots using ./.../ as a datadir: .bc & exec rm -f ~/.ssh/.pid.*

Then, fix the bug in the logic in the compat_check_pids() for the remainder of the botnet upgrades.

Changed 5 years ago by bryan

Also from /var/tmp

/tmp

/usr/tmp

Changed 5 years ago by bryan

  • status changed from assigned to closed
  • resolution set to fixed
Note: See TracTickets for help on using tickets.