Some sites do not have their TLS security set- up correctly. You can get around the page that Chrome then displays. This is called the “interstitial bypass”, you should use it with great care (not like one of the sites I visited a year ago that got themselves a nice ransomware attack), for instance on machines you can dispose off.
The mechanism has changed over time, from a simple button to a passphrase that changes every now and then.
A way to bypass a Chrome interstitial page is to type a secret keyword. Until today, this not-no-secret keyword was “badidea”. And it just changed. So h… – François Beaufort – Google+
I need them one day to better understand xsd:choice mapping to C# for both XSD and WSDL usage.
I have the feeling that the WSDL and XSD importer are trying to be smart, so for instance when you have multiple choices that come down to a common basic type like a derivation from xsd:string, it makes to two properties: a C# enumeration to select the type and a C# string value for the content referencing the enumeration through a XmlChoiceIdentifierAttribute.
Recently I had to play some notification sounds in a Windows Delphi application where the application deployment should be as easy as possible: preferable copying the EXE around.
The thing that more recent Delphi versions made a lot easier is embedding WAV files as WAVE resources, more on that further on. Read the rest of this entry »
I hope this is a coincidence. Before Nick Hodges left, the TLS security of the various embarcadero https servers was increased, most from grade F. Now they might soon be grade F again.
Hopefully somebody in IT has time to take a renewed look as security needs constant attention.
Two very interesting videos showing some background information as it is extremely hard to anonymise data. Not just for now, but especially against future de-anonymisation efforts.
You always have to be careful with Delphi finalization sections cleaning up things that might have not created inside the corresponding initialization section. This is especially true for the System unit.
That one actually contains this little piece of code that is being called after FinalizeUnits is called which also fianalises external memory managers like FastMM:
{$IFDEF MSWINDOWS}
FinalizeLocaleDate;
if PreferredLanguagesOverride <> nil then
FreeMem(PreferredLanguagesOverride);
...
Which means that you will have to enable the NeverUninstall conditional define as soon as the InstHashMap has been used.
Most often that’s the case with FMX applications that heavily relies on weak references.
The same holds for PreferredLanguagesOverride which is used by SetLocaleOverride and can be worked around by performing this right at the end of the .dpr:
Old style KCT-101 dip-switch settings (least significant bit is on the left; top=0; bottom=1)
A = 0000: 0
B = 1000: 1
C = 0100: 2
D = 1100: 3
E = 0010: 4
F = 1010: 5
G = 0110: 6
H = 1110: 7
I = 0001: 8
J = 1001: 9
K = 0101: 10
L = 1101: 11
M = 0011: 12
N = 1001: 13
O = 0111: 14
P = 1111: 15
De sleutelhanger is een mini afstandsbediening met VIER voorgeprogrammeerde kanaten. (ook wel cijfercodes genoemd)
De voorgeprogrammeerde kanaten zijn: 1 -2 – 15 – 16.
Deze vier kanalen zijn niet te wijzigen. Bij het indrukken van de toetsen worden altijd deze VIER kanalen (cijfercode 1-2-15-16) geactiveerd.
Old style YCT-100 / TMT-2100
Op de afstandbediening bevinden zich 4x AAN en 4x UIT druktoetsen voor 16 verschillende schakelstanden.
Met de schuifschakelaar aan de onderzijde bepaalt u de schakelstanden, te weten:
Aan-Uitschakelen van ontvangers
Boven de linker toetsen staat het woordje ON, met deze toetsen schakelt u de contactdozen en/of inbouwontvangers
AAN. Boven de rechter toetsen staat het woordje OFF, met deze toetsen schakelt o de contactdozen en/of inbouwontvangers UIT.
Dimmen (alleen In combinatie met model YC412 en CM 300)
Nadat de dimmers zijn ingeschakeld drukt men nogmaals op de ON·toets {links}, om de lichtsterkteregelaar te starten.
Zodra de gewenste lichtsterkte is bereikt, drukt u nogmaals de ON-toets in. (zie afb. 7) De ingestelde lichtsterkte is nu in het
geheugen opgeslagen. De eerst volgende keer dat u dimmer inschakelt, zal de lichtsterkte gelijk zijn aan de laatste stand.
Batterij wordt meegeleverd, type A23/12 Volt alkaline, gebruik bij vervanging alleen alkaline batterij.
What I want is a graph over time. Based on that, I can start working on different triggers than the default “less than 20% free space available“, for instance: