Bonum Certa Men Certa

Shaya Potter & Debian WaReZ expulsion

posted by Roy Schestowitz on Mar 15, 2024,
updated Mar 15, 2024

Shaya Potter

Reprinted with permission from Daniel Pocock.

In recent years, Debian leaders have abused their positions to leak rumors and gossip about some developers while hiding far more serious scandals.

One of those is the shadow expulsion of Shaya Potter (blog, CV) in 1998.

Potter was a child prodigy who began a US Navy internship when he was fifteen or sixteen. At the same time, Novare, Inc was hosting some Debian infrastructure on their company servers.

Potter claims his software was being deployed to the USS Theodore Roosevelt (Secure Tactical Access Terminal) while at the same time, Debian records show that he was stashing WaReZ on master.debian.org, a server operated by Novare.

The case of a navy intern committing piracy is interesting for a wide range of reasons that have a lot more to do with Debian than the navy.

Potter began co-authoring Debian as a minor. It appears that he was 19 when he was caught with WaReZ but it is not clear what age he was when he actually downloaded these illegal copies of software. The age of majority varies between different countries and different states of the US. Therefore, there was some confusion about whether it should be handled as a juvenile offence. I recently wrote about the concerns with FSFE encouraging minors to do unpaid work on open source projects.

Earlier this year I wrote about the fact that only 86 of the original Debian co-authors agreed to form an association with a constitution. If we look at the names of the people who consented to form an association, Shaya Potter is not in the list. If Potter did not consent to the constitution then he wasn't a member at all. Morever, the association only came into existence at the end of the vote in December 1998. Potter was supposedly expelled in November 1998, one month before the vote. Therefore, as the organization didn't really exist yet and as he hadn't consented to be a member, we can't really say he was expelled at all.

Nonetheless, it looks like his position with the US Navy also ended the year after the Debian drama. Barely five years later, Potter went on to win the LISA'05 award for the best student paper.

The great irony in this case is that people were angry with Potter for violating copyright law. Yet this was the first time the developers forcefully removed the name of a Debian co-author from the software. Therefore, by removing his name and failing to give him equal credit as a joint author of the Debian software, they were violating his copyright interests. They set a precedent for violating the copyright interests of other authors, for example, the violent suppression of Ted Walther in DebConf6.

To put this in perspective, consider the case of Rolf Harris, convicted of harassment and abuse in the UK. His copyright interests from a long career in show business still continued to receive royalties even during his time in prison. If a sex offender can continue receiving royalties while in prison, why can't all Debian Developers continue receiving recognition even after minor disputes within the project?

At the time, developers expressed some concern that the scandal would be leaked and gain significant publicity due to the connection with the US Navy.

It is interesting to see how this scandal regarding a minor and the US military was covered up while gossip about other developers, like the assault on Ted Walther was deliberately leaked. The accusations against Potter were far more serious than the gossip about Walther.

In 2018, Debian leader Chris Lamb started making attacks on the privacy of volunteers and our families.

Despite supposedly being "expelled" from an organization that didn't exist, Potter has continued maintaining the hebcal package, the Perpetual Jewish Calendar, for more than twenty years. Potter moved to Israel in August 2019, four months after the decision to send DebConf20 to Haifa, Israel. It looks like the expulsion was in some ways a charade so that Debian can pretend they take a hard line on piracy while in reality, there were no consequences for Potter's career. He walked straight out of the US Navy and into IBM TJ Watson research laboratory.

Please see the next blog post for details about how Potter made these bad choices under the burden of 14,000 messages from debian-private.

One of Potter's earlier emails to the debian-private gossip network

Subject: Re: Debian release strategy (Was: Re: XFree86 3.2 is out, should we , , delay the release , of Debian 1.2)
Date: Fri, 1 Nov 1996 14:17:42 -0500 (EST)
From: Shaya Potter <spotter@itd.nrl.navy.mil>
To: Klee Dienes <klee@sedona.com>
CC: Bruce Perens <Bruce@pixar.com>, debian-private@lists.debian.org

On 1 Nov 1996, Klee Dienes wrote:
> > > I think the key is getting LIBC 6 and the new X available _early_ in > > the time frame. > > I've got a preliminary packaging of glibc-1.96 ready (as part of the > testing/development of the POSIX/FIPS-152 conformance testing > package). I've been holding off on uploading it until after rex was > frozen to avoid adding too much confusion to the pot, as well as to > see what comes of our new-found relationship with Lasermoon. I'll > upload a copy on Monday after the code freeze takes place.
Oh, about the posix testing, if you need help I am still here.
Thanks,
Shaya -- Shaya Potter spotter@itd.nrl.navy.mil
-- Please respect the confidentiality of material on the debian-private list. TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com

Potter asked the Debian leader to hand over copies of debian-private discussion about underage developers.

Subject: Re: why I want the archives on me (was Re: spotter@debian.org)
Date: Tue, 17 Nov 1998 12:56:41 -0500
From: Shaya Potter <spotter@ymail.yu.edu>
To: joost@pc47.mpn.cp.philips.com
CC: debian-private@lists.debian.org

----- Original Message ----- From: <joost@pc47.mpn.cp.philips.com>
> >On Tue, 17 Nov 1998, Shaya Potter wrote: > >> Now that this is out of the way, I'd like to publicly ask if I can have an >> archive of all the communication that went on in regard to me. > >Strictly speaking I tend to disagree that you or anybody has an a-priori >right to know what is being said and told on debian-private. It is simply >a private list. Things would be different if you were mentioned in a >public list without being able to respond. But that is in all aspects >clearly not the current situation.
First, I never said I have a right. In many ways I think i don't have a right, or even if I did, I don't deserve it. I don't think my statements have implied that I believe I have a right to demand that it be given to me.
I do have a right to ask that it be done. Debian has a right to say yes or no.
> >(Nevertheless, I think that it would be considerate to cc: you in >any discussion that involves you in a very personal manner - this has >IMHO until now hardly been the case though.)
It hasn't? Than how did the decision to expell me come about? Who told people who made the decision what happened? Was this all done in private mail?
> >If a non-subscriber of debian-private must share in the conversation on >debian-private, then this should IMHO be done by adding that person to the >clearly visible cc: line of the header of any messages to be "published." >That way, it will be adequately clear that the correspondence leaves the >realm of debian-private and thus everybody can conclude that normal >confidentiality can not be expected. AFAIK respect for the confidential >nature of debian-private is a prerequisite for subscription to this list.
I would have respected the confidentiality, as I have made it known that I don't want this to spread, as I am embarrased by my actions.
> >Practically speaking, I disagree that the underlying case generally >concerns you. What matters here is not who Shaya Potter personally is or >what particularly Shaya Potter did. The discussion is about how issues >like the one involving you relate to Debian. This discussion does not >involve you personally.
I don't want the entire discussion, I just want to see the parts that touch on me personally. I don't care for the rest, of what about underage developers and the like....
> >> I was told that it would not be a star chamber, and that I'd be cc'd in >> on all the corrospondace. That didn't occur. > >There was no "star chamber." You have already been generously cc:'-ed.
I was? The only cc:'s I ever got were in response to me starting a thread. That implies to me, that acc. to what you were saying, that no discussion on -private occured that I didn't start. However, I know this not to be the case, as before I was unsubscribed from -private, I saw a thread or 2 started that dealt with me.
> >IMHO you do not have a right to be cc:-'ed on the _general_ discussion >which does not particularly (personally) involve you.
never said I did.
> >> Also, I really have no idea of what discussion went on, if mistruthes >> were spread about the incident (as in reality, I'm the only one that >> knows completely what happened, and no one really ever asked me for the >> full story). > >If this worries you so much, then I seriously wonder why you did not >immediately relate it to debian-private when the issue arose in the first >place?
I did apologize on -private right away, however, I didn't want to spread what I did. I specifically told people that I would rather this not be discussed on -private and have me showed the door quietly, and told never to come back. That didn't happen, it was discussed on -private. I don't know what was discussed in relation to me, so I want to be informed.
> >Again, the discussion is not yours. Again, you are not personally >involved. Your only "role" in the discussion is that you have created a >precedent. I thinks we can all agree that we would rather have had you >not be a precedent case, but it happened. I'm very sorry, but you'll >have to blame yourself for that.
Trust me, I've blamed myself a lot for this. If you seen any of my corrospondance you would know this. I don't blame anyone for my predicament, but myself.
>Discussion on debian-private does not count as a statement from Debian. >So there simply were no statements. I'm not really in favor of making any >strong or overly verbose statements either. If there ever is to be a >statement from Debian about an issue such as the current one involving >Shaya, I think that person should be briefed thoroghly beforehand.
I'm not talking about a debian statement. I don't want a public statement, and I know a lot of people from debian don't want one either (though some might). What I meant by statements, was statements that individuals made, that might be incorrect, or inacurate.
>Shaya, can you please just put this to a rest? IMHO it is not very >productive for anybody. And please take it from me that you have no >reason to be concerned that you have been in a "star chamber."
I am not worried about a star chamber, I would have prefered it in many ways. However, at least with a star chamber you usually get to see the case presented against you, even though you don't have the ability to defend yourself. As I said many times, my case is indefensable, so that wouldn't bother me.
Shaya

Potter actually resigned on 2 November 1998 but they still spent two weeks deciding to expel him

He was not a member anyway as the organization didn't exist yet. He resigned. Therefore, how obscene it is to retrospectively have an expulsion.

This practice of expelling a non-member, which is obviously unethical and impossible, laid the foundation for many future problems in Debian. For example, Frans Pop had tried to resign before committing suicide but people pulled him back in.

Subject: Re: Novare and master
Date: Mon, 2 Nov 1998 15:56:06 -0600
From: Ean R . Schuessler <ean@novare.net>
To: Shaya Potter <spotter@yucs.org>
CC: debian-private@lists.debian.org

On Mon, Nov 02, 1998 at 12:59:22AM -0500, Shaya Potter wrote: > I have heard through the grapevine that you are considering pulling > novare's support of debian b/c of my actions. is this true? if it is, I > would hope that you reconsider and view me as an aberation. My behavior > was wrong, stupid, illegal, puts novare and debian in a sticky situation > and above all that, broke a trust that was given to me. I would like to > apologize for these things, but in my mind an apology doesn't fix the > past, it can only set the foundation for the future. If in your mind, you > would be more open to allowing debian to continue on as is, if I am gone, > let this be my letter of resignation. If other debian developers think I > should be gone,let it too be a letter of resignation. I don't want this > to turn into a public argument and the more it's argued even in private, > the more public it can become. I can't take the embarasment and rather be > kicked out and punished swiftly than have the chance of staying.
Say what? You're on smack. Kick your bootie for being a naughty little man, yes. Stop supporting Debian because you wanted some 3l1t3 w4r3$, not friggin' likely.
I think that you should take on 10 new packages and maintain them in an exemplary manner, you should also break some raw eggs on your face, take a picture and we'll post it on devel. I might even send my girlfriend to infiltrate your Navy base and spank you bloody. What you should stop doing, however, is whining and pirating software.
Ahimsa. E
-- _______________________________________________________________________ Ean Schuessler Director of New Products and Technologies Novare International Inc. The Unstoppable Fist of Digital Action *** WARNING: This signature may contain jokes.

Please see the next blog post for details about how Potter made these bad choices under the burden of 14,000 messages from debian-private.

Other Recent Techrights' Posts

Disable 'Secure Boot' (If It Lets You)
it doesn't put you in control
Longtime Red Hat Staff: Maybe Just Disable 'Secure Boot'
A refreshing take from Adam Williamson
A Dozen Observations About "UEFI 9/11" Deflections
What we are expected to see, tentatively
The World's Richest Ponzi Scheme (Faking Value Using Net Waste)
The higher they go the harder they fall
We Could Dual-Boot Back in the 1990s, Why Has This Become So Difficult?
And prone to breakage
Slopwatch: Google News is Still Promoting Many Fake Articles About "Linux", in Effect Rewarding Misinformation and Plagiarism
things continue to deteriorate
They Say That People Are Afraid of or Worried About "Hey Hi", But the Worriers Should be the Fools Who Invested in It
At the end of the day nobody should worry more than those who invested their money in this bubble
 
The UEFI 9/11 - Part X - An Outline of the Series About Microsoft Sabotaging GNU/Linux (With Ramifications to Unfold Online in Coming Weeks as People Reboot)
Today is UEFI 9/11 (9/11/2025)
Ron Wyden: Microsoft Should be Held Accountable for Security Breaches (He Has Said This for Years Already, It Never Happens)
Negative media coverage isn't a fine and it does nothing to compensate Microsoft's billions of victims
Culture of silence: Ubisoft harassment convictions, Mozilla, Sylvestre Ledru & Debian make no comment
Reprinted with permission from Daniel Pocock
Links 11/09/2025: "Hey Hi" Ponzi Schemes at Oracle (Unpaid Contracts) and Cindy Cohn is Leaving the EFF
Links for the day
Gemini Links 11/09/2025: Playdate Console, Dichotomy between the Real and the Digital
Links for the day
The Microsoft AstroTurfing and Microsoft-Led Blame-Shifting Tactics Are Ahead of Us
Of course it has nothing to do with security, it's about control, i.e. them controlling everything
Celebrating Assassination is Bad Because It Legitimises Assassination of the People You Like, Too
Condoning or even celebrating political assassinations is bad optics (and taste)
Being Conditioned to Accept Unreliable Computer Systems That Fail With Black Screen of Death (BSoD)
Welcome to 2025
New Series: The Coup Against GNU/Linux Has Begun
today, this year in particular, we shall also focus on Secure Boot, which is sold based on a lie and tortures many computer user
New Paper on "BYOVD, but in firmware. Signed UEFI shells, vulnerable modules offer new paths for Secure Boot bypasses."
One might say digital "security theatre"
Links 11/09/2025: Oracle Layoffs, Drunk Pilots in Japan Airlines, US-Korea Tensions Grow
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, September 10, 2025
IRC logs for Wednesday, September 10, 2025
Xubuntu Site Compromised
Let's hope it is not a security breach
Links 10/09/2025: Retaliation at Facebook and Microsoft Reveals Almost 100 Security Holes
Links for the day
Gemini Links 10/09/2025: Annihilation of Self, The Future Eaters, and Leaving Academia
Links for the day
Harassment evidence: franceinfo's Clara Lainé report on Ubisoft prosecution
Reprinted with permission from Daniel Pocock
Links 10/09/2025: Microsoft Layoffs in "RTO" Clothing and Windows TCO, GitHub TCO
Links for the day
Blaming Everything on China
TikTok works for China. GAFAM works for fascists.
People Get Tired of "Hey Hi" (AI), Unlike the Subservient Money-Obsessed Media That Gets Paid to Pretend This Bubble Still Matters
"crash will be way bigger than dot.com burst in 90s. and that was Internet, actually transformative technology, not this expensive AI toy with direct dependency on the energy input which is not scalable"
Brett Wilson LLP Accepts That the Serial Strangler From Microsoft Filed a Case That Also Implicates My Wife (Everything is Connected)
They used to pretend that there were two separate cases
10 Reasons to Disable (or Enable) UEFI Secure Boot
Tomorrow the "trusted corporation" Microsoft will see a certificate expire
Gemini Links 10/09/2025: Hospital and Large Feeds
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, September 09, 2025
IRC logs for Tuesday, September 09, 2025
The Bluewashing of Red Hat is Being Completed, Many Staff Understand They'll be Made Redundant
Jim AllowHurst (Whitehurst) is meanwhile promoting Microsoft's agenda from within other companies
Throwing Away "Old" Computers (Mozilla and Other Climate Deniers)
Mozilla is not leftist
statCounter Sees GNU/Linux Exceeding 10% in Bulgaria This Month
What can Microsoft still do to stop GNU/Linux?
Dark Patterns
Microsoft saying "security" is like a Convicted Felon in the White House saying "law and order".
It's Almost Fall (Autumn)
To "Facebook prison" you are bound
Bruce Schneier About "Secure Boot"
Bruce Schneier isn't a fan of "Secure Boot"
Links 09/09/2025: Microsoft Mass Layoffs Again and "RTO" (Timed Like It Serves as a Distraction From the Mass Layoffs)
Links for the day
RMS Told Microsoft to Stop 'Secure Boot' (He Even Went There to Say That), But They Didn't Listen
Dr. Stallman (RMS) assumed that speaking to sociopaths would work
What Richard Stallman Told Me About 'Secure' Boot in 2012
"if the user doesn't control the keys, then it's a kind of shackle"
Those Who Helped Microsoft Weaponise "Secure Boot" Against GNU/Linux and BSDs Are Fleeing
Microsofters doing what they do best: they evade accountability
Simple is Better, Simplicity is Power
That is "the advantage of having commodity GNU/Linux systems," an associate notes
Much Ado About Nonsense
Microsoft Lunduke is still all dramatisation and sensationalism
Current Events in France
It needs to dump Microsoft and other GAFAM (US) giants, move to Free software
Further Media Cut-downs
media reporting about the media being cut
Links 09/09/2025: US-Korea Tensions and Meta Whistleblowers
Links for the day
Gemini Links 09/09/2025: Moon Eclipse and ROOPHLOCH Reports
Links for the day
Links 09/09/2025: “Torrents of Hate” and Political Crisis in France
Links for the day
Gemini Links 09/09/2025: "Dedigitizing" and Forgejo on FreeBSD
Links for the day
Google News (Not Just Google Search) Lets Itself by Gamed by One Slopfarm - to the Point Almost Half of "Linux" News is Bot-Produced Plagiarism (LLM Slop With Slop Images)
That says a lot about what Google thinks of quality, even in Google News
Bill Gates-Funded Media Inadvertently Refutes the Microsoft Lie That in 2025 Microsoft Had Just Two Waves of Layoffs
There were about 12 rounds of layoffs so far in 2025
Official SUSE Blog Still Uses LLM Slop (Bots) to Make Fake Articles (Marketing)
The company is all about sound bites
Companies Realise That Slop Doesn't Work as Advertised, Accordingly Dump It
"Hype dims as a country-wide survey of US corporations shows a sudden drop-off in AI use among firms with more than 250 employees."
Microsoft-Funded Lawsuits Against Critics of UEFI 'Secure Boot'
Remember that no company (or law firm) ever survives collaborations with Microsoft
From theregister.co.uk to theregister.com (US) to The Register MS (Run by Microsoft Operatives) and theregister.ai
The best way to break this racket (or cycle of hype and harm) is to break the chains of funding
Open Source Initiative (OSI) Culture of Censorship Necessitates More Speech
The OSI bans dissent or people who merely point out that the OSI is abusive
How to Reach Us Discreetly (Other Than Encrypted E-mail)
We're still managing to maintain a 100% source protection record. We soon turn 19.
LLMs Are Vastly Worse Than a Waste of Energy and the Externalities Are Huge
Worse than just higher power bills for everybody
LLMs Versus Search (Not Replacing Search But Engaging in DDoS Attacks Against Web Sites That Permit Searching)
The state of the Web isn't just bad; it's utterly terrible
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, September 08, 2025
IRC logs for Monday, September 08, 2025
It's Only the Second Week of September and Already Two Waves of Layoffs at Microsoft, Slopfarms and Microsoft-Funded Sites Spin It as "AI Investments" Rather Than Commercial Failure
A very large third one expected next week
The UEFI 9/11 - Part IX - Shunning Old Computers (in 2023 the Certificate Was Updated/Overridden, Underlying Aim May Be Herding/Forcing People to Get TPM and Other 'Novel' Restrictions)
the "upgrade treadmill"