CIRCL
Master issue for TAUTO-3
Automatic testing of CIRCLean functionalities with a malicious sample Dataset
Tested on RPi2 Model B v1.1 as well, the 5/27/15 CIRCLean img does NOT working. Get a 'alsactrl store: save state 1608 error' and then all services start shutting down and app dies. Any help?
Could you give a try with this image: hXXps://www.circl.lu/assets/CIRCLean/2015-06-02_CIRCLean.img.gz (OLD)
sha256: c8e58491b93b5f0aca40e5ece775f6b63693ea87b2b6ed29eb6200e382e93564
It is a test image we never released officially, but working for sure on rpi2. The alsa error is very weird and I did not have that issue recently... You are using a stock unmodified rpi, right?
I reformatted an extra SD card, laid the image down using “dd linux” cmd with the image provided 2015-06-02.
Im getting the same “alsa error” then a msg that all services will shutdown and Pi unit shuts OFF(lights stop blinking).
If I swap in the original SD card with Debian image, I get a login cmd prompt to the Raspberry as usual and unit works fine.
Any recommendations on capturing a log to either forward to you all OR just review.
Regards…
JMC555
From: Raphaël Vinot [mailto:[email protected]] Sent: Friday, July 03, 2015 4:06 AM To: CIRCL/Circlean Cc: jmc555 Subject: Re: [Circlean] Master issue for TAUTO-3 (#23)
Could you give a try with this image: hXXps://www.circl.lu/assets/CIRCLean/2015-06-02_CIRCLean.img.gz (OLD)
sha256: c8e58491b93b5f0aca40e5ece775f6b63693ea87b2b6ed29eb6200e382e93564
It is a test image we never released officially, but working for sure on rpi2. The alsa error is very weird and I did not have that issue recently... You are using a stock unmodified rpi, right?
— Reply to this email directly or view it on GitHub https://github.com/CIRCL/Circlean/issues/23#issuecomment-118282104 . https://github.com/notifications/beacon/AMjO5yiZgkNOkvBkU35W_p0uKZsjQ_4eks5oZkfbgaJpZM4E-Lzm.gif
https://github.com/CIRCL/PyCIRCLean/blob/master/.travis.yml - https://github.com/ytisf/theZoo
Currently we run the PyCIRCLean code against theZoo during the Travis build, but we don't have a way to verify that the files are being identified as malicious. Ideally we'll soon have a way to identify a list of files + how they should be identified and then write tests that confirm the desired behavior.
