Steve Jacobs
Downloads: 0
Posts: 90
Smile Score: +42
About Me
I am a Free member
Gender: Male


Visit Stats
Last Visit: 2 years ago
Member Since: 09 Feb 2008
Profile Views: 2,473

Website
http://encropowered.com/
Steve Jacobs's Posts
Average Rating from Steve:
(7)

sort: smiles | time
burypromote
+1
Encro commented on 14 Nov 2010
You are whinging about a free piece of software that is maintained by a very small team?

So what you are really saying is you have had 10 months to learn how to program and contribute a fix to this community based open source bug yet chose not to help. That is completely unacceptable!!!

In all seriousness though, I'm only joking with the above expectation but your comment is a little absurd. It takes time to analyse logs, data from Instruments and debugging information not to mention peoples everyday lives and endless other tasks. This project is a hobby developed and maintained by the kind folk who build it for the world (for free). I would suspect that the Netscape plugin API is some incredibly old tortuous code that is quite a pain to work with and understand but I'm only guessing :)
Common log file locations are:
$HOME/Library/Logs
/Library/Logs
/private/var/log
if you would like to confirm file sizes.

The largest log file I have is 2.8MiB which goes back to early 2007.
Log files are rotated and archived using zip compression by the system to make the log files usually incredibly small.

Speak to the Camino team in the forums and let them know it concerns you that it's not in a release build yet. Until then enjoy the program and ignore the extra generated error lines in the console logs. They are only a minor inconvenience in extra logged data and not something that has caused any significant issues
[Version 2.0.5]


1 Reply

burypromote

+42
Encro replied on 14 Nov 2010
Ooops I clicked the wrong reply button :)
This is a reply in the "kCGErrorIllegalArgument: CGSGetWindowBounds: NULL window" discussion below.
burypromote
+6
Encro commented on 06 Sep 2010
I'm just playing with the trial now in personal review and it is incredibly good. I can only imagine the amount of time and speed up that I would have occurred by using this app to file out repetitive business form data for customers.

One thing I can see that is missing is on the Set Variable action. It should have a Prompt with dialog box to set a variable option included.
I know this could be done by using applescript or javascript to prompt and store the variable but it seems to be such an obvious and straight forward omission which could further enhance the product by being added in directly. A form could be exactly the same for each customer 99% of the time and all that would be different would be the name. In a call centre environment etc you are going to be processing this stuff in real time while on the call so you won't be recalling a list of names from a json file or xml etc. A quick prompt to fill in the name would be quick but I guess you could submit the form manually after tweaking the value in the name field etc. I would still love to see this added though

A very very solid v1.0 though so top work Todd! :)
[Version 1.0]



burypromote
+10
Encro commented on 24 Mar 2010
To avoid this being buried in the comments.
The Smultron Project has been forked by Jean-François Moy and is now available at: http://github.com/jfmoy/Fraise

See the MacUpdate Fraise Page for more details:
http://www.macupdate.com/fraise
[Version 3.6b1]



burypromote
+1
Encro commented on 01 Dec 2009
We use the 2X Client to connect to a Microsoft RDP Server. It handles load balancing a lot better for running multiple virtualised desktops. One thing that is a little annoying is the Mac version doesn't seem to allow Windowed mode when connected to a virtual desktop and always wants to start on monitor 1 if you have more than one screen.
At this stage I prefer Microsoft RDC on the Mac because it allows a bit more control but this is advancing quicker than RDC.

There are some further instructions here detailing connecting to an Application Server.
http://www.2x.com/applicationserver/as_manual/2XApplicationServer-Installi-4.html
[Version 7.3.753]



burypromote
+4
Encro commented on 25 Sep 2009
Please see my extensive comments on http://www.macupdate.com/trimmit as these dangers apply equally as well to Xslimmer.

Use an application such as http://www.macupdate.com/codesign-checker to test if the application is signed before making changes.

These apps can cause major problems for code signed applications that access the keychain and it is in your best interest to avoid using them to modify code signed binaries.

Unsigned binaries are fine to experiment with for size reduction etc.
[Version 1.7.5]



burypromote
encro commented on 04 May 2009
You should make this the actual version and provide the Felt Version as an option. After playing with WillowPE it looks pretty cool and can do quite a bit. I can see you are trying to make it fun and it shines through with the playful language all over the website but I feel people would take it more seriously if this were the actual version in the spotlight.

What would be really awesome is the addition of a step sequence that allowed keyboard control and inline sending of variables, the pasteboard and macros similar to how AutoIT works on the PC which I use heavily in a business environment (It can do much more than this but there is still no Mac version or equivalent yet).

eg: A webform sequence

Send("{"!TAB"}") ;Send Command Tab to switch back to browser from willow.
Send("{$EMAIL}") ;Paste the current $email variable.
Send("{TAB 2}") ;Send Tab Sequence Twice.
Send("{@HOUR}")
Send("{DOWN 3}")
Send("{TAB}")
Send("a random string of words")
Send("{TAB}")

or even:
Send($name & "{SPACE}" & $department & "{SPACE}" & "|" & "{SPACE}" & @Mon & "-" & @MDay & "{SPACE}" & "|" & "{SPACE}" & @Hour & ":" & @Min & "{SPACE}" & "|" & "{SPACE}")

http://www.autoitscript.com/autoit3/docs/macros.htm
http://www.autoitscript.com/autoit3/docs/appendix/SendKeys.htm
[Version 1.0.4]


1 Reply

burypromote

+42
encro replied on 04 May 2009
Edit: I've discovered an app that does what I require.
burypromote
+4

encro reviewed on 07 Mar 2009
Excellent work. This tool has standardised the behaviour to do the exact same thing in every app and has made the green zoom button useful again rather than an ignored button because you couldn't guarantee the result.

Fantastic little helper.
[Version 1.2]



burypromote

encro reviewed on 05 Aug 2008
Haha, awesome work!
More fun than watching the dock bounce.
[Version 1.0]



burypromote
encro tipped on 21 Feb 2008
You can also enable 'Show Path Bar' in the View Menu of the Finder if you are using OS X 10.5

This will place a path bar at the bottom of the Finder Window.

If I need to obtain the POSIX path I usually just drag a file or folder into Terminal.app and copy the path from there.
[Version 1.0.5]



burypromote
+1
encro had trouble on 10 Feb 2008
Be aware that apps like Trimmit can break code signed applications such as Mail.app on 10.5 if the strip debug symbols option is enabled. This is why it is a good thing to have the backup option enabled.

I can manage to consistently break Mail.app and cause it to popup the password window. It will then never remember the password, attempt to store or attempt to retrieve it from the keychain *if the Application code signature is invalid*.

In testing I've tried removing many things from Mail.app such as language files, compressing images, removing redundant unnecessary files and stripping the redundant PowerPC binary and various other things from the bundle. None of this seems to damage Mail.app's code signature.

How do you break Mail.app you ask?

By stripping the debug symbols from Mail.app using one of many app trimming applications such as Trimmit. Since Mac OS X 10.5 Leopard introduced Code Signing and Apple Mail is code signed my guess is that because the bundle is changed and the code signature is then broken and invalid Apple Mail is then treated as an untrusted application and is refused access to the keychain by SecurityServer.

According to
http://developer.apple.com/releasenotes/Security/RN-CodeSigning/index.html
applications should trigger a popup confirmation to allow the Application to update the keychain but it appears that Mail.app does not do this and SecurityServer suppresses the dialog as the code signature is invalid.
Filed as Apple Bug ID #5734181

Opening Console.app and checking secure.log shows many entries from SecurityServer to advise:
Feb 10 23:04:02 macbookpro com.apple.SecurityServer[20]: suppressing keychain prompt for invalidly signed client /Applications/Mail.app(7514)
Feb 10 23:04:32: --- last message repeated 16 times ---

If you are getting these messages, this wll mean you may need to restore from a backup version of Mail.app from storage, time machine or another computer. If you re-install the app from the original 10.5 Installer CD you may also need to run the 10.5.1 installer and Security Update to ensure that Mail.app is up to date.
[Version 0.95]


3 Replies

burypromote

+42
encro commented on 10 Feb 2008
Code Signing: cs_invalid :
(Pretty much all Apple applications are code signed and will break on 10.5)

Apple Apps:
Activity Monitor
Address Book
Airport Utility
Console
DictionaryPanel
Directory Utility
Disk Utiliity
iCal
iChat
iDVD
Image Capture
Input Method Hot
iPhoto
iSync
iTunes
iWeb
Java Preferences
Java Web Start
Keychain Access
Mail
Network Utility
ODBC Administrator
PhotoBooth
Podcast Capture
Preview
Quicktime Broadcaster
QuickTime Player
RAID Utility
Safari
Server Admin Tools
Soundtrack Pro
Spaces
Stickies
System Profiler
Terminal
Terminal
TextEdit
ThumbnailServer
Time Machine
VoiceOver Utility

3rd Party apps:
Cyberduck
EyeTV 3
Newsfire
burypromote

