Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve LVM partitioning via Packer and on HVM #4

Open
konklone opened this issue Oct 21, 2014 · 5 comments
Open

Resolve LVM partitioning via Packer and on HVM #4

konklone opened this issue Oct 21, 2014 · 5 comments
Assignees

Comments

@konklone
Copy link
Contributor

Just noting that this is outstanding before we're good for production use.

@NoahKunin
Copy link
Contributor

From @arowla:

Resizing the available space on the attached EBS is not a straightforward task.... We need to add instructions to this effect:

  1. Use fdisk to delete /dev/xvdk4 and recreate using the full space.
  2. Use lvextend on the same.
  3. Run resize2fs on the mountpoint.

Until this is fully scripted, we should include this in the documentation somewhere in hardening.md

@seanherron
Copy link
Contributor

Suggest we attempt to descope this. I don't see a real security value given the cost and complexity.

@NoahKunin
Copy link
Contributor

Concur overall on cost-complexity vs security, but we can't de-scope it from the control list until I get concurrence from InfoSec. For nosuid and nodev in virtual IaaS I would concur immediately, but I'm not sure I have sufficient documentation (yet) to argue against noexec, especially in Moderate level production systems.

When @avriette returns (or any enterprising member of the public!), I'd love to get a proposal written up to formally de-scope.

I'm removing the backlog label now, because we don't know how long it will take to de-scope the control, and having this scripted out isn't too much work, and saves people time/pain in the interim. Doesn't mean we will complete it in this sprint or if it will flip to the next one, but de-scoping will not occur in Dec or in early Jan.

cc @ozzyjohnson for visibility.

@NoahKunin NoahKunin removed the Backlog label Dec 18, 2014
@ozzyjohnson ozzyjohnson self-assigned this Dec 18, 2014
@seanherron
Copy link
Contributor

🆗

@ozzyjohnson
Copy link
Member

Finally got around to this. See #28. There's a test AMI generated with these changes available internally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants