You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "phrocker (via GitHub)" <gi...@apache.org> on 2026/07/22 21:53:33 UTC
[I] Threat model [accumulo]
phrocker opened a new issue, #6489:
URL: https://github.com/apache/accumulo/issues/6489
**What is your question?**
Please consider asking your question on our mailing list or in our Slack channel, instead. See https://accumulo.apache.org/contact-us
I'm having to generate a threat model and I'm choosing to do so with OTM. Is this useful to the broader project? I don't want to create unnecessary churn but this is turning into something I have to do for my own purposes. Is this something that I should submit as PR here?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Threat model [accumulo]
Posted by "phrocker (via GitHub)" <gi...@apache.org>.
phrocker commented on issue #6489:
URL: https://github.com/apache/accumulo/issues/6489#issuecomment-5148587691
That's reasonable. I believe a follow up would be to submit a pr and ask @DomGarguilo review , but I would submit a follow up issue in doing so. I have a threat model I've generated for my branched project so I will pull that apart and submit in more manageable chunks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Threat model [accumulo]
Posted by "ctubbsii (via GitHub)" <gi...@apache.org>.
ctubbsii commented on issue #6489:
URL: https://github.com/apache/accumulo/issues/6489#issuecomment-5148047121
Since this issue could be interpreted as a somewhat open ended discussion, I'm going to close this as fixed by #6490, so we don't keep issues unresolved indefinitely. But, if there's more discussion warranted, we can discuss on the mailing list, or if there's an additional concrete proposal, a PR could be proposed for review.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Threat model [accumulo]
Posted by "ctubbsii (via GitHub)" <gi...@apache.org>.
ctubbsii commented on issue #6489:
URL: https://github.com/apache/accumulo/issues/6489#issuecomment-5052576377
What is OTM? Some projects are creating a SECURITY.md file for their projects, to help explain their security model to get more helpful bug reports (either manually, or AI-assisted). I think it would benefit our project to have some kind of file like that. But, I suspect we'd have to iterate on the contents of the file a bit. You could start with a draft PR and then post on the dev list to point people to it to discuss. I could be wrong, but I thought @DomGarguilo might have started looking into this, but I don't know if he's made any progress.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Threat model [accumulo]
Posted by "DomGarguilo (via GitHub)" <gi...@apache.org>.
DomGarguilo commented on issue #6489:
URL: https://github.com/apache/accumulo/issues/6489#issuecomment-5059048817
> I could be wrong, but I thought [@DomGarguilo](https://github.com/DomGarguilo) might have started looking into this, but I don't know if he's made any progress.
I was gauging interest in the idea. I have not started on anything concrete. If someone else has interest/experience I am happy let them handle things since I don't have any experience and am not sure what is best practice here.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Threat model [accumulo]
Posted by "ctubbsii (via GitHub)" <gi...@apache.org>.
ctubbsii closed issue #6489: Threat model
URL: https://github.com/apache/accumulo/issues/6489
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Threat model [accumulo]
Posted by "dlmarion (via GitHub)" <gi...@apache.org>.
dlmarion commented on issue #6489:
URL: https://github.com/apache/accumulo/issues/6489#issuecomment-5090952341
Added SECURITY.md in #6490
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] Threat model [accumulo]
Posted by "ctubbsii (via GitHub)" <gi...@apache.org>.
ctubbsii commented on issue #6489:
URL: https://github.com/apache/accumulo/issues/6489#issuecomment-5148754125
I'm not sure if I understood you correctly, but in case you planned on creating both an issue and a PR at the same time, please only create the PR unless an issue is required for one of:
* detailing planned future work for which a PR is not immediately forthcoming, or
* coordinated tracking of multiple tasks (if the tasks are long-running, consider using a project instead)
There may be other scenarios where an issue is useful in addition to a PR, but generally, it's just redundant. I'm only mentioning this because sometimes people who aren't very active here (or newcomers) sometimes bring along practices from other projects that are very highly redundant (like some projects create a basically blank issue for every separate PR, and that's not at all useful; so we try to discourage that in this project).
But, if all you meant was that the PR you'd be making would be follow-on to this, that's fine, please disregard my response 😺
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@accumulo.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org