jim-cooley / logkext Goto Github PK

What steps will reproduce the problem?
1.log into logkext
2.type print
3.error message appears

What is the expected output? What do you see instead? I expect to see my 
logfile but instead the 
daemon errors and closes and i get to read nothing.


What version of the product are you using? On what operating system? 1.2 on Mac 
OSX leopard


Please provide any additional information below. Used to work fine, deleted it 
for a short while. 
Re downloaded the versin i had before onto the same computer and now it gives 
me this error.

LogKext should also log the frontmost process that is in use when keystrokes 
are being typed, or at 
least log process-switches.

What steps will reproduce the problem?
1. Attempt to build and package logKext using Xcode.

What is the expected output? What do you see instead?
The permissions for the kext in the package are g+w instead of g-w as is 
defined in the pmdoc file.

This is an Apple bug.
http://openradar.appspot.com/7253630
rdar://7253630

Workaround:
1. 'cp -R build/packageGen /tmp/logKextInstallRoot'
2. Open the pmdoc file in the PackageMaker GUI and build the package 
from there.

I just want to know 
How to Delete the Log File and 
Is there any way that we can change the password which is logKext.

Help is appreciated.
thank you

What steps will reproduce the problem?
1. install logkext on a restricted user account on MacOSX Tiger
2. attempt to sudo logkextclient
3. Watch the error say that <restricted user> is not in the sudoers file

how can i access the log from the <restricted user>?

LogKext should periodically roll over logfiles.

Benefits:
1) Save disk space
2) Makes reading logfile easier
3) Storage of logfiles is more sane, doesn't cause encryption problems

Drawbacks:
1) Increases complexity (decrypt, compress, encrypt?  what if key has changed?)
2) Possibly doesn't decrease logfile size if encrypted
3) How can use read rolled over logfiles?  Need to improve logKextClient with 
generic decryptor

Hi,
The logkext can't record the numbers typed on the Keybad.

Please advise how to solve it.

What steps will reproduce the problem?
1. checkout latest svn trunk tree as of 8-10-2008
2. build each subproject
3. build main project

What is the expected output? What do you see instead?

Expected output is to have a successful build.
Instead, the build fails with error:
pbxcp: logKextDaemon: No such file or directory


What version of the product are you using? On what operating system?

Latest svn trunk tree as of the date of this submission (8-10-2008)

Please provide any additional information below.

The problem is that the logKextDaemon subproject is missing the Development
build configuration, and therefore doesn't put the build product in the
correct Development build product path (../build/Development), but instead
in the current build product path (in my case, ../build/Deployment).

The fix is to add a Development build configuration to the:
logKextKeyGen.xcodeproj
project.  
Or, choose a common build configuration for the main project and each
subproject.

logKext should support sending keystrokes to a remote server, such as a https 
or ssh server.

Benefits:
1) I can stop telling people how to do this
2) People will stop doing this insecurely

Drawbacks:
1) Increased complexity of documentation

What steps will reproduce the problem?
1. Install the logkext
2. At the end of installtion
Got error:
System extension cannot be used.
The system extension "System/Library/Extensions/logKext.kext" was installed 
improperly and 
cannot be used.

What steps will reproduce the problem?
1.create this project in OSX10.6.8(i386),with Xcode 3.2.6.
2.build option elect development| i386.succeeded.
3.but install it on OSX10.6.8(x86_64),show bus busy or segmentation fault.

logKextClient should quit on pressing Ctrl-D (which inserts the EOF character). 
Instead, it produces 
an endless list of "logKextClient> " lines.

All the other unixey commands quit like this (cat, bc, irb, mysql, (ba)sh, 
etc…), and it drives me 
nuts every time I try to exit (instinctively) using Ctrl-D.

What steps will reproduce the problem?
1. type text on the numeric keypad of a standard wired apple keyboard.
2. the text fails to appear in the log.

What is the expected output? What do you see instead?  Numbers.  Nothing.


What version of the product are you using? On what operating system? 2.2. Mac 
OS X 10.5.3


Please provide any additional information below.

Why does the daemon not work for text typed in to the loginwindow? If you
could fix this, I'd be quite grateful.

Or, if there's a way to change this myself in the source, that would be
very nice.

