desktop-packages team mailing list archive

[LPCrooks <lesane.crooks@xxxxxxxxxx>]

Public bug reported:

When connecting to one given IP on SSH multiple times using custom
ports, e.g.

127.0.0.1:22062 and
127.0.0.1:22064

and browsing them interchangeably, Nautilus will display the respective
file lists and folder structures correctly in different tabs; however,
when trying to open a file that exists in the file system at 22062 but
not in 22064 Nautilus will report any file as missing within a correctly
displayed folder on machine 22062 that does not exist at 22064 once one
has accessed 22064 a single time before. In case the file does exist,
Nautilus might display and later on write to either version (did not
grasp the pattern yet) which leads to serious mess working on two
different machines behind a common NAP using port masquerading as in
stated scenario

This bug is persistent throughout an entire unity session even after
disconnecting from the remote machine as well as after terminating
Nautilus so i suggest the bug might as well be based somewhere outside
Nautilus where SSH connections are stacked or something.

Might as well be security-related in case something is written to a
place it shouldn't end up.

** Affects: nautilus (Ubuntu)
     Importance: Undecided
         Status: New

** Information type changed from Private Security to Public

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1452775

Title:
   Nautilus mixes up SSH handles of multiple connections to identical IP
  using different ports

Status in nautilus package in Ubuntu:
  New

Bug description:
  When connecting to one given IP on SSH multiple times using custom
  ports, e.g.

  127.0.0.1:22062 and
  127.0.0.1:22064

  and browsing them interchangeably, Nautilus will display the
  respective file lists and folder structures correctly in different
  tabs; however, when trying to open a file that exists in the file
  system at 22062 but not in 22064 Nautilus will report any file as
  missing within a correctly displayed folder on machine 22062 that does
  not exist at 22064 once one has accessed 22064 a single time before.
  In case the file does exist, Nautilus might display and later on write
  to either version (did not grasp the pattern yet) which leads to
  serious mess working on two different machines behind a common NAP
  using port masquerading as in stated scenario

  This bug is persistent throughout an entire unity session even after
  disconnecting from the remote machine as well as after terminating
  Nautilus so i suggest the bug might as well be based somewhere outside
  Nautilus where SSH connections are stacked or something.

  Might as well be security-related in case something is written to a
  place it shouldn't end up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1452775/+subscriptions