Re: Spam the AOO forums

[Bidouille]

So, maybe a dictionnary attack

- Mail original -
> De: casa...@email.it
> À: "dev" 
> Envoyé: Lundi 30 Janvier 2023 18:06:07
> Objet: Re: Spam the AOO forums
> 
> I did some tests, the two hacked accounts did not have the same
> username/password.
> 
> - Messaggio originale -
> Da: "casalva" 
> A: "dev" 
> Inviato: Lunedì, 30 gennaio 2023 17:42:02
> Oggetto: Re: Spam the AOO forums
> 
> Thanks for the reply, but if I increase the number of characters,
> what happens to the thousands of passwords that already exist?
> 
> - Messaggio originale -
> Da: "Bidouille" 
> A: "dev" 
> Inviato: Lunedì, 30 gennaio 2023 11:46:18
> Oggetto: Re: Spam the AOO forums
> 
> Did you talk about "@pump_upp - best crypto pumps on telegram !"
> flood?
> Seems to be an account issue with same username/password
> 
> PhpBB don't prevent this.
> https://tracker.phpbb.com/browse/PHPBB3-17096
> Only solution is to increase the password lenght to 8
> 
> - Mail original -
> > De: casa...@email.it
> > À: "dev" 
> > Envoyé: Dimanche 29 Janvier 2023 10:05:05
> > Objet: Re: Spam the AOO forums
> > 
> > 
> > A few days ago it also happened in the English forum.
> > 
> > - Messaggio originale -
> > Da: casa...@email.it
> > A: "dev" 
> > Inviato: Domenica, 29 gennaio 2023 9:51:35
> > Oggetto: Spam the AOO forums
> > 
> > Hello everybody.
> > Every once in a while someone manages to hack into an old, already
> > existing account to post spam to the forum.
> > How can we defend ourselves? For now I have deactivated the hacked
> > accounts, without banning ...
> > Regards.
> > 
> > charlie
> > (admin AOO Italian forum)
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > 
> > 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Nightly Builds

[Jim Jagielski]

+1

> On Jan 26, 2023, at 10:09 AM, Matthias Seidel  
> wrote:
> 
> Hi all,
> 
> I think we can all agree on a 4 week  (30 days) period for archiving the
> binaries?
> 
> Looking at:
> 
> https://nightlies.apache.org/openoffice/install/linux64/?C=M;O=D
> 
> we should also think about shortening the filenames. For example the Git
> hash could be reduced to the first 10 digits.
> 
> Opinions?
> 
> Regards,
> 
>Matthias
> 
> Am 22.01.23 um 09:31 schrieb Peter kovacs:
>> The output from git --log can be filtered to a since date. If we use the 
>> last build date then we can check if there are entries.
>> Maybe some other switches would help.
>> 
>> Am 21. Januar 2023 15:03:02 MEZ schrieb Matthias Seidel 
>> :
>>> Hi Gavin,
>>> 
>>> Am 21.01.23 um 13:33 schrieb Gavin McDonald:
 Hi All,
 
 The nightly builds at https://ci2.apache.org/#/builders/58 are using up
 much unnecessary
 disk space on the nightlies.apache.org server.
 
 Currently Openoffice alone is using more than 1TB - all due to these
 nightly builds.
 Over 600GB are the linux64 snapshots and the rest are the linsnap* ones.
 
 Many many of these snapshots are identical to previous ones, but because
 the date of the build is included then they are just repeated each day.
 Even if no commits for weeks there is multi GB tars and debs being uploaded
 each day.
 
 This seems a waste.
 
 Not only this, but no snapshots are being cleaned up, we have snapshots
 dating back nearly a year just sitting there.
 
 Lets clean this up and be smarter going forwards.
 
 I would like to see these nightlies changed :-
 
 1. Change to run weekly instead of daily.
 2. Instead of, or in addition to 1, build and upload by commit trigger.
>>> Just to clarify:
>>> 
>>> I think the logic should be: Look every day (night) if there was a code
>>> change. If yes, do a build, otherwise skip.
>>> 
>>> I don't want to trigger a build with every single commit... ;-)
>>> 
>>> Regards,
>>> 
>>>Matthias
>>> 
 3. Clean up snapshots older than 1 month.
 
 Thoughts please
 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org