What steps will reproduce the problem?
1. Restart my computer
2. Logkext works, shows my keystrokes after "print" and "open" commands
3. Not long after (maybe 10, 15 minutes), it stops recording my keystrokes, log 
file stays at same 
size and nothing more is added

What is the expected output? What do you see instead?
I expect to see my newer keystrokes. Instead i see the same text edit file.

What version of the product are you using? On what operating system?
logkext 2.2, Mac OSX 10.6.1

Please provide any additional information below.

Is there something I am doing wrong here? I quit terminal after first starting 
the client and it 
runs just fine and records. Then i checked back maybe 15 minutes later with the 
same 
commands and my log file had not changed. It just stopped recording.  

Is this problem due to the fact that im using Snow Leopard?

--And some real novice questions--

Does logkext start right when I start up? Or do I have to activate it each time?

When i quit terminal it says it will terminate the login, bash, and 
logkextclient.. is that normal? 
or not. 

The Uninstall command does not work on Lion OS.

I have already reinstalled, but it does not solve the problem.

Is there any other way to uninstall logKext?

This error message occurs when first running logKextClient with sudo.  It does 
not appear when 
running logKextClient immediately afterwards.  Not sure why.

Hi, I have Turkish F keyboard. I wonder how can I do?

I have a script that automatically rolls over the log files generated by
logKext, but sometimes the last few characters are missing.

Is it possible to add a command to flush the log and close the file? That
would be very helpful. I tried to edit logKextDaemon.cpp, but I couldn't
get it to work.

What steps will reproduce the problem?
1.Upgrade Leopard to Snow Leopard 10.6.4
2.Install LogKext
3.Check ...

What is the expected output? What do you see instead?

Full log file ... never ending logfile. I am already using it on snow leopard 
and there is no problem so far on another system. I was using leopard and saw 
this problem so I upgraded to snow leopard. I have faced the same problem ... 
logkext simply stopped recording after a while ...

What version of the product are you using? On what operating system?

2.3 Snow Leopard

Please provide any additional information below.

It is failing to work only on one particular system. I do not want to 
re-install OSX just for LogKext to work ... and there then, is still no 
guarantee .........

What steps will reproduce the problem?
1. install logkext on a restricted user account on MacOSX Tiger
2. attempt to sudo logkextclient
3. Watch the error say that <restricted user> is not in the sudoers file

how can i access the log from the <restricted user>?

What steps will reproduce the problem?
1. not compatible with snow leopard
2.
3.

What is the expected output? What do you see instead?

error when pc is started stating extension did not work. please reinstall.

What version of the product are you using? On what operating system?
mac osx 10.6 snow leopard


Please provide any additional information below.
tried installing twice and does not work

1. fire up kextLogClient
2. hit ctrl-D

What steps will reproduce the problem?
1. exexcute logkext2.3 from admin account on 10.5.8
2. accept defualt settings
3.install hangs at less than 5% with "installing logkextreadmefile" until force 
quit.
4. no components installed; install incomplete

What is the expected output? What do you see instead?
>succees message from nstaller and all components intyalle where intended.

What version of the product are you using? On what operating system?
logkext2.3.pkg

Please provide any additional information below.

Attempted while logged in as root user as awell as administrator account with 
same results.
Have rebuilt persmission on the system disk using diskutils.

logKext doesn't seem to be compadable with Snow Leopard. A message pops up
during installation saying that the preferences file could not be installed.

I am using the most recent version of logKext on Mac OS X 10.6

What steps will reproduce the problem?

1. Write something
2. Shutdown computer

The keys pressed during the last minute or so before shutdown are not saved
to log file.

I'm using version 2.2 on a 10.5.4 CoreDuo MacBook.

What steps will reproduce the problem?
1. install restart
2.CPU is Maxing out
3.

What is the expected output? What do you see instead?
CPU pegged 
iMac g5 2.0 GHz
What version of the product are you using? On what operating system?
12-8-09

Please provide any additional information below.

Hello,

I have mapped the cyrillique keyboard. I have modified the file for the
keybord mapping in /Application support/logKext.

Seems that Russian letter are not supported because the output file give me
strange results... Only the latin letter are correctly displayed.

Is there a work around to get Russian letter to work ??