+42
encro commented on 21 Feb 2008
Apple Bug ID #5734181 Closed. Marked as behaves as intended.

I think it would have been better if SecurityServer advised that the Application has been changed and the content could no longer be verified. The keychain asked if you would like to trust the app with broken signature.

I can see where Apple is coming from a Security Perspective though.
burypromote

+42
Encro replied on 25 Sep 2009
To test an application signature (Mail.app in this context):

codesign -vv /Applications/Mail.app

If it's good you should get the following:
/Applications/Mail.app: valid on disk
/Applications/Mail.app: satisfies its Designated Requirement


If it is broken you will get the following:
/Applications/Mail.app: code or signature modified


Applications with a broken signature will be denied from reading from the keychain.
burypromote
encro had trouble on 10 Feb 2008
Monolingual 1.3.8 will break Mail.app on Leopard and possibly other code signed applications.

I can manage to consistently break Mail.app and cause it to popup the password window. It will then never remember the password, attempt to store or attempt to retrieve it from the keychain *if the Application code signature is invalid*.

In testing I've tried removing many things from Mail.app such as language files, compressing images, removing redundant unnecessary files and stripping the redundant PowerPC binary and various other things from the bundle. None of this seems to damage Mail.app's code signature.

How do you break Mail.app you ask?

By stripping the debug symbols from Mail.app using one of many app trimming applications such as Monolingual. Since Mac OS X 10.5 Leopard introduced Code Signing and Apple Mail is code signed my guess is that because the bundle is changed and the code signature is then broken and invalid Apple Mail is then treated as an untrusted application and is refused access to the keychain by SecurityServer.

According to
http://developer.apple.com/releasenotes/Security/RN-CodeSigning/index.html
applications should trigger a popup confirmation to allow the Application to update the keychain but it appears that Mail.app does not do this and SecurityServer suppresses the dialog as the code signature is invalid.
I have filed as Apple Bug ID #5734181

Opening Console.app and checking secure.log shows many entries from SecurityServer to advise:
Feb 10 23:04:02 macbookpro com.apple.SecurityServer[20]: suppressing keychain prompt for invalidly signed client /Applications/Mail.app(7514)
Feb 10 23:04:32: --- last message repeated 16 times ---

If you are getting these messages, this wll mean you may need to restore from a backup version of Mail.app from storage, time machine or another computer. If you re-install the app from the original 10.5 Installer CD you may also need to run the 10.5.1 installer and Security Update to ensure that Mail.app is up to date.


===================================
Technical Details for strip command
===================================
/usr/bin/strip: changes being made to the file will invalidate the code signature in: /private/tmp/Mail.app/Contents/MacOS/Mail

Stripping debug symbols.

#!/bin/zsh
#This shell code sample taken from Trimmit.app
[[ -n $sym ]]&&{
# strip debug symbols. "2>&1" means error messages to the standard out.
/usr/bin/strip -Sur Contents/MacOS/*(*) 2>&1
/usr/bin/strip -Sx **/*.dylib(N) **/*.framework/**/*(*N) 2>/dev/null
echo "== Stripping debug symbols."
[Version 1.3.8]


2 Replies

burypromote

+42
encro commented on 10 Feb 2008
Code Signing: cs_invalid :
(Pretty much all Apple applications are code signed and will break on 10.5 if debug stripping is enabled)

Apple Apps:
Activity Monitor
Address Book
Airport Utility
Console
DictionaryPanel
Directory Utility
Disk Utiliity
iCal
iChat
iDVD
Image Capture
Input Method Hot
iPhoto
iSync
iTunes
iWeb
Java Preferences
Java Web Start
Keychain Access
Mail
Network Utility
ODBC Administrator
PhotoBooth
Podcast Capture
Preview
Quicktime Broadcaster
QuickTime Player
RAID Utility
Safari
Server Admin Tools
Soundtrack Pro
Spaces
Stickies
System Profiler
Terminal
Terminal
TextEdit
ThumbnailServer
Time Machine
VoiceOver Utility

3rd Party apps:
Cyberduck
EyeTV 3
Newsfire
burypromote

+42
encro commented on 21 Feb 2008
Apple Bug ID #5734181 Closed. Marked as behaves as intended.

I think it would have been better if SecurityServer advised that the Application has been changed and the content could no longer be verified. The keychain asked if you would like to trust the app with broken signature.

I can see where Apple is coming from a Security Perspective though.
Displaying 1-10 of 39
1 2 3 4 >
Displaying 1-2 of 2
Please login or create a new
MacUpdate Member account
to use this feature


- -