Andy Cobaugh wrote:
> On 2011-07-27 at 11:00, J.Lance Wilkinson ( [email protected] ) said:
>> I have a need to secure a COSIGN protected resource from a command line
>> (download a protected file).
...
>>
>> Suggestions? Code already available? Where to start with Roll My Own?
>
> # get your cookies
> curl -L -b /tmp/cookies.txt -c /tmp/cookies.txt https://yourcosignlogin.com
>
> # attempt to login
> curl -L -b /tmp/cookies.txt -c /tmp/cookies.txt
> https://yourcosignlogin.com/cosign.cgi \
> --data "login=username&password=password"
>
> # now access your protected site
> curl -L -b /tmp/cookies.txt -c /tmp/cookies.txt
> https://someothersite.com/pathtoresource
>
> I may be missing something, and it's been a while since I wrote this,
> but that's basically all our nagios check scripts do to check that our
> cosign login cgi is working and that a particular protected site is
> working correctly. You might have to change the GET variables as
> appropriate for your site. Bear in mind the usual security precautions
> about passing a password to a command like that or storing a password in
> a script.
THAT'S IT. Thanks, Andy.
--
J.Lance Wilkinson ("Lance") InterNet: [email protected]
Systems Design Specialist - Lead Phone: (814) 865-4870
Digital Library Technologies FAX: (814) 863-3560
E3 Paterno Library
Penn State University
University Park, PA 16802
------------------------------------------------------------------------------
Got Input? Slashdot Needs You.
Take our quick survey online. Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
Cosign-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cosign-discuss
