[MacPorts] #70680: sudo @1.9.16 -- sudo: port: command not found

[MacPorts]

#70680: sudo @1.9.16 -- sudo: port: command not found
---------------------+--------------------
  Reporter:  RobK88  |      Owner:  (none)
      Type:  defect  |     Status:  new
  Priority:  Normal  |  Milestone:
 Component:  ports   |    Version:  2.10.1
Resolution:          |   Keywords:
      Port:  port    |
---------------------+--------------------

Comment (by Schamschula):

 Replying to [comment:21 jmroot]:
 > Replying to [comment:19 Schamschula]:
 > > I'm not sure when this was changed upstream: need to check the release
 notes.
 >
 > I remember we went through this years ago when Apple first shipped a
 version that defaulted to sanitising the environment.
 >
 > Using whatever PATH happens to be set is not a good (secure) default,
 but adding the MacPorts prefix to the default secure_path might be OK.

 I'm thinking of substituting the MacPorts path for {{{/usr/local/*}}},
 i.e. setting

 {{{--with-secure-path-
 value=/opt/local/sbin:/opt/local/bin:/usr/sbin:/usr/bin:/sbin:/bin}}}

 If someone wants/needs {{{/usr/local/bin}}} or {{{/usr/local/sbin}}}, they
 can edit {{{sudoers}}}, even though that has several hurdles. In my case,
 the command line tools for BBEdit are installed under
 {{{/usr/local/bin}}} .

-- 
Ticket URL: <https://trac.macports.org/ticket/70680#comment:22>
MacPorts <https://www.macports.org/>
Ports system for macOS