ravthan all-eyes issues

ravthan / all-eyes

Automatically exported from code.google.com/p/all-eyes

0 stars 0 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Add the capability to remove ae user accounts and authorizations

#131 GoogleCodeExporter opened 8 years ago
0
Make sure isDuplicateMsg is protected by mutex lock

#130 GoogleCodeExporter opened 8 years ago
0
"scan-build -V --use-cc=/usr/bin/clang make" in src/ae/daemon exposed bug in aemsg.c:119

#129 GoogleCodeExporter closed 8 years ago
2
Android static code analysis results

#128 GoogleCodeExporter opened 8 years ago
1
Further Valgrind, fuzzing test results

#127 GoogleCodeExporter closed 8 years ago
1
fuzzing - can send more then msgid upto 32 characters

#126 GoogleCodeExporter closed 8 years ago
1
fuzzing valgrind run - android App crashes

#125 GoogleCodeExporter closed 8 years ago
2
fuzzing - valgrind & Android App combo problem

#124 GoogleCodeExporter closed 8 years ago
2
fuzzing bug - can send the monitor message with same ID - with different events

#123 GoogleCodeExporter closed 8 years ago
3
valgrind output - 'ae' daemon, filemon, filedescriptormon, selfmon, socketmon, procmon running

#122 GoogleCodeExporter closed 8 years ago
3
fuzzing-bug discovery - Denial of Service attack resolved using timeout

#121 GoogleCodeExporter closed 8 years ago
2
create_checksum_filemon may have command injection in call to sha256sum

#120 GoogleCodeExporter closed 8 years ago
5
calChecksumFilemon may have command injection in call to sha256sum

#119 GoogleCodeExporter closed 8 years ago
5
isHeartBeatMsg may have a buffer overflow

#118 GoogleCodeExporter closed 8 years ago
1
Change in the flow of heartbeat messages

#117 GoogleCodeExporter closed 8 years ago
3
Normalize max message length

#116 GoogleCodeExporter closed 8 years ago
1
Module monitormgmt.c, function processMonitorMsg - Possible extra characters

#115 GoogleCodeExporter closed 8 years ago
1
Module aemgrmgmt.c, function aeMgrMgmt - handling failure to start

#114 GoogleCodeExporter closed 8 years ago
1
Monitor Message validation handling

#113 GoogleCodeExporter closed 8 years ago
2
Module selfmon.c, Function selfmonResponse

#112 GoogleCodeExporter closed 8 years ago
2
Module selfmon.c buffer size

#111 GoogleCodeExporter closed 8 years ago
1
aescrypt.c potential vulnerabilities

#110 GoogleCodeExporter closed 8 years ago
3
Module aemsg.c, function aemsg.c uses strcpy

#109 GoogleCodeExporter closed 8 years ago
3
Alternative Notifications

#108 GoogleCodeExporter closed 8 years ago
5
Modify chkAeMsgIntegrity to handle MSG_TRAILER as it handles AE_MSG_HEADER

#107 GoogleCodeExporter closed 8 years ago
2
Denial of service concern with SSL-client limitation.

#106 GoogleCodeExporter closed 8 years ago
5
procmon.pl recommend using Proc::ProcessTable instead of parsing ps output

#105 GoogleCodeExporter closed 8 years ago
1
sha256check assumes that sha256sum returns valid hash sum

#104 GoogleCodeExporter closed 8 years ago
3
Running sha256check w/o arguments yield no usage info.

#103 GoogleCodeExporter closed 8 years ago
1
Test of Submitting Bug

#102 GoogleCodeExporter closed 8 years ago
1
It looks like the ae daemon alwasy fails to match the event message in order to take the action

#101 GoogleCodeExporter closed 8 years ago
3
Errors in ae daemon as a result of changing the timestamp to microseconds

#100 GoogleCodeExporter closed 8 years ago
2
Possible Denial of service attack - by design as explained in issue #98

#99 GoogleCodeExporter closed 8 years ago
0
Limitation of Monitor event cache size

#98 GoogleCodeExporter closed 8 years ago
2
The file descriptor monitor is not creating properly formatted timestamp in the message id

#97 GoogleCodeExporter closed 8 years ago
5
The file monitor is not creating properly formatted timestamp in the message id

#96 GoogleCodeExporter closed 8 years ago
4
The size of the timestamps in the message ids is not consistent across languages

#95 GoogleCodeExporter closed 8 years ago
6
AeProxy and the AeManager should check the timestamps defined in the message ids

#94 GoogleCodeExporter closed 8 years ago
2
Need to turn on the AppArmor inside the chroot jail

#93 GoogleCodeExporter closed 8 years ago
3
incorrect time used in some monitors - which timezone is used?

#92 GoogleCodeExporter closed 8 years ago
4
possible memory leak

#91 GoogleCodeExporter closed 8 years ago
2
security risk - there is no non-repudiation - mitigation is issue #7

#90 GoogleCodeExporter closed 8 years ago
4
'ae' daemon Privilege violation of operating with least privilege

#89 GoogleCodeExporter closed 8 years ago
5
The filemon and filedescr monitors buffer size might cause bufferoverflow

#88 GoogleCodeExporter closed 8 years ago
2
Still Replay attack is possible

#87 GoogleCodeExporter closed 8 years ago
5
Change the word "Halt" to "Log Message" on the Android display screen

#86 GoogleCodeExporter closed 8 years ago
1
Change the actions in the AeManager to align with the redefined actions in the ae daemon

#85 GoogleCodeExporter closed 8 years ago
3
Add a write lock to the AeConnector's write method

#84 GoogleCodeExporter closed 8 years ago
2
Ubuntu statically linking false warning

#83 GoogleCodeExporter closed 8 years ago
0
If monitors send duplicate message, restart it.

#82 GoogleCodeExporter closed 8 years ago
2