[Q] Proxy enumeration problem
See original GitHub issue(let me know if I should rather ask on Stackoverflow)
Almost done with the proxy I have a last thing left: enumeration. For code like:
for (var arg in arguments)
print(arg);
I get no output, even though my ownKeys code is called and returns the array indices. Someone mentioned the returned list is filtered against the list of keys in the target object (like an intersection). What’s the correct way to make enumeration working?
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (12 by maintainers)
Top Results From Across the Web
Sensor Proxy behind a proxy-firewall
Hi. I am setting up Tenalbe sensor proxy, however due to strict network requirements, this server will not be directly connected to the...
Read more >enumeration operation may not execute. Error? - Stack Overflow
I had this problem as well but not iterating over the collection isn't really an option for me. After some thought, I did...
Read more >Troubleshooting Microsoft Defender for Identity known issues
Describes how you can troubleshoot issues in Microsoft Defender for Identity. ... Proxy authentication problem presents as a licensing error.
Read more >Tenable Add-On for Splunk struggling with proxy connection
Nessus custom SSL certificate setup issue · FYI: Nessus Agents up to v8. · Problems with Nessus Plugin 24271 (SMB Shares File Enumeration...
Read more >Dynamic Enumeration of Similarity Joins - DROPS
As an example, O is set of points in Rd and a query Q specifies a simple ... A widely studied problem related...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

There are several places where property attributes of a property are queried internally, so it’s not limited to enumeration only. I could add the trap initially for enumeration only, to fix this particular limitation, and then figure out what changes are needed for all the remaining call sites. But we’ll see, I’ll check what’s needed when I get the chance 😃
The
__proto__property is the “internal” prototype of the object and is an inherited getter. There’s also an artificial debugger property which provides the value without a getter call.