Etienne Stalmans

The change was activated on the 16th of October and recorded in the Heroku changelog: [https://devcenter.heroku.com/changelog-items/1488](https://devcenter.heroku.com/changelog-items/1488) The devcenter documentation has not been updated yet, but should be before too long.

@X-n3t @derazo1 have you tried without `--o365`? This is just a [short-cut to try autodiscover](https://github.com/sensepost/ruler/wiki#office365) directly against O365 instead of going through the usual path of company --> O365. Also...

Hi @ad0nis It is nearly impossible to figure out exactly what lead to this breakage, but it looks like the server responded with an empty NTLMv1 response. You can try...

hi @phonexicum Thanks for the report. Looks like there is an error being returned from the method but not being handled. The next line then tries to parse a non-existing...

Thanks for trying it out and the kind words @l0kihardt! It seems like the `ReadUnicodeString` bug might be playing a role in this bug report as well: https://github.com/sensepost/ruler/issues/121#issuecomment-633351036 I'll have...

Reading through this it looks like the `flag` bug was likely because of the `ReadUnicodeString` bug ``` } else if property.PropertyType == PtypString { trow.ValueArray, pos = utils.ReadUnicodeString(pos, resp) rows[k]...

Hi Based on your information above, it could likely be one of two things. First, you aren't using `--username` you might require this, either using the username or email address....

Hi, I believe this might be fixed in the new release, if you still have access to the environment, please give it a try.

@donjuanme a few thoughts, you might need to use both `--email` and `--username`. The other thing is to check `--domain` refers to the internal domain. So maybe it is `test`...

hey @petermolnar11 this is probably way too late, but have you looked at how I did this in Liniaal, where I never ran into this issue: https://github.com/sensepost/liniaal/blob/master/liniaal.go#L129-L167 hope that helps?