SecWG: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
← Older edit
Justinmorrison (talk | contribs)
Bureaucrats, confirmed, emailconfirmed
53 edits
VisualWikitext
mNo edit summary
Justinmorrison (talk | contribs)
Bureaucrats, confirmed, emailconfirmed
53 edits
mNo edit summary
 
(17 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Meetings ==
{{access}}
{{headerbox}}
Security Working Group works on access control.
*'''MAINTAINERS:''' {{:SecWG/Maintainers}}
{{boxend}}
{{recruiting}}


'''Thursday, May 1st, 7pm at Noisebridge.'''  @crw took a chat log on Slack (see [[SecWG_Meeting_Notes_2014_05_01]]).  Remote attendance was provided via Mumble.
We're working on [[Olympus]], the currently deployed door access system for the front door, with hopes to roll it out for separate rooms in the space, with access control delegated to other guilds.


Conclusions:
This group was formed in 2014 and made multiple other wiki pages over the years and [[272]] access is presently in a rebuilt form set up by Woz. We should collect current data and plans here.


* Narrowing scope of SecWG down to access control
=Current Project=
* possibly spinning up [[Docents]] again.
We're working on a new door access system, [[Olympus]], currently deployed for the front door, with plans to roll it out for separate rooms in the space, managed by guild.
* Setting up a kiosk at the front ([[User:Sid]] had started this)


==Project Strands==
* [[User:Solderfumesandtea|Daniel]] focuses on simplicity of this system. He took the initial lead in building this, writing code and assembling hardware.
* [[User:Mcint|Loren]] focuses on ensuring reliability & uptime of the system, and helping others to get involved, lend their own skills. He also wants to tie the system in with more general membership portals and bootstrap management enough to pass it off to others.
* [[User:Brennan nb|Brennan]] wants to build out the system to support Apple- & Google- -Wallet managed credentials.


'''Impromptu virtual meeting on Thursday, May 8th''', via mailing list, IRC, and Slack/#security-wg resulted in some nice [[AccessControlModeling]] and several mailing list threads.
==Peoples==
See [[SecWG/Maintainers]] for previous contributors.


Conclusions:  
==Outstanding Goals==
* Get Apple developer group account (free as nonprofit) for signing keys needed for deployment, or even TestFlight'ing. -> [[User:Mcint|Loren]] or [[Noisebridge:Treasurer]]/[[Noisebridge:Secretary]] action.
* Make repeatable units for other room.
* ''(Subtle, many implicit requirements, many possibilities, much effort)'' Design/write/'''prove''' simple syncing systems to support access control, offline concerns, privacy, non-impersonation.


* Let's install an RFID reader at the top of the stairs. Debate continues over whether to leave front gate setup alone, or to remove the keypad for entry.
=Timeline=
* Members and Associate Members would be entitled to an RFID entry badge. Debate over whether to allow all types of RFID cards so that ppl won't need a separate physical item (they can use their Clipper card).
* the RFID reader we have now -- does it work? We're not sure.
* keeping [[Docents]] running is at least "Very Hard" and may be "Impossible". Let's work on technological solutions to social problems first.
* Access control to the space != solving problems related to protecting property (theft, vandalism, etc) within the space. Totally separate conversation that will be had in the future.


==History==
Past working group notes can be found at [[SecWG/History]].


=== Agenda for Next Meeting ===


''Todo: set a meeting date/time -- week of May 12th is too busy for everyone involved.''
{{Category:WG}}


Meeting will be Mumble-accessible starting at $MEETING_TIME
[[Category:SecWG]]
 
[[Category:WG]]
* Getting an RFID reader installed on the NB door lock (i.e. not the gate, the door at the top of the stairs).
* What to do about the elevator, which is currently a "backdoor" to our physical security.  Suggestions include building new walls around that area (labor-intensive but doable) and hacking the elevator itself (has social capital issues b/c we'd have to convince the landlord).
* Should we install more lockers?
* (or) should we put up far more solid structure around the Member Shelves and then install an RFID (or other) lock there?
* any new discussion topics pertaining to threat modeling based on known Problems that NB regularly has.
 
== Peoples ==
 
*[[User:Nthmost|nthmost]]
*[[User:Thex|X]]
*[[User:yesac|Casey]]
*[[User:Crw]]
*[[User:Sid]]
* Adrian
* Schuyler
*[[User:mux]]
 
== Projects ==
* Alpha
* Beta
* Etc...

Latest revision as of 13:39, 13 December 2024

Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Stuff | Events | Projects | Meetings | Donate E
272 Capp St. | Layout | Exits | Bathrooms | Network | Audio | AV | Construction | Electrical | Storage

STREET | Patio | Parking | Fence | Access | Gate | Payphone | Doorbell | Back patio | Roof | Neighbors
DOWNSTAIRS | Entrance | Stairs | Roll up door | Front | Print Shop | Arcade | Cafe |
Hackitorium | Stage | Electronics Bench | Wood Shop | Back hall | Metal Shop | Back Stairs |
UPSTAIRS | Lounge | Music | Electronics | Classrooms | Lockers | Privacy Booth | Fire escape | Plants | Sustenance | Housekeeping

E
Access | Gate | Front Door | Doorbell | RFID Token | Payphone | Security Camera | SecWG | Olympus (Door) V · T · E


Security Working Group works on access control.

RECRUITING! Maintainer volunteers wanted, consider volunteering to become a maintainer. E

We're working on Olympus, the currently deployed door access system for the front door, with hopes to roll it out for separate rooms in the space, with access control delegated to other guilds.

This group was formed in 2014 and made multiple other wiki pages over the years and 272 access is presently in a rebuilt form set up by Woz. We should collect current data and plans here.

Current Project

We're working on a new door access system, Olympus, currently deployed for the front door, with plans to roll it out for separate rooms in the space, managed by guild.

Project Strands

  • Daniel focuses on simplicity of this system. He took the initial lead in building this, writing code and assembling hardware.
  • Loren focuses on ensuring reliability & uptime of the system, and helping others to get involved, lend their own skills. He also wants to tie the system in with more general membership portals and bootstrap management enough to pass it off to others.
  • Brennan wants to build out the system to support Apple- & Google- -Wallet managed credentials.

Peoples

See SecWG/Maintainers for previous contributors.

Outstanding Goals

  • Get Apple developer group account (free as nonprofit) for signing keys needed for deployment, or even TestFlight'ing. -> Loren or Noisebridge:Treasurer/Noisebridge:Secretary action.
  • Make repeatable units for other room.
  • (Subtle, many implicit requirements, many possibilities, much effort) Design/write/prove simple syncing systems to support access control, offline concerns, privacy, non-impersonation.

Timeline

History

Past working group notes can be found at SecWG/History.


About Working Groups

Category for Working Groups (WGs).

Working Groups maintain core functions of the space for the community, working "on the space", addressing enduring concerns of the space and space participants, and affecting participants who may not contribute to the WG, or many not be aware of it. By contrast, guilds focus on sharing knowledge and safe practice of a craft, "for guild participants, in the space".

Our working groups have goals they aim to achieve within the context of (at least) the makerspace's resources, wp:working group. In this usage, guilds harken back to mastery of a craft or trade in a certain area, wp:guild.

Working Groups should have

  • A wiki page to coordinate
    • With a place in the template hierarchy
    • With Slack and Discord channels
    • With Maintainers listed, ideally on a subpage, to support separate mw:Transclusion onto other pages.
    • A clear mission. And if applicable, goals to accomplish before disbanding.
    • A sponsoring Guild

Copy the source of this section into new WG pages, and gradually replace parts with appropriate information.

Or briefly, temporarily, transclude via {{:Category:WG}}

Previous related thinking documented as FractalWorkingGroup pattern proposal.


Retrieved from "https://main-wiki.extremist.software/index.php?title=SecWG&oldid=84952"