Star Password Decoder

[Dimple Belousson]

Since many Windows applications can and will automatically save passwords, it's sometimes annoying when after so much time has passed since you actually need to type in your password, you've actually forgotten what your password was!That issue can be overcome with Asterisk Password Decrypter. While it doesn't actually decrypt anything as the name might suggest, Asterisk Password Decrypter can reveal what the password is behind the stars (or asterisks) you see on your screen instead of a plain text password.This password recovery program can reveal many hidden passwords in Windows including those for Microsoft programs like those from the Office Suite (Outlook password recovery), FTP clients like WS_FTP or FileZilla and some Internet browsers including special support for Internet Explorer.The trial version of Asterisk Password Decrypter is able to only reveal up to 3 characters of the passwords it uncovers.Compatibility and LicenseThis download is licensed as shareware for the Windows operating system from password software and can be used as a free trial until the trial period ends (after an unspecified number of days). The Asterisk Password Decryptor 3.31 demo is available to all software users as a free download with potential restrictions and is not necessarily the full version of this software.What version of Windows can Asterisk Password Decryptor run on?Asterisk Password Decryptor can be used on a computer running Windows 11 or Windows 10. Previous versions of the OS shouldn't be a problem with Windows 8 and Windows 7 having been tested. It runs on both 32-bit and 64-bit systems with no dedicated 64-bit download provided.Filed under: Asterisk Password Decryptor DownloadWe have tested Asterisk Password Decryptor 3.31 against malware with several different programs. Please review the test results. We have not certified this program as clean. [Read more]Download for Windows 4.33 MB

• $$ Cost:Free Trial

I installed an 8-TXS decoder in my 8P Duke of Gloucester TTS loco yesterday. This is the last of my steam locos to be upgraded, and I did so mainly in order to get the better chuff rate and the AFC sounds, despite the fact that there's no DoG sound file as yet. I used the Tornado profile, which has 3 cylinders and a decent chime whistle similar to the DoG. Perhaps Hornby will migrate the DoG TTS sound profile in due course - its sounds are very good.

The installation went well, although I had to reset the decoder with the Bluetooth password at the outset. However, when I came to run the auto-calibration, the loco did not move and I found that the overcurrent warning was showing in the app. I reloaded the profile as advised in the app, although I wonder if this was strictly necessary. The loco then ran well, but I didn't try autocalibration again.

I wonder if the decoder's overcurrent detection is too sensitive? Autocalibration seems to apply instant maximum voltage to the stationary motor, which will draw a much higher momentary current than normal acceleration from a standstill. I suppose it's possible that there's a genuine fault with the loco, but it's only a few years old and not heavily used so that seems unlikely. The overcurrent protection could at least reset itself in a user friendly way when the high current draw has been cleared.

I did trigger the autocalibration from DCC (Railmaster) after setting CV149 to 0 in the app, by turning on F28 (which also turns on F0). This is how I've always done it. The loco didn't even twitch, which suggests that the overcurrent triggered instantly. I haven't tried it again because reloading the profile gets rather tedious.

Yes I thought about using the Britannia profile but that is 2 cylinder rather than 3, and the Tornado does have decent chime whistles on F3, like the DoG. The only very minor gripe is that AFC uses F2 whistles as its moving-off sound - in an ideal world AFC could be set up to use F3 instead of F2.

I'd be happy to do more tests to pin this problem down, and I can certainly change my Railmaster setup to allow me to trigger F0 directly, although I've used F28 successfully many times before with other locos. I think the interesting test would be whether a lower setting for VHigh would remove the overcurrent, and if so how high a voltage it could tolerate.

The main barrier to doing this is the apparent need to reload the profile and then reset all the customised CVs in order to clear the overcurrent error shown in the app. This just too tedious to contemplate! Is there any other proven way of clearing the error?

I started by autocalibrating with F28, and it worked! I tried a couple of times more to be certain, and ran the loco successfully, and then I thought I'd better try using F0, and it failed with the overcurrent. I'm sure that this is nothing to do with F28 versus F0, but just some randomness in the overcurrent mechanism.

So following Steve's advice I powered off the track for at least 5 minutes (the loco has no power bank) and I rebooted the iPad, but this unfortunately didn't clear the overcurrent. The loco responds to sounds and makes chuffing noises but the motor doesn't turn.

ADCC/ABC testing has shown these decoders can be sensitive to voltage change on track resulting in spurious reaction to grubby track thinking it is a diode induced stop/reverse, hence a sensitivity setting is being introduced via CV128, however whether this will affect over-current tripping is yet to be considered.

I tried the decoder again this morning and it has magically recovered after a good night's sleep! Very strange, after a complete power down for 5 minutes yesterday didn't clear the overcurrent condition, and nor did a profile reload or a CV8 reset. I shall never use autocalibration again after this experience. Applying maximum voltage to a stationary motor just seems too vicious.

@LTSR, I can't do a stall test because I don't have a DC controller, and from reading up about it stall testing does seem to risk damaging the motor unless done very briefly. If I were to remove the decoder again I could check the resistance across the motor drive wires on the decoder socket, which would presumably give the stall current by Ohm's law.

You said that you used F28 as a trigger - as that is the AFC command which also triggers a number of other sounds eg whistle, steam cocks and chuffs, I wonder if that created a higher than usual current draw on an already marginal loco? Stick to F0 as Rob described and you should have no issues.

Thanks Steve. It would be good to know how the overcurrent protection works - what current triggers it and over what time measurement, and how it gets reset. Is the advice in the app to reload the profile a red herring, and it just resets after a suitable period of power off?

I thought about whether F28 would put an additional load on the decoder with the sounds starting, but in fact F28 only caused 1 overcurrent out of 4 recalibrations, whereas F0 caused the overcurrent on the one time that it was used directly. It could be that the F28 sounds divert a bit of power away from the motor drive, and hence slightly reduce the protected motor current? It's clearly right on the limit of the overcurrent protection.

I agree that autocalibration is useful, and I've used it many times previously without problems, but I wonder why it needs to use maximum motor voltage? Surely the back emf characteristics of the motor could be determined with a lower voltage?

I wasn't doing autocalibration, but I too get this message about Motor Overcurrent. My Bachmann Class 37 is on a DC track. The profile and everything loaded and I got sounds. However the loco didn't move. When I tried to reload the profile, after completion, I got the overcurrent message and the App has lost connection to the decoder (Bluetooth). Nothing I do seems to get it back. Is that the end of the decoder.

Steven, might I suggest that next time you have a problem, rather than adding a post to a topic that is different to your problem (by your own admission), you start your own topic to find your answer.

A little while ago I found the OWASP Juice Shop, and thoroughly enjoyed stumbling my way through its various challenges. The Juice Shop page itself can explain what it's about better than I need to here, but anybody looking for a stepping stone into the strange and mystical world of security testing, or even just web application testing in general, would be well-advised to check it out.

After sharing it with my team at work, I wrote a guide to help them progress through various challenges at their own pace, without feeling too lost. While writing that, I ended up including snippets of Python code I was running from the REPL to demonstrate, and thought "...hey, I could probably automate this whole thing!"

This blog is the result, and the code for the impatient ones is here. This blog and the linked repository were written against version 2.18of the Juice Shop - naturally, by the time I got around to writing this, there's been an update that added a new challenge which I haven't had a chance to really look at yet. Something to do after I finish writing this! Anyway, below is the full list of challenges along with some (hopefully) useful explanations for how I figured them out initially.

So opening :3000/#/score-board completes this challenge. The score board helpfully lists all the available flags, and at the end of the list, a Continue code that can be used to restore our progress. This updates with every new flag awarded - it's worth copying regularly, particularly if you're trying to inject data into the Juice Shop as youmay mistakenly crash the whole thing!

There's probably at least a dozen ways you can trip this flag, even without noticing. For now, let's try to login as test'(note the apostrophe) with any old password. It'll fail, showing us a SQLite error that'll come in handy later...

OK, things are heating up. If you're unfamiliar with Cross-site scripting(XSS) attacks, they're used by attackers to execute code in a victim's browser. A reflected XSS attack means the malicious payload is coming from the victim's request, somehow. If we copy the payload and paste it into the Search bar of the Juice Shop, we'll get a nasty little pop-up and a lovely little challenge complete notification, but what actually happened?

c80f0f1006