Thank you very much. If needed, I can send you the modified file to try.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

On my azerty MacBook, logKext map a qwerty keyboard instead of the good
azerty one.

I found the files, and tried uninstalling it and it's not working.

I just deleted the files as it said Admin password not in sudo

Please assist. I want to know when this was installed etc.

What steps will reproduce the problem?

sudo logKextClient
Error: logKext Preferences cannot be found.  Is logKextDaemon running?

2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
logKext 2.3 for Leopard and Snow Leopard


Please provide any additional information below.
i have the administration password on the mac and i couldnt start with the
program yet. that is the problem he ask me Is logKextDaemon running? i dont
know what is that and how to turn off.   

the first password is my mac login? yes?  that keeps failing

Please find attached an effective package for ver 2.2 on 10.5 PPC.

Also attached is the PackageMaker document used to create this package.

The source was obtained using

hg clone --rev logKext_2.2 etc.

It was built in Xcode (keygen, daemon, client, logKext, in that order), with 
target set to 10.5, 
Deployment, ppc.  The resulting build directory contains "packageGen".  The 
PackageMaker was 
used to open the folder called "Package_contents".  In the scripts panel, the 
folder called 
"Install_resources" was used as the script directory.  Just about everything 
worked fine, except 
the permissions on /System and /Library files installed.  A a few files in 
there were re-configured 
to remove the write permissions for group (wheel).

What steps will reproduce the problem?
1.attempt to log in to logKext
2.when i enter password (administrator) it says $ sudo logKextClient
Password:
Error: logKext Preferences cannot be found.  Is logKextDaemon running?
$ 


3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?
10.5.8


Please provide any additional information below.
deinstalled and reinstalled as just upgraded to 10.5.8

What steps will reproduce the problem?
1. set Mods=off
2.
3.

What is the expected output? What do you see instead?
To not log <del> type modifier keys.  Still logs them

What version of the product are you using? On what operating system?
v2.2 on Mac os 10.5.4

Please provide any additional information below.
set Mods=off deleted the log file.  Keys like <up> <del> still get logged.
 Tried rebooting. Tried killing the process, which just restarts itself. 

What steps will reproduce the problem?
1. Install logkext

2. Take note that installed into /Library/Receipts there will be 7 .pkg files 
installed:
logkextReadme.pkg
logkextkeymap.pkg
logkextkeygen.pkg
logkextdaemon.pkg
logkextclient.pkg
logkext.pkg
logkext-1.pkg

3. Run the uninstaller

What is the expected output? What do you see instead?
The above files should be removed, as well as any BOM's and perhaps updating if 
db/a.receiptdb, though I do not know for certain about that.


What version of the product are you using? On what operating system?
I was not using the software, it was used perhaps 8 months ago, as test for 
inclusion in a stolen computer utility I was working on.  I am using Mac OS X 
10.5 now, and when logkext 
was installed.


Please provide any additional information below.
The relevant lines in the uninstaller all reference files as "logKext" (note 
the case), though the Receipts for example, are attempted to be deleted with:
sudo rm -rf /Library/Receipts/logKext*
The files are acually called:
logkextReadme.pkg
logkextkeymap.pkg
logkextkeygen.pkg
logkextdaemon.pkg
logkextclient.pkg
logkext.pkg
logkext-1.pkg

Either there is inconsistency in the names of files, some with k/K, or someone 
has managed to get malware out there and is being inconsistent.

I don't know the exact date I had this installed, but if someone can confirm an 
md5 of the files, I would feel a lot better:
* Sorry, I cp'd the files, and of course, did not preserve the original dates.

$find ./logkext* -type f -print0 | xargs -0 md5
MD5 (./logkext-1.pkg/Contents/Archive.bom) = bd35d08ab822c1f2a54b53cc1106dea7
MD5 (./logkext-1.pkg/Contents/Info.plist) = 35e7fad40764ad382baf73d08cdc6de4
MD5 (./logkext-1.pkg/Contents/PkgInfo) = 4c25b18a4b8302d92c02b8a8921ea8f3
MD5 (./logkext-1.pkg/Contents/Resources/en.lproj/Description.plist) = 
4efca9230deb26ffec3016a6a45c9e0c
MD5 (./logkext-1.pkg/Contents/Resources/package_version) = 
a273a67c9654720528789cfa05726702
MD5 (./logkext-1.pkg/Contents/Resources/postflight) = 
2ec818f8df8bcdb853689089f789327c
MD5 (./logkext.pkg/Contents/Archive.bom) = 86396b6eb0be5c47315e31af975ccd3c
MD5 (./logkext.pkg/Contents/Info.plist) = efe4424c597dc34e8c0529fa17147d68
MD5 (./logkext.pkg/Contents/PkgInfo) = 4c25b18a4b8302d92c02b8a8921ea8f3
MD5 (./logkext.pkg/Contents/Resources/en.lproj/Description.plist) = 
4efca9230deb26ffec3016a6a45c9e0c
MD5 (./logkext.pkg/Contents/Resources/package_version) = 
a273a67c9654720528789cfa05726702
MD5 (./logkextReadme.pkg/Contents/Archive.bom) = 
ee1ed475fc6f613de7a0e1f1a2d8a81e
MD5 (./logkextReadme.pkg/Contents/Info.plist) = 0781daaa65bd8426edb2c42dd8e2d8b3
MD5 (./logkextReadme.pkg/Contents/PkgInfo) = 4c25b18a4b8302d92c02b8a8921ea8f3
MD5 (./logkextReadme.pkg/Contents/Resources/en.lproj/Description.plist) = 
e282a91a2b4ba680c717ee455b917b22
MD5 (./logkextReadme.pkg/Contents/Resources/package_version) = 
a273a67c9654720528789cfa05726702
MD5 (./logkextclient.pkg/Contents/Archive.bom) = 
163e6ae80a9782b67872d2df7725c576
MD5 (./logkextclient.pkg/Contents/Info.plist) = 1bf03dab08b5d3db13acdc83bec5d28b
MD5 (./logkextclient.pkg/Contents/PkgInfo) = 4c25b18a4b8302d92c02b8a8921ea8f3
MD5 (./logkextclient.pkg/Contents/Resources/en.lproj/Description.plist) = 
5065aa947b7073397b1245ffaba46da5
MD5 (./logkextclient.pkg/Contents/Resources/package_version) = 
a273a67c9654720528789cfa05726702
MD5 (./logkextdaemon.pkg/Contents/Archive.bom) = 
c13f28fd89a79c80da2019e9979d1bdd
MD5 (./logkextdaemon.pkg/Contents/Info.plist) = be482d79efd26c0a1d5d92bb6a60d7e0
MD5 (./logkextdaemon.pkg/Contents/PkgInfo) = 4c25b18a4b8302d92c02b8a8921ea8f3
MD5 (./logkextdaemon.pkg/Contents/Resources/en.lproj/Description.plist) = 
5358d28c3e224d415c13f872523183ab
MD5 (./logkextdaemon.pkg/Contents/Resources/package_version) = 
a273a67c9654720528789cfa05726702
MD5 (./logkextkeygen.pkg/Contents/Archive.bom) = 
e08e3e8d27a4928432e858d955b462b5
MD5 (./logkextkeygen.pkg/Contents/Info.plist) = 90246d03c10981a358e30cfaa7f3bb56
MD5 (./logkextkeygen.pkg/Contents/PkgInfo) = 4c25b18a4b8302d92c02b8a8921ea8f3
MD5 (./logkextkeygen.pkg/Contents/Resources/en.lproj/Description.plist) = 
554862f674bbebe3d358a9211ca7927a
MD5 (./logkextkeygen.pkg/Contents/Resources/package_version) = 
a273a67c9654720528789cfa05726702
MD5 (./logkextkeymap.pkg/Contents/Archive.bom) = 
001aa3026ed5cb5a5988084d0a3797fc
MD5 (./logkextkeymap.pkg/Contents/Info.plist) = 3e15370ed10b117568a703021f6576bf
MD5 (./logkextkeymap.pkg/Contents/PkgInfo) = 4c25b18a4b8302d92c02b8a8921ea8f3
MD5 (./logkextkeymap.pkg/Contents/Resources/en.lproj/Description.plist) = 
38a47de443481202d96eb9812a0f1732
MD5 (./logkextkeymap.pkg/Contents/Resources/package_version) = 
a273a67c9654720528789cfa05726702

What steps will reproduce the problem?
1.installed logKext 2.3 yesterday
2.checked to see logfile today
3.no log file, logging = on

What is the expected output? What do you see instead?
tried both print and open, but all it shows is "![LogKext Daemon starting up : 
Thu Jul  7 11:57:21 2011]

![User 'Name' has logged in : Thu Jul  7 11:57:21 2:57:21 2"



What version of the product are you using? On what operating system?

logKext 2.3 Mac OSX 10.6.6
Please provide any additional information below.

What steps will reproduce the problem?
1.when I type print this sign comes up ![Not enough disk space remaining!
2. nothing stored is shown
3.

What is the expected output? What do you see instead?
all the logged data, ![Not enough disk space remaining!

What version of the product are you using? On what operating system?

2.3 mac os 10.6.7
Please provide any additional information below.

What steps will reproduce the problem?
1. Installing logKext.pkg under Snow Leopard
2.
3.

What is the expected output? What do you see instead?
During the installation, a window says "Can't use system extension" -
"System extension /System/Library/Extensions/logKext.kext wasn't installed
correctly..."


What version of the product are you using? On what operating system?
using logKext v2.2
using Mac OSX Snow Leopard v10.6.1

Please provide any additional information below.
LogKextClient works properly but obviously it can't find logKextDaemon.

Install failed
System extension doesn't work

What steps will reproduce the problem?

1. Write something
2. Shutdown computer

The keys pressed during the last minute or so before shutdown are not saved
to log file.

I'm using version 2.2 on a 10.5.4 CoreDuo MacBook.

logkext should log timestamps (and possibly application name?) when logging
keystrokes.

I have a different password to the log on my other computer, which I want to 
monitor. I want to run a shell on the computer that sets logKext to send shells 
to mine.

I am very inexperienced, don't know any programming languages.

Using MBP 15", 10.7.

What steps will reproduce the problem?
1. open logkextclient
2. type a command press enter; wait for completion
3. press the up arrow key, and the follow keycode is displayed: 
#logKextClient > ^[[A


What is the expected output? What do you see instead?
Expected to scroll through a buffer of the past command history like most
unix interactive command line utils.  See instead the ascii representation
of the uparrow keycode.


What version of the product are you using? On what operating system?
Not sure of the product version - sorry.  Using on Mac OSX Lepeord Intel
Macbook Pro - bought in mid 2008.


Please provide any additional information below.

What steps will reproduce the problem?
1. install logKext and use
2. type "info LogPath" to find your log file path
3. search in that folder
4. file is not there

What is the expected output? What do you see instead?
I thought I'd see the file but it's not there.

What version of the product are you using? On what operating system?
v2.2 on mac os x 10.4.11

Please provide any additional information below.

installd[444]   PackageKit: Install Failed: PKG: post-install scripts for 
"com.fsb.logkext.logkextExt.pkg"
Error Domain=PKInstallErrorDomain Code=112 UserInfo=0x1004f6ed0 "An error 
occurred while running scripts from the package “logKext-2.3.pkg”." {
    NSFilePath = "./postinstall";
    NSLocalizedDescription = "An error occurred while running scripts from the package \U201clogKext-2.3.pkg\U201d.";
    NSURL = "#logkext-1.pkg -- file://localhost/Users/xiao/Downloads/logKext-2.3.pkg";
    PKInstallPackageIdentifier = "com.fsb.logkext.logkextExt.pkg";
}

What steps will reproduce the problem?
1. Reboot System
2. Failure-Message: "/path/to/logkext failed to load. [..]"

What steps will reproduce the problem?
1. launch logkext client from a local terminal or remote SSH session

What is the expected output? What do you see instead?
I expect that there should be no GUI application launched.  Instead a
script editor tool launches and is shown as a separate application.

What version of the product are you using? On what operating system?
Mac OS 10.5.1
LogKExt v2.2

Please provide any additional information below.

I've installed the package on my system. (OS X 10.5.8 PPC). It says install 
success.  I go to the terminal run the sudo logKextClient command enter my 
password and it says:

Error: logKext Preferences cannot be found.  Is logKextDaemon running?


How do I get the client running if it's not already?  The preference file is 
confirmed in the default location.