CyberArmy University | Open Source Institute | CyberArmy Intelligence & Security | CyberArmy Services & Projects

CAMS Stuff - Who wants to help with the protocol?



    CAMS Stuff - Who wants to help with the protocol? [View] [Reply] [Top]
    Posted by Gen parad0x On 2002-09-12 21:17:30
    So, CA is back up. No time to procrastinate anymore. No reason to anyways, we have a site again.

    CAMS had some steam awhile back, but now we need to get that ball rolling again. It's a big project and if we want it to go anywhere, we need to do something about it.

    So, I need to know, who wants to help set the protocol for the CAMS transactions. You don't need to be a networking genius or a spec ops member to specify, don't worry. However, you should have a general idea what a network protocol should be like. If you don't know right now but think you can get ready, then that's fine.

    I'll basically be setting up a CVS server we'll use to track this project, and I'm shortly going to re-enable my brigade and get things working. The brigade itself might move (spec ops has very restrictive membership rules), but I will make sure people who want to be on this project have that opportunity (within reason).

    CAMS is going to include:
    - A challenge based authentication system
    - A flexible protocol (versioning so we can upgrade it gracefully)
    - Several modes
    - Low overhead


    CAMS _may_ have:
    - A server based architecture
    - Strong crypto support
    - Puggable protocol support
    - Broadcast messages by group.

    So. You can email:
    dfayra00@umail.ucsb.edu

    With the string "CAMS:" at the start of the subject. ANY EMAILS WITHOUT THIS LINE WILL BE IGNORED! Please make my mail-filing life easy or I will ne a nazi about letting you in :)
     
      RE: CAMS Stuff - Who wants to help with the protocol? [View] [Reply] [Top]
      Posted by Ret. CinC Chawmp On 2002-09-12 21:44:04
      I regret that I expect to be too busy irl, from about now, to be able to participate in such a project any longer. But I will follow the development of the project, and offer any suggestions I have :)

      Can I recommend taking advantage of OSI's CVS hosting (I'm not sure if this is totally un and running yet, but it should definately be the first place to call), and a good way to help to promote OSI as well as CAMS.


      On 2002-09-12 21:17:30, parad0x wrote
      >So, CA is back up. No time to procrastinate anymore. No reason to anyways, we have a site again.
      >
      >CAMS had some steam awhile back, but now we need to get that ball rolling again. It's a big project and if we want it to go anywhere, we need to do something about it.
      >
      >So, I need to know, who wants to help set the protocol for the CAMS transactions. You don't need to be a networking genius or a spec ops member to specify, don't worry. However, you should have a general idea what a network protocol should be like. If you don't know right now but think you can get ready, then that's fine.
      >
      >I'll basically be setting up a CVS server we'll use to track this project, and I'm shortly going to re-enable my brigade and get things working. The brigade itself might move (spec ops has very restrictive membership rules), but I will make sure people who want to be on this project have that opportunity (within reason).
      >
      >CAMS is going to include:
      >- A challenge based authentication system
      >- A flexible protocol (versioning so we can upgrade it gracefully)
      >- Several modes
      >- Low overhead
      >
      >
      >CAMS _may_ have:
      >- A server based architecture
      >- Strong crypto support
      >- Puggable protocol support
      >- Broadcast messages by group.
      >
      >So. You can email:
      >dfayra00@umail.ucsb.edu
      >
      >With the string "CAMS:" at the start of the subject. ANY EMAILS WITHOUT THIS LINE WILL BE IGNORED! Please make my mail-filing life easy or I will ne a nazi about letting you in :)
       


CyberArmy::Forum v0.6
Generated In 0.01206 seconds


About Us | Privacy Policy | Mission Statement | Help