February 2026 - whitebox-dev - ml.whitebox.aero

Re: Contact form submission
by Xavier Antoviaque 20 Feb '26

20 Feb '26

Hi Quinn, The mailing-list email is dev(a)ml.whitebox.aero - I have put it in CC, in this email and my previous one, so Milos and Avinash should be getting it too. And sounds good then - let's schedule a meeting now to have it on our calendars? What time(s) would work for you? How about Tuesday Feb 24th at 17:00 UTC+1? This would be right after our team weekly meeting. -- Xavier Whitebox.aero <https://whitebox.aero/> On Thu, Feb 12, 2026, at 15:38, Tracestrack wrote: > Hi Xavier, > > I didn’t see the mailing list you mentioned in the mail. Could you forward it again? > >> And yes, let's figure out a way to merge this together in the meantime. We had discussed doing a call to look at the customization options for the maps -- maybe we could also use the opportunity to discuss the remaining steps on the MR? Next week we have a release so we will have to focus on that, but how about the week after, from Feb 23? > > Yes no problem. Let’s try to merge the MR after the release. I would not increase the current scope and leave room for improvement later. > > Best regards > Quinn > >> On 12 Feb 2026, at 09:20, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >> >> Hi Quinn, >> >> Great, thank you! April for the work on improving the new contributor experience sounds good! It also gives us some time to finish the current >> >> And yes, let's figure out a way to merge this together in the meantime. We had discussed doing a call to look at the customization options for the maps -- maybe we could also use the opportunity to discuss the remaining steps on the MR? Next week we have a release so we will have to focus on that, but how about the week after, from Feb 23? >> >> I'm also CC'ing the mailing-list -- Milos, Avinash, would that work for you too? Also have a look at this email thread, below, for context. >> >> -- >> Xavier >> Whitebox.aero <https://whitebox.aero/> >> >> On Tue, Feb 10, 2026, at 13:54, Tracestrack wrote: >>> Hey Xavier, >>> >>> Thanks for your nice gesture! Indeed to make an open source project successful, it's very important to make it easy to work with. I appreciate your attitude to make the project better. >>> >>> Yes feel free to forward my feedback to other developers. Maybe I missed some design decisions so I can also discuss with them. I can discuss in the PR or if possible I can also join the mailing list. >>> >>> For the follow up work to improve developer experience, I can continue with it in April. Let's first aim to merge the existing work. In a trunk based development approach, there is no need to wait for a PR to be perfect. We always improve the master branch and have stable release branch. >>> >>> Best regards >>> Quinn >>> >>>> On 10 Feb 2026, at 12:37, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>> >>>> >>>> Hi Quinn, >>>> >>>> Sorry that you have to go through some of the rough edges of the current project setup -- you're one of the very first external contributors, and as a result some of it isn't as intuitive or well documented as it should be. (Btw, definitely feel free to charge me for the extra time that you end up spending on the work because of this, as needed - that's useful work that deserves pay.) >>>> >>>> If the nginx change is tricky, we can look into moving that part to a separate task to assign it to Avinash or Milos. Can I CC the mailing list, so that we keep others aware and discuss this with them? >>>> >>>> I'm thinking that your impressions and issues are important to address, as you won't be the last one to face them afterwards, all future contributors will too. So I would like to offer you to do a second task/contract, which would be to address some of the issues you have had: you know best what would have helped you to find when you got started with the project, so you are uniquely equipped to address them. For example, adding missing information in the documentation, explaining better the parts of the plugin system that you had trouble understanding initially, fixing installation issues, improving error messages you got, adding logging/debug info that would have helped you, etc. >>>> >>>> And if there are some things you are not sure how to improve, you could create tasks in our backlog to address them instead, to be assigned to the team. Would you be up for that? That would help the project tremendously, if the next contributor after you could benefit from your experience ! >>>> >>>> -- >>>> Xavier >>>> Whitebox.aero <https://whitebox.aero/> >>>> >>>> On Sat, Feb 7, 2026, at 21:28, Tracestrack wrote: >>>>> Hey Xavier, >>>>> >>>>> The PR is still not merged and it seems the team wants to use proxied requests for map resources using nginx: >>>>> 1) https://gitlab.com/whitebox-aero/whitebox/-/merge_requests/195#note_3045052… >>>>> 2) https://gitlab.com/whitebox-aero/whitebox-plugin-map/-/merge_requests/31#no… >>>>> >>>>> Currently my approach is a simple DNS/hostname change. Would it be more efficient if the teams fix it using nginx, as for me it’s not quite straightforward? Or could they take over my PRs? >>>>> >>>>> At the beginning you asked me some feedback. Here are some based on the map refactoring work (I might be wrong because of lack of project requirement knowledge): >>>>> 1) the plugin system looks cool but it makes the learning curve more steep and harder to work with. It can be a lot easier to use a single repo to build and test. At least some core plugins can be built in to the frondend/backend directly, for example map, since it’s impossible to build/use without it. >>>>> 2) the network part is complicated but probably necessary. But the use of DNS server/dnsmasq might be an overkill. It can be simplified by setting /etc/hosts file or set the hosts in the router's DNS config. We can also hardcode hostnames in all the config/url paths, something like I did with “dev-server” hostname, instead of all the proxies and APIs to get hostname. >>>>> >>>>> Overall I think it’s a complicated project and it’s not very easy to work with and requires a lot of technical knowledge to set up. >>>>> >>>>> Best regards >>>>> Quinn >>>>> >>>>>> On 14 Jan 2026, at 15:49, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>>>> >>>>>> Hi Quinn, >>>>>> >>>>>> Sounds good! I have just made the transfer, it should be on your account already. >>>>>> >>>>>> And yes, once the PR is merged I'll start a thread with the other devs to schedule the workshop. >>>>>> >>>>>> -- >>>>>> Xavier >>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>> >>>>>> On Tue, Jan 13, 2026, at 15:23, Tracestrack wrote: >>>>>>> Hi Xavier, >>>>>>> >>>>>>> The first 1 hour is mostly for administration and initial intake like understanding and setting up the project. This 22 hours is for actually solving the problem. So the total work is 1+22=23 hours. >>>>>>> >>>>>>>> Thank you for the update, and for getting everything ready in the PR! I haven't yet re-reviewed your latest work, but I will make sure to do that and to get the other devs to do another pass. I will also ask them for the workshop. >>>>>>> >>>>>>> Yeah I’ll be responsive to the PR and let’s arrange a time for the workshop! >>>>>>> >>>>>>> Best regards >>>>>>> Quinn >>>>>>> >>>>>>>> On 13 Jan 2026, at 15:16, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>>>>>> >>>>>>>> Hi Quinn, >>>>>>>> >>>>>>>> Thank you for the update, and for getting everything ready in the PR! I haven't yet re-reviewed your latest work, but I will make sure to do that and to get the other devs to do another pass. I will also ask them for the workshop. >>>>>>>> >>>>>>>> In any case I will send you the payment now. Does your second invoice include the 1h paid upfront or not? Ie is it 22h in total or 23h? >>>>>>>> >>>>>>>> -- >>>>>>>> Xavier >>>>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>>>> >>>>>>>> On Mon, Jan 12, 2026, at 21:26, Tracestrack wrote: >>>>>>>>> Dear Xavier, >>>>>>>>> >>>>>>>>> Best wishes for the new year! My work on the map rework is mostly done! >>>>>>>>> >>>>>>>>> The MRs are not merged yet but I believe there won’t be much work left. I’ve added a doc about how to test it: https://gitlab.com/whitebox-aero/whitebox/-/blob/4a8b59e4d997613e8229710842… >>>>>>>>> I’m sending the invoice therefore. The total amount is €3300 of 22 hours. In the invoice you can see where the time is spent. This is conclusive and won’t be more invoice. >>>>>>>>> >>>>>>>>> I will continue to follow up on the reviews and eventually get it merged. Let’s also schedule a demo and map styling workshop in the next two weeks if possible. I’m fine with recording. >>>>>>>>> >>>>>>>>> Looking forward to your feedback! >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> Quinn >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> On 29 Dec 2025, at 15:44, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>>>>>>>> >>>>>>>>>> Hi Quinn, >>>>>>>>>> >>>>>>>>>> Thanks for the update! We will be able to discuss the work on the MR, but definitely feel free to send me your invoice for the time spent so far. >>>>>>>>>> >>>>>>>>>> And sounds good for the workshop! Actually to have the maximum amount of people benefiting from it, if you are willing to record it as a screenshare video, we could add it to the project documentation for the styling of the maps. >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Xavier >>>>>>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>>>>>> >>>>>>>>>> On Tue, Dec 23, 2025, at 10:45, Tracestrack wrote: >>>>>>>>>>> Hey Xavier, >>>>>>>>>>> >>>>>>>>>>> Just to let you know I'll try to finish the work this week. I have solutions for individual problems (like generating contours and map cuts) and just need to put them together. I will send you a remaining invoice of 19 hours of work next year :) If you need a 30-minutes workshop about how to style the map it can also be arranged for free. >>>>>>>>>>> >>>>>>>>>>> Merry Christmas! >>>>>>>>>>> >>>>>>>>>>> Best regards >>>>>>>>>>> Quinn >>>>>>>>>>> >>>>>>>>>>>> On 3 Dec 2025, at 12:04, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Hi Quinn, >>>>>>>>>>>> >>>>>>>>>>>> Sounds good, thanks for letting me know! We will be reviewing this week, and you can follow-up on it when you're back from vacation, that works. I will also let you know about the next steps & scope - we will probably go for it, but I want to take a closer look before confirming. >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Xavier >>>>>>>>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>>>>>>>> >>>>>>>>>>>> On Tue, Dec 2, 2025, at 23:49, Tracestrack wrote: >>>>>>>>>>>>> Hey Xavier, >>>>>>>>>>>>> >>>>>>>>>>>>> Just to let you know I'll be on holiday from tomorrow to December 15. So I might not be able to handle the comments on time. >>>>>>>>>>>>> >>>>>>>>>>>>> The 10 hours work is mostly done for the PR I created. I’ll resolve any issues/comments from the PR within this timeframe. >>>>>>>>>>>>> >>>>>>>>>>>>> The remaining work are mentioned in https://gitlab.com/whitebox-aero/whitebox/-/issues/445#note_2922742233 , which I think needs another 5 to 10 hours. If you want me to do it, I’m happy to do it after my vacation! >>>>>>>>>>>>> >>>>>>>>>>>>> Best regards, >>>>>>>>>>>>> Quinn >>>>>>>>>>>>> >>>>>>>>>>>>>> On 27 Nov 2025, at 16:48, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Perfect, thank you Quinn! I have just sent the payment for the first invoice, it should be on your bank account. >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Xavier >>>>>>>>>>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Nov 27, 2025, at 15:22, Tracestrack wrote: >>>>>>>>>>>>>>> Hi Xavier, >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Please find the first invoice in the attachment. I’ve examined the whole project and got a clear picture. On Sunday I will finish the work and create a PR. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Best regards >>>>>>>>>>>>>>> Quinn >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On 25 Nov 2025, at 15:46, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Hi again Quinn, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Sure thing - here it is: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Flouzo d/b/a Whitebox >>>>>>>>>>>>>>>> 78 allée Primavera >>>>>>>>>>>>>>>> Centre Ubidoca, 7377 >>>>>>>>>>>>>>>> 74370 Annecy >>>>>>>>>>>>>>>> France >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> EU VAT: FR79500171566 >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Xavier >>>>>>>>>>>>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Tue, Nov 25, 2025, at 15:20, Tracestrack wrote: >>>>>>>>>>>>>>>>> Hi Xavier, >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Thanks. I'll put my comment and plan there. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> For starting the project, I'd like to charge 10% upfront (in this case 150 euro). Could you send me your billing info like VAT number if you have? Then I can create an invoice. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Best regards >>>>>>>>>>>>>>>>> Quinn >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On 25 Nov 2025, at 13:12, Xavier Antoviaque <xavier(a)whitebox.aero> wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Quinn, >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> I have posted a proper task about this here: https://gitlab.com/whitebox-aero/whitebox/-/issues/445 and copied our discussions about the approach there. The best would be to continue the discussion there - if you have further thoughts or questions from your exploration, can you post them there? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Then you can use the 10h to advance this task - when you get to 10h, you post what you have in a MR (a draft one if it's not 100% ready), and we rediscuss then? >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>>>> Xavier >>>>>>>>>>>>>>>>>> Whitebox.aero <https://whitebox.aero/> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, Nov 20, 2025, at 00:21, Tracestrack wrote: >>>>>>>>>>>>>>>>>>> Hi Xavier, >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Thanks for your inquiry! I can only provision limited amount of time on this project to help add the color relief, maybe also tune up the highway and place names. I need to check the current status first. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Looking at the code, it seems you are using vector maps with maplibre. I assume everything is set up and working. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> I think you don’t need contour lines or hillshades, which makes things easier. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> My rate for contracting work is 150 euro/hour. This work takes around 10 to 20 hours. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> If you want to do it yourself, you can refer to opentopomap as well: https://github.com/der-stefan/OpenTopoMap >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Let me know what you think! >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Best regards >>>>>>>>>>>>>>>>>>> Quinn >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On 19 Nov 2025, at 18:25, Xavier <donotreply(a)wordpress.com> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> *First name:* >>>>>>>>>>>>>>>>>>>> Xavier >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> *Last name:* >>>>>>>>>>>>>>>>>>>> Antoviaque >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> *Email:* >>>>>>>>>>>>>>>>>>>> xavier(a)whitebox.aero >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> *Message:* >>>>>>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> I'm one of the maintainers of the open source project Whitebox https://gitlab.com/whitebox-aero/whitebox - we would like to improve the rendering of the tiles we are currently displaying in the application. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Do you work with open source projects? In particular, if we contract you are you able to release the work you do (or reuse) under a copyleft license? Note that since our project needs to work without internet, the tiles are embedded and served locally. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> For what we would need: the project is used by pilots while flying, so it would be good to have a better showing of the topology than what we have now, to be able to better visualize the relief visually through colors, a bit like the rendering you showcase on https://www.openstreetmap.org/#map=10/41.4263/1.3225&layers=P -- but with less emphasis on the roads (which are useful visual landmarks, but much less important), and more on the airports and aerodromes. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Is this interesting to you? What would be your rates? >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> If so, happy to meet to discuss. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Xavier. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> View in dashboard <https://tracestrackmaps.wordpress.com/wp-admin/admin.php?page=jetpack-forms…> >>>>>>>>>>>>>>>>>>>> Time: November 19, 2025 at 6:25 pm >>>>>>>>>>>>>>>>>>>> IP Address: 🇪🇸 146.70.128.253 <https://jetpack.com/redirect/?source=ip-lookup&path=146.70.128.253> >>>>>>>>>>>>>>>>>>>> Browser: Firefox (Desktop) >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Source URL: https://tracestrack.com/contact/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Mark as spam <https://tracestrackmaps.wordpress.com/wp-admin/admin.php?page=jetpack-forms…> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Sent by an unverified visitor to your site. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Powered by Jetpack Forms <https://jetpack.com/forms/?utm_source=jetpack-forms&utm_medium=email&utm_ca…> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> *Attachments:* >>>>>>>>>>>>>>> • Invoice-0BDD53C6-0454.pdf >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> *Attachments:* >>>>>>>>> • Invoice-0BDD53C6-0487.pdf >>>>>> >>>> >>> >>

4 5

[update] 2026-02-19
by milos＠whitebox.aero 20 Feb '26

20 Feb '26

Heya, #498 - https://gitlab.com/whitebox-aero/whitebox/-/issues/498 Did a brief investigation of the reported issues and opened tickets. The new logs are super useful :D #492 - https://gitlab.com/whitebox-aero/whitebox/-/issues/492 Estimates pretty much done, to finish priorities and I'll post it up, tackling that first thing in the morning

1 0

2026-02-19 Update
by Avinash Sah 19 Feb '26

19 Feb '26

Hey, #484 https://gitlab.com/whitebox-aero/whitebox/-/issues/484 #477 https://gitlab.com/whitebox-aero/whitebox/-/issues/477 Reviewed. #492 https://gitlab.com/whitebox-aero/whitebox/-/issues/492 Reviewed tickets ahead of planning discussion. 0.alpha3 discussion recording: https://app.fireflies.ai/view/0-alpha3-discussion::01KHV08FG31WYQ2RW65Z0FCP… Thanks, Avinash S.

1 0

Your meeting recap - Sprint planning & retro - Whitebox
by Fred from Fireflies.ai 18 Feb '26

18 Feb '26

1 0

Fwd: [AbuseID:112DC0E:1F]: AbuseBSI: [CB-Report#20260211-10008626] Offene Redis-Server in AS24940
by Xavier Antoviaque 18 Feb '26

18 Feb '26

Milos, Avinash -- do we have a redis server that has open ports? If so, could you add a ticket to handle this (and properly setup the firewall on all our boxes to close all ports by default, unless we open them? -- Xavier Whitebox.aero <https://whitebox.aero/> On Wed, Feb 11, 2026, at 11:51, abuse(a)hetzner.com wrote: > Dear Mr Xavier Antoviaque, > > We have received a notification from the German Federal Office for > Information Security (BSI) for (the IP address of) a server you have > with us. We are automatically forwarding this notification on to you, > for your information. > > The original report has been included below. Additional information is > provided with the how-to guides referenced in the report. Please note > that we do not have any further information to share. > > These notifications do not mean your server was involved in any abusive > activity. They are simply alerting you to a potential issue on your > server, that could be exploited, and that is usually fairly easy to > secure. > > You do not need to send us, or the BSI, a response. > > In case of further questions, please contact certbund(a)bsi.bund.de and > keep the ticket number of the original report [CB-Report#...] in the > subject line. Do not reply to <reports(a)reports.cert-bund.de> as this is > just the sender address for the reports and messages sent to this > address will not be read. > > Kind regards > > Abuse Team > > Hetzner Online GmbH > Industriestr. 25 > 91710 Gunzenhausen / Germany > Tel: +49 9831 5050 > Fax: +49 9831 5053 > www.hetzner.com > > Register Court: Registergericht Ansbach, HRB 6089 > CEO: Martin Hetzner, Stephan Konvickova, Günther Müller > > You have the option of making an appeal against a negative decision. > To do that, please reply directly to this ticket. If this is the Abuse > Team’s final decision, you can also make a complaint by writing to > info(a)hetzner.com. The European Commission also provides a > platform that you can use as a platform for online dispute resolution > (ODR) at http://ec.europa.eu/consumers/odr. We are neither willing > nor required to participate in a dispute resolution process before a > consumer arbitration board. > > For the purposes of this communication, we may save some of your > personal data. For information on our data privacy policy, please see: > www.hetzner.com/privacy-policy-notice > >> Dear Sir or Madam, >> >> Redis is an open-source in-memory database server with a simple >> key-value data structure often used with dynamic web applications. >> >> If a Redis server is openly accessible from the Internet and no >> SASL authentification has been configured, anyone who can connect >> to the server has unrestricted access to the data stored with it. >> This allows attackers to modify or delete any data or potentially >> steal sensitive information like login credentials for web >> applications or customer data from online shops. >> >> Please find below a list of affected systems hosted on your network. >> The timestamp (timezone UTC) indicates when the system was found >> to be running an openly accessible Redis server. >> >> We would like to ask you to check this issue and take appropriate >> steps to secure the Redis servers on the affected systems or >> notify your customers accordingly. >> >> If you have recently solved the issue but received this notification >> again, please note the timestamp included below. You should not >> receive any further notifications with timestamps after the issue >> has been solved. >> >> Additional information on this notification, advice on how to fix >> reported issues and answers to frequently asked questions: >> <https://reports.cert-bund.de/en/> >> >> This message is digitally signed using PGP. >> Information on the signature key is available at: >> <https://reports.cert-bund.de/en/digital-signature> >> >> Please note: >> This is an automatically generated message. Replies to the >> sender address <reports(a)reports.cert-bund.de> will NOT be read >> but silently be discarded. In case of questions, please contact >> <certbund(a)bsi.bund.de> and keep the ticket number [CB-Report#...] >> of this message in the subject line. >> >> Affected systems on your network: >> >> Format: ASN | IP | Timestamp (UTC) | Redis version >> 24940 | 135.181.254.90 | 2026-02-10 10:35:10 | 8.4.0 >> >> Mit freundlichen Grüßen / Kind regards >> Team CERT-Bund >> >> Bundesamt für Sicherheit in der Informationstechnik >> Federal Office for Information Security (BSI) >> CERT-Bund >> Godesberger Allee 87, 53175 Bonn, Germany >>

3 5

[update] 2026-02-17
by milos＠whitebox.aero 18 Feb '26

18 Feb '26

Milos to ATC, #477 - https://gitlab.com/whitebox-aero/whitebox/-/issues/477 #484 - https://gitlab.com/whitebox-aero/whitebox/-/issues/484 Ready for review Cleared for takeoff

1 0

[update] 2026-02-13
by milos＠whitebox.aero 13 Feb '26

13 Feb '26

R2D2's *beep boop*, #383 - https://gitlab.com/whitebox-aero/whitebox/-/issues/383 #489 - https://gitlab.com/whitebox-aero/whitebox/-/issues/489 Reviewed #450 - https://gitlab.com/whitebox-aero/whitebox/-/issues/450 Merged hotfix in !218

1 0

2026-02-12 Update
by Avinash Sah 13 Feb '26

13 Feb '26

Hey, #383 https://gitlab.com/whitebox-aero/whitebox/-/issues/383 Fixed multiple bugs related to recovery from complete crashes; the implementation is now significantly more stable. #302 https://gitlab.com/whitebox-aero/whitebox/-/issues/302 Merged. https://gitlab.com/whitebox-aero/whitebox/-/merge_requests/217 CI fix investigated, implemented & merged. Thanks, Avinash S.

1 0

[update] 2026-02-12
by milos＠whitebox.aero 13 Feb '26

13 Feb '26

Heya, #476 - https://gitlab.com/whitebox-aero/whitebox/-/issues/476 Merged #477 - https://gitlab.com/whitebox-aero/whitebox/-/issues/477 Almost done with the tests, to be pushed to ready for review #450 - https://gitlab.com/whitebox-aero/whitebox/-/issues/450 Investigated some of the issues, opened a MR to fix the first issue - https://gitlab.com/whitebox-aero/whitebox/-/merge_requests/218

1 0

[update] 2026-02-11
by milos＠whitebox.aero 12 Feb '26

12 Feb '26

Heya, #302 - https://gitlab.com/whitebox-aero/whitebox/-/issues/302 #383 - https://gitlab.com/whitebox-aero/whitebox/-/issues/383 Reviewed #476 - https://gitlab.com/whitebox-aero/whitebox/-/issues/476 Fixed tests, to be merged

1 0