Perl 5 Commit Summary #1136

Perl 5 commit summary, activity since Wednesday

No activity.
0
nick
6/27/2020 3:10:23 AM
perl.perl5.porters 48117 articles. 1 followers. Follow

3 Replies
16 Views

Similar Articles

[PageSpeed] 25

--00000000000027f30105a90865e6
Content-Type: text/plain; charset="UTF-8"

At least it's correct this time.


On Fri, Jun 26, 2020 at 8:10 PM Perl 5 commit summary <nick@ccl4.org> wrote:

> Perl 5 commit summary, activity since Wednesday
>
> No activity.
>

--00000000000027f30105a90865e6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-size:small">At least it&#39;s correct this time.</div><div style=3D"font-=
size:small" class=3D"gmail_default"></div><div><br></div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jun 26, 20=
20 at 8:10 PM Perl 5 commit summary &lt;<a href=3D"mailto:nick@ccl4.org">ni=
ck@ccl4.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">Perl 5 commit summary, activity since Wednesday<br>
<br>
No activity.<br>
</blockquote></div></div>

--00000000000027f30105a90865e6--
0
perl
6/27/2020 3:26:29 AM
--Apple-Mail=_4743B68A-ED3E-437C-A68D-EFEE01CC2991
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Interesting. Rik is trying to kill this email and thought he had =
succeeded.

> On Jun 26, 2020, at 10:26 PM, Karen Etheridge <perl@froods.org> wrote:
>=20
> At least it's correct this time.
>=20
>=20
> On Fri, Jun 26, 2020 at 8:10 PM Perl 5 commit summary <nick@ccl4.org =
<mailto:nick@ccl4.org>> wrote:
> Perl 5 commit summary, activity since Wednesday
>=20
> No activity.


--Apple-Mail=_4743B68A-ED3E-437C-A68D-EFEE01CC2991
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Interesting. Rik is trying to kill this email and thought he =
had succeeded.<br class=3D""><div><br class=3D""><blockquote type=3D"cite"=
 class=3D""><div class=3D"">On Jun 26, 2020, at 10:26 PM, Karen =
Etheridge &lt;<a href=3D"mailto:perl@froods.org" =
class=3D"">perl@froods.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gmail_default" =
style=3D"font-size:small">At least it's correct this time.</div><div =
style=3D"font-size:small" class=3D"gmail_default"></div><div =
class=3D""><br class=3D""></div></div><br class=3D""><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jun =
26, 2020 at 8:10 PM Perl 5 commit summary &lt;<a =
href=3D"mailto:nick@ccl4.org" class=3D"">nick@ccl4.org</a>&gt; wrote:<br =
class=3D""></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">Perl 5 commit summary, activity since =
Wednesday<br class=3D"">
<br class=3D"">
No activity.<br class=3D"">
</blockquote></div></div>
</div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_4743B68A-ED3E-437C-A68D-EFEE01CC2991--
0
toddr
6/27/2020 6:17:59 PM
On Sat, Jun 27, 2020 at 01:17:59PM -0500, Todd Rinaldo wrote:
> Interesting. Rik is trying to kill this email and thought he had succeeded.

The (crazy) problem is that my shell access to the machine was cut off
without warning, so I wasn't able to disable the cronjob.

But for some reason Ricardo still has shell access to the machine. However,
he has no permissions of any form (read or even execute) on my home
directory, so despite me being able to tell him exactly what files are
where, how they are triggered, what they do, and about 5 ways you might
knobble it if you had even the slightest bit of access, he can't.

Also, whilst we know the (top level) owner of the rack (etc) that the
machine sits within, we seem to be completely unable to find anyone who
has root access, or even *knows* who has root access. It seems that the
machine has been disowned.

My suspicion is that as it was set up by someone who has now left that
company, records of it have mostly been lost. But that doesn't explain
how/why my shell access was cut off last October, as the original
sysadmin responsible for the setup had already (amicably) left by then,
so someone else must exist who has some root access.

(ho, unless it's getting authority for me via, say, LDAP, but not
Ricardo. In which case LDAP changes elsewhere would have this side effect,
for me, but not for him.)

Pulling the power cable (or the network cable) on the machine would be
just fine. But we can't even find someone who would do that.

Nicholas Clark
0
nick
6/27/2020 6:29:18 PM
Reply: