bugWebSTUMP - Bugs: bug #59356, Merge into STUMP

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #59356: Merge into STUMP

Submitter:  Tristan Miller <psychonaut>
Submitted:  Mon 26 Oct 2020 04:42:52 PM UTC
 
Category:  None Severity:  1 - Wish
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Mon 27 Dec 2021 10:51:33 PM UTC, comment #2: 

Experiments with gpg indicate that my first plan to have the scripts that run from web form submissions do the signing for rejections or PGPMoose approvals is not going to work. It seems that the gpg security features get in the way of doing anything in a suid script where real and effective users differ.

The simple solution is to migrate the STUMP mail handling into Webstump so that Webstump mails itself messages that trigger scripts that run entirely as the Webstump user to carry out the signing and either posting of articles or mailing of rejections. Messages that Webstump sends to itself do not need to contain any of the data (unlike messages to STUMP), they just need to say which message is to be processed.

Having a trigger message that just says 'process all articles with decisions' would require some concurrency control which is probably a step too far.

Owen Rees <owenrees>
Project Member
Fri 17 Dec 2021 09:04:37 PM UTC, comment #1: 

I would do this by merging STUMP into WebSTUMP as WebSTUMP already supports multiple newsgroups. Here is an outline of how I would go about it - I think at least some of the various intermediate stages are useful in their own right.

  1. Support submissions directly to WebSTUMP
    1. Rejection reasons and messages managed by WebStump (use with STUMP 'reject custom' at first)
    2. Acknowledgements received/approved and rejections mailed directly from WebStump (STUMP noAck list to match everyone and all rejections are 'ignore' at first).
    3. Add managed automated rejection for binary/HTML etc.
    4. Accept submissions directly, post approved messages directly (use absence of stump-prolog.txt to select direct posting so WebSTUMP handles both cases)
  2. Migrate STUMP email based moderation into WebSTUMP as a per-group option

I think that ends up with WebSTUMP being able to do everything that STUMP does now but with per-group options managed via a web interface.

Owen Rees <owenrees>
Project Member
Mon 26 Oct 2020 04:42:52 PM UTC, original submission:  

WebSTUMP bills itself as a front end to "STUMP and Gatekeeper", Gatekeeper being a successor to STUMP that its original developer, Igor Chudov, planned but apparently never ended up releasing.  So I think this means that WebSTUMP is not currently useful without STUMP. Conversely, I don't believe that STUMP is commonly used without WebSTUMP, but even if it is, I think there are no disadvantages to distributing WebSTUMP with STUMP.  So perhaps we should merge WebSTUMP into STUMP.

Tristan Miller <psychonaut>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by owenrees (Posted a comment)
  • -email is unavailable- added by psychonaut (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    No changes have been made to this item

    Back to the top


    Powered by Savane 3.9