x3f | Tools for manipulating X3F files from Sigma cameras | Camera library

So, this is a bit of a round-about fashion, but use a bytes object:

Changed for (int i = 0; i < sizeof shellcode; i++) { to for (int i = 0; i < sizeof shellcode - 1; i++) { and it now works!

I don't know where you see the value 0x119, but BYTE bootstrap[12] is a BYTE array.

So assigning bootstrap[i++] = sizeof(bootstrap) + shellcodeALength - i - 4; will store the lowest byte of the expression in bootstrap[i++] and ignore the rest, hence can never go above 255.

You probably want something like this instead:

The Serial object has a __del__ method which does what you want, so you don't need to write it.

That being said, you shouldn't rely on __del__ being called. For the same reason that you shouldn't leave files opened, you shouldn't rely on the garbage collector to close things for you. In fact, during interpreter shutdown, there is no reason to garbage collect your objects since the OS will reclaim this memory anyway, so implementations other than CPython don't really bother. The reason to do it is these objects that hold handles to OS resources which may not get closed when the program closes.

So, to be sure that the handle gets released properly, you should close() the serial port yourself, and not wait for interpreter shutdown to do it for you.

I think iframes might have a # in their url like this: www.someurl.com/page/#/something, try removing the #: www.someurl.com/page/something.

There are 3 issues with your code.

First: you are using input values in form of hexstring values - they have to be transformed to binary data with hex2bin.

Second: Your PHP script is using a random padding so it adds some data to makes the output looking different each time it runs. For decryption only the first 16 bytes (32 hexstring characters) will be used (those in your $e variable) you have to force OpenSSL to deny any padding - that's what the option "OPENSSL_ZERO_PADDING" is good for.

Third: The other option "OPENSSL_RAW_DATA" is forcing OpenSSL to take raw data instead of base64-encoded data.

Put all three parts together in the code you receive the expected plaintext (here in hexstring): c704de5f1eacc0403d0000da5cf60941

console:

There is no trailing slash, and therefore, if I'm interpreting the spec correctly, isn't the "right-most" slash is the one before c, and therefore the cookie-path is a/b?

Almost. From 1, uri-path would be /a/b/c. 2 and 3 don't apply. From 4, the output would be /a/b, with the leading / included.

Another way of asking is, if a modern, spec-compliant browser received a cookie

If you mean actual browsers, this isn't exactly the same question; have you found an interpretation that differs?

There is still divergence from the spec, and a resource like the web-platform-tests dashboard for cookies/path may be a better resource to confirm modern browser behaviour.

However, to answer in terms of the spec:

received a cookie with no Path attribute ... from https://example.com/a/b/c, should that cookie be sent in a subsequent request to https://example.com/a/b?

Yes, because the algorithm in 5.1.4 means the default-path of the cookie is /a/b, and this path-matches /a/b because

The cookie-path and the request-path are identical.

Firstly, to address the code syntax itself, PHP allows you to dynamically create variable names.

Let's say you have a variable:

According to your code you have created a QPushButton with a custom icon instead of modifying the clear icon of the QLineEdit.

The solution is to access the QToolButton and set the icon: