---Challenges:- Body: | -- Alert -- Welcome to Geegle, we appreciate holidays. Here's a magic trick, can you figure out how it's done? Details: https://magic.corp.geegle.org Please do not reply to this email. Delay: 100000 DependsOnPoints: 1 Sender: alerts@geegle.org Title: "[Do Not reply] Holiday Season"- Body: | Welcome to Geegle! We're so happy you've decided to become a Geegler and join our family of developers, writers, creators and wizards! This is your Geegle inbox - you'll interact with most of our services through here (and get important updates from us!). This is still a testing version, so if you find anything juicy, please send it to flag@geegle.org for us to take a look at! We may reward you for finding something interesting. We would also like to tell you that wer're rating our new staff based on what they find! If you want to see how you're doing, jump on to https://scoreboard.corp.geegle.org. So what are you waiting for, get into it! Warm Thanks, Geegle HR Delay: 0 DependsOnPoints: 1 Sender: hr@geegle.org Title: Wecome to Geegle!- Body: | Welcome to Geegle Newsletter! We work to send out a newsletter every so often to make sure that all our Geeglers are up to date with everything going on at Geegle. This is issue 0x01, our introductory edition. Light on content and easy to read, just the way everyone likes newsletters. The big news for this newsletter is our brand new zero-trust network. This is a brand new way of enterprise security, courtesy of Geegle. Essentially, nothing on the Geegle intranet is trusted, and every connection between Geegle services go through an access-control proxy called Uberproxy. On Uberproxy, we do centralized authentication, logging, tracing, etc. This practice was actually first introduced by our competitor Google via their BeyondCorp model. It's also worth noting that we are rolling out our brand new CLI-Relay infrastructure. To use any Geegle-internal commandline apps, you no longer need to connect via nc or telnet. Instead, even CLI apps traffic now go through Uberproxy, powered by websocket. We realise new things might be hard to use for some geeglers, so here's some instructions:

You can interact with the CLI app by sending and receiving commands through the CLI web interface.
Alternatively, we also provide a `cli-relay` program that you can download. With it, you can use the CLI app as if it's a local binary. You will need to provide your uberproxy cookies to the binary. See web interface for more information.
If you are a Geegler with code access, the CLI-Relay web interface is also integrated with our internal monorepo Geegle3. So you might be able to download the CLI binary, source code, or libraries directly on the web interface. Just follow the instructions on the page.

That's all for this edition, enjoy! Thats a wrap, Geegle Newsletter Delay: 300000 DependsOnPoints: 1 Sender: Geegle-Newsletter@geegle.org Title: Geegle News 0x01- Body: | Welcome to Geegle Newsletter! Welcome to the CTF edition of the newsletter! We wanted to share some things we always notice in CTF's so you watch out for them whenever you play! There's always one of these...

So you better be ready for it! There's hidden flags:

And... Someone tries to be funny and attack the CTF infrastructure

So yeah, I bet you can't wait to see all of that sometime soon! Thats a wrap, Geegle Newsletter Delay: 2400000 DependsOnPoints: 1 Sender: Geegle-Newsletter@geegle.org Title: Geegle News 0x02- Body: | Welcome to Geegle Newsletter! In edition 0x03, we have some fun testing info. We promise it's nothing to do with anything important, just a chance to learn something new.

Testing on the Toilet

Only Verify State-Changing Method Calls

Method calls on another object fall into one of two categories:

State-changing: methods that have side effects and change the world outside the code under test, e.g., sendEmail(), saveRecord(), logAccess().
Non-state-changing: methods that return information about the world outside the code under test and don't modify anything, e.g., getUser(), findResults(), readFile().

You should usually avoid verifying that non-state-changing methods are called:

It is often redundant: a method call that doesn't change the state of the world is meaningless on its own. The code under test will use the return value of the method call to do other work that you can assert.
It makes tests brittle: tests need to be updated whenever method calls change. For example, if a test is expecting mockUserService.isUserActive(USER) to be called, it would fail if the code under test is modified to call user.isActive() instead.
It makes tests less readable: the additional assertions in the test make it more difficult to determine which method calls actually affect the state of the world.
It gives a false sense of security: just because the code under test called a method does not mean the code under test did the right thing with the method's return value.

Instead of verifying that they are called, use non-state-changing methods to simulate different conditions in tests, e.g., when(mockUserService.isUserActive(USER)).thenReturn(false). Then write assertions for the return value of the code under test, or verify state-changing method calls.

Verifying non-state-changing method calls may be useful if there is no other output you can assert. For example, if your code should be caching an RPC result, you can verify that the method that makes the RPC is called only once.

That's much simpler! But remember that instead of using a mock to verify that a method was called, it would be even better to use a real or fake object to actually execute the method and check that it works properly. For example, the above test could use a fake database to check that the permission exists in the database rather than just verifying that addPermission() was called.

https://pasteweb.corp.geegle.org/paste/990a96f3-4224-452f-9183-da5dbb9477eb

https://who-is-attacking-me.corp.geegle.org

https://game.corp.geegle.org

https://geelang.corp.geegle.org

https://intern-project.corp.geegle.org

https://payroll.corp.geegle.org

https://shell.corp.geegle.org

https://tellgeegle.corp.geegle.org

https://docs.corp.geegle.org

https://employees.corp.geegle.org

https://flatearth.corp.geegle.org

https://guest.corp.geegle.org/

https://seclearn.corp.geegle